Feb  1 18:57:32 joe dbus[1463]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Feb  1 18:57:36 joe dbus[1463]: [system] Successfully activated service 'org.freedesktop.PackageKit'
[…]
Feb  1 18:57:52 joe dbus[1463]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Feb  1 18:57:52 joe dbus[1463]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb  1 18:58:22 joe acpid: client connected from 21645[0:0]
Feb  1 18:58:22 joe acpid: 1 client rule loaded
Feb  1 18:58:24 joe acpid: client connected from 21690[0:0]
Feb  1 18:58:24 joe acpid: 1 client rule loaded
Feb  1 18:58:25 joe acpid: client 2437[0:0] has disconnected
Feb  1 18:58:25 joe acpid: client 21645[0:0] has disconnected
Feb  1 18:58:25 joe acpid: client connected from 21700[0:0]
Feb  1 18:58:25 joe acpid: 1 client rule loaded
Feb  1 18:58:26 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,882734 seconds 
Feb  1 18:58:26 joe acpid: client 21700[0:0] has disconnected
Feb  1 18:58:26 joe acpid: client connected from 21706[0:0]
Feb  1 18:58:26 joe acpid: 1 client rule loaded
Feb  1 18:58:26 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,355983 seconds 
Feb  1 18:58:26 joe acpid: client 21706[0:0] has disconnected
Feb  1 18:58:26 joe acpid: client connected from 21708[0:0]
Feb  1 18:58:26 joe acpid: 1 client rule loaded
Feb  1 18:58:27 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,238147 seconds 
Feb  1 18:58:27 joe acpid: client 21708[0:0] has disconnected
Feb  1 18:58:27 joe acpid: client connected from 21716[0:0]
Feb  1 18:58:27 joe acpid: 1 client rule loaded
Feb  1 18:58:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,878238 seconds 
Feb  1 18:58:30 joe acpid: client 21716[0:0] has disconnected
Feb  1 18:58:30 joe acpid: client connected from 21715[0:0]
Feb  1 18:58:30 joe acpid: 1 client rule loaded
Feb  1 18:58:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,882411 seconds 
Feb  1 18:58:30 joe acpid: client 21715[0:0] has disconnected
Feb  1 18:58:30 joe acpid: client connected from 21719[0:0]
Feb  1 18:58:30 joe acpid: 1 client rule loaded
Feb  1 18:58:30 joe acpid: client 21719[0:0] has disconnected
Feb  1 18:58:30 joe acpid: client connected from 21718[0:0]
Feb  1 18:58:30 joe acpid: 1 client rule loaded
Feb  1 18:58:30 joe acpid: client 21718[0:0] has disconnected
Feb  1 18:58:30 joe acpid: client connected from 21750[0:0]
Feb  1 18:58:30 joe acpid: 1 client rule loaded
Feb  1 18:58:30 joe acpid: client connected from 21751[0:0]
Feb  1 18:58:30 joe acpid: 1 client rule loaded
Feb  1 18:58:30 joe acpid: client connected from 21753[0:0]
Feb  1 18:58:30 joe acpid: 1 client rule loaded
Feb  1 18:58:30 joe acpid: client connected from 21752[0:0]
Feb  1 18:58:30 joe acpid: 1 client rule loaded
Feb  1 18:58:30 joe acpid: client connected from 21760[0:0]
Feb  1 18:58:30 joe acpid: 1 client rule loaded
Feb  1 18:58:30 joe acpid: client connected from 21762[0:0]
Feb  1 18:58:30 joe acpid: 1 client rule loaded
Feb  1 18:58:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,290751 seconds 
Feb  1 18:58:31 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,818537 seconds 
Feb  1 18:58:31 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,754924 seconds 
Feb  1 18:58:31 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,266656 seconds 
Feb  1 18:58:31 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,234906 seconds 
Feb  1 18:58:31 joe acpid: client 21750[0:0] has disconnected
Feb  1 18:58:31 joe acpid: client 21751[0:0] has disconnected
Feb  1 18:58:31 joe acpid: client 21753[0:0] has disconnected
Feb  1 18:58:31 joe acpid: client 21752[0:0] has disconnected
Feb  1 18:58:31 joe acpid: client 21760[0:0] has disconnected
Feb  1 18:58:31 joe acpid: client 21762[0:0] has disconnected
Feb  1 18:58:31 joe acpid: client connected from 21779[0:0]
Feb  1 18:58:31 joe acpid: 1 client rule loaded
Feb  1 18:58:31 joe acpid: client connected from 21783[0:0]
Feb  1 18:58:31 joe acpid: 1 client rule loaded
Feb  1 18:58:31 joe acpid: client connected from 21781[0:0]
Feb  1 18:58:31 joe acpid: 1 client rule loaded
Feb  1 18:58:31 joe acpid: client connected from 21784[0:0]
Feb  1 18:58:31 joe acpid: 1 client rule loaded
Feb  1 18:58:31 joe acpid: client connected from 21785[0:0]
Feb  1 18:58:31 joe acpid: 1 client rule loaded
Feb  1 18:58:31 joe acpid: client 21779[0:0] has disconnected
Feb  1 18:58:31 joe acpid: client 21781[0:0] has disconnected
Feb  1 18:58:31 joe acpid: client connected from 21786[0:0]
Feb  1 18:58:31 joe acpid: 1 client rule loaded
Feb  1 18:58:31 joe acpid: client connected from 21782[0:0]
Feb  1 18:58:31 joe acpid: 1 client rule loaded
Feb  1 18:58:31 joe acpid: client connected from 21788[0:0]
Feb  1 18:58:31 joe acpid: 1 client rule loaded
Feb  1 18:58:31 joe acpid: client connected from 21789[0:0]
Feb  1 18:58:31 joe acpid: 1 client rule loaded
Feb  1 18:58:31 joe acpid: client connected from 21787[0:0]
Feb  1 18:58:31 joe acpid: 1 client rule loaded
Feb  1 18:58:31 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,229171 seconds 
Feb  1 18:58:31 joe acpid: client 21783[0:0] has disconnected
Feb  1 18:58:31 joe acpid: client 21784[0:0] has disconnected
Feb  1 18:58:31 joe acpid: client 21785[0:0] has disconnected
Feb  1 18:58:31 joe acpid: client 21786[0:0] has disconnected
Feb  1 18:58:31 joe acpid: client 21782[0:0] has disconnected
Feb  1 18:58:31 joe acpid: client 21788[0:0] has disconnected
Feb  1 18:58:31 joe acpid: client 21789[0:0] has disconnected
Feb  1 18:58:31 joe acpid: client 21787[0:0] has disconnected
Feb  1 18:58:31 joe acpid: client connected from 21790[0:0]
Feb  1 18:58:31 joe acpid: 1 client rule loaded
Feb  1 18:58:31 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,259734 seconds 
Feb  1 18:58:31 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,981206 seconds 
Feb  1 18:58:32 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,155246 seconds 
Feb  1 18:58:32 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,193490 seconds 
Feb  1 18:58:32 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,334812 seconds 
Feb  1 18:58:32 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,342426 seconds 
Feb  1 18:58:32 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,861761 seconds 
Feb  1 18:58:32 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,916665 seconds 
Feb  1 18:58:32 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,939687 seconds 
Feb  1 18:58:32 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,959909 seconds 
Feb  1 18:58:32 joe acpid: client 21790[0:0] has disconnected
Feb  1 18:58:32 joe acpid: client connected from 21827[0:0]
Feb  1 18:58:32 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client 21827[0:0] has disconnected
Feb  1 18:58:37 joe acpid: client connected from 21829[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21830[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client 21829[0:0] has disconnected
Feb  1 18:58:37 joe acpid: client 21830[0:0] has disconnected
Feb  1 18:58:37 joe acpid: client connected from 21832[0:0]
Feb  1 18:58:37 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,355162 seconds 
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client 21832[0:0] has disconnected
Feb  1 18:58:37 joe acpid: client connected from 21833[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client 21833[0:0] has disconnected
Feb  1 18:58:37 joe acpid: client connected from 21840[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client 21840[0:0] has disconnected
Feb  1 18:58:37 joe acpid: client connected from 21835[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client 21835[0:0] has disconnected
Feb  1 18:58:37 joe acpid: client connected from 21836[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client 21836[0:0] has disconnected
Feb  1 18:58:37 joe acpid: client connected from 21841[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client 21841[0:0] has disconnected
Feb  1 18:58:37 joe acpid: client connected from 21831[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client 21831[0:0] has disconnected
Feb  1 18:58:37 joe acpid: client connected from 21837[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client 21837[0:0] has disconnected
Feb  1 18:58:37 joe acpid: client connected from 21834[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client 21834[0:0] has disconnected
Feb  1 18:58:37 joe acpid: client connected from 21844[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client 21844[0:0] has disconnected
Feb  1 18:58:37 joe acpid: client connected from 21848[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client 21848[0:0] has disconnected
Feb  1 18:58:37 joe acpid: client connected from 21846[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client 21846[0:0] has disconnected
Feb  1 18:58:37 joe acpid: client connected from 21845[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client 21845[0:0] has disconnected
Feb  1 18:58:37 joe acpid: client connected from 21839[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21838[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21850[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21842[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21843[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21849[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21912[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21916[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21914[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21923[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21922[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21921[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21926[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21924[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21920[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21917[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21915[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21927[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21919[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21918[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21925[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21928[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:37 joe acpid: client connected from 21958[0:0]
Feb  1 18:58:37 joe acpid: 1 client rule loaded
Feb  1 18:58:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,591764 seconds 
Feb  1 18:58:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,921379 seconds 
Feb  1 18:58:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,997818 seconds 
Feb  1 18:58:45 joe acpid: client 21839[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21838[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21842[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21843[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21912[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21916[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21914[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21923[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21922[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21921[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21926[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21924[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21920[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21915[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21927[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21919[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21918[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21925[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client 21928[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client connected from 22009[0:0]
Feb  1 18:58:45 joe acpid: 1 client rule loaded
Feb  1 18:58:45 joe acpid: client 22009[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client connected from 22008[0:0]
Feb  1 18:58:45 joe acpid: 1 client rule loaded
Feb  1 18:58:45 joe acpid: client 22008[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client connected from 22014[0:0]
Feb  1 18:58:45 joe acpid: 1 client rule loaded
Feb  1 18:58:45 joe acpid: client 22014[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client connected from 22015[0:0]
Feb  1 18:58:45 joe acpid: 1 client rule loaded
Feb  1 18:58:45 joe acpid: client 22015[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client connected from 22017[0:0]
Feb  1 18:58:45 joe acpid: 1 client rule loaded
Feb  1 18:58:45 joe acpid: client 22017[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client connected from 22011[0:0]
Feb  1 18:58:45 joe acpid: 1 client rule loaded
Feb  1 18:58:45 joe acpid: client 22011[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client connected from 22018[0:0]
Feb  1 18:58:45 joe acpid: 1 client rule loaded
Feb  1 18:58:45 joe acpid: client 22018[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client connected from 22020[0:0]
Feb  1 18:58:45 joe acpid: 1 client rule loaded
Feb  1 18:58:45 joe acpid: client 22020[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client connected from 22021[0:0]
Feb  1 18:58:45 joe acpid: 1 client rule loaded
Feb  1 18:58:45 joe acpid: client 22021[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client connected from 22010[0:0]
Feb  1 18:58:45 joe acpid: 1 client rule loaded
Feb  1 18:58:45 joe acpid: client connected from 22013[0:0]
Feb  1 18:58:45 joe acpid: 1 client rule loaded
Feb  1 18:58:45 joe acpid: client 22013[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client connected from 22025[0:0]
Feb  1 18:58:45 joe acpid: 1 client rule loaded
Feb  1 18:58:45 joe acpid: client 22025[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client connected from 22026[0:0]
Feb  1 18:58:45 joe acpid: 1 client rule loaded
Feb  1 18:58:45 joe acpid: client 22026[0:0] has disconnected
Feb  1 18:58:45 joe acpid: client connected from 22022[0:0]
Feb  1 18:58:45 joe acpid: 1 client rule loaded
Feb  1 18:58:49 joe acpid: client 22022[0:0] has disconnected
Feb  1 18:58:49 joe acpid: client connected from 22023[0:0]
Feb  1 18:58:49 joe acpid: 1 client rule loaded
Feb  1 18:58:49 joe acpid: client 22023[0:0] has disconnected
Feb  1 18:58:49 joe acpid: client connected from 22019[0:0]
Feb  1 18:58:49 joe acpid: 1 client rule loaded
Feb  1 18:58:49 joe acpid: client 22019[0:0] has disconnected
Feb  1 18:58:49 joe acpid: client connected from 22024[0:0]
Feb  1 18:58:49 joe acpid: 1 client rule loaded
Feb  1 18:58:49 joe acpid: client 22024[0:0] has disconnected
Feb  1 18:58:51 joe acpid: client connected from 22029[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client 22029[0:0] has disconnected
Feb  1 18:58:51 joe acpid: client connected from 22027[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client 22027[0:0] has disconnected
Feb  1 18:58:51 joe acpid: client connected from 22030[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client 22030[0:0] has disconnected
Feb  1 18:58:51 joe acpid: client connected from 22067[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client 22067[0:0] has disconnected
Feb  1 18:58:51 joe acpid: client connected from 22028[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22066[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client 22066[0:0] has disconnected
Feb  1 18:58:51 joe acpid: client connected from 22031[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client 22031[0:0] has disconnected
Feb  1 18:58:51 joe acpid: client connected from 22070[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client 22070[0:0] has disconnected
Feb  1 18:58:51 joe acpid: client connected from 22072[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client 22072[0:0] has disconnected
Feb  1 18:58:51 joe acpid: client connected from 22073[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client 22073[0:0] has disconnected
Feb  1 18:58:51 joe acpid: client connected from 22069[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client 22069[0:0] has disconnected
Feb  1 18:58:51 joe acpid: client connected from 22074[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client 22074[0:0] has disconnected
Feb  1 18:58:51 joe acpid: client connected from 22078[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client 22078[0:0] has disconnected
Feb  1 18:58:51 joe acpid: client connected from 22075[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client 22075[0:0] has disconnected
Feb  1 18:58:51 joe acpid: client connected from 22079[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client 22079[0:0] has disconnected
Feb  1 18:58:51 joe acpid: client connected from 22108[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22096[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22111[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22107[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22114[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22113[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22116[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22115[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22138[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22147[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22144[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22146[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22151[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22150[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22165[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22149[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22170[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22152[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22172[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:51 joe acpid: client connected from 22173[0:0]
Feb  1 18:58:51 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,631537 seconds 
Feb  1 18:58:52 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,660875 seconds 
Feb  1 18:58:52 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,752088 seconds 
Feb  1 18:58:52 joe acpid: client 22108[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22096[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22111[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22107[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22114[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22113[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22116[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22115[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22138[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22147[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22144[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22146[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22151[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22150[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22165[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22149[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22170[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22152[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22172[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22173[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client connected from 22206[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22208[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22207[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client 22206[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client connected from 22211[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22212[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22209[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22213[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22217[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22210[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client 22207[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client connected from 22216[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22215[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22214[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22218[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22219[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client 22208[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client connected from 22220[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22225[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22221[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22223[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22226[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22224[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22222[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe acpid: client connected from 22230[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,030642 seconds 
Feb  1 18:58:52 joe acpid: client 22211[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22212[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22209[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22213[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22217[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22210[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22216[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22215[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22214[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22218[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22219[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22220[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22225[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22223[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22226[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22224[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22222[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client 22230[0:0] has disconnected
Feb  1 18:58:52 joe acpid: client connected from 22231[0:0]
Feb  1 18:58:52 joe acpid: 1 client rule loaded
Feb  1 18:58:52 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,116123 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,293666 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,301561 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,313765 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,357300 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,383545 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,407421 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,207078 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,213384 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,219297 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,222569 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,220987 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,225633 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,220936 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,191790 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,193328 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,189683 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,202418 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,271325 seconds 
Feb  1 18:58:53 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,370208 seconds 
Feb  1 18:58:54 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,865896 seconds 
Feb  1 18:58:54 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,933192 seconds 
Feb  1 18:58:54 joe acpid: client 22221[0:0] has disconnected
Feb  1 18:58:54 joe acpid: client 22231[0:0] has disconnected
Feb  1 18:58:54 joe acpid: client connected from 22305[0:0]
Feb  1 18:58:54 joe acpid: 1 client rule loaded
Feb  1 18:58:54 joe acpid: client connected from 22306[0:0]
Feb  1 18:58:54 joe acpid: 1 client rule loaded
Feb  1 18:58:54 joe acpid: client connected from 22308[0:0]
Feb  1 18:58:54 joe acpid: 1 client rule loaded
Feb  1 18:59:04 joe acpid: client 22305[0:0] has disconnected
Feb  1 18:59:04 joe acpid: client 22306[0:0] has disconnected
Feb  1 18:59:04 joe acpid: client 22308[0:0] has disconnected
Feb  1 18:59:04 joe acpid: client connected from 22317[0:0]
Feb  1 18:59:04 joe acpid: 1 client rule loaded
Feb  1 18:59:04 joe acpid: client 22317[0:0] has disconnected
Feb  1 18:59:04 joe acpid: client connected from 22314[0:0]
Feb  1 18:59:04 joe acpid: 1 client rule loaded
Feb  1 18:59:04 joe acpid: client 22314[0:0] has disconnected
Feb  1 18:59:04 joe acpid: client connected from 22318[0:0]
Feb  1 18:59:04 joe acpid: 1 client rule loaded
Feb  1 18:59:04 joe acpid: client 22318[0:0] has disconnected
Feb  1 18:59:04 joe acpid: client connected from 22312[0:0]
Feb  1 18:59:04 joe acpid: 1 client rule loaded
Feb  1 18:59:05 joe acpid: client 22312[0:0] has disconnected
Feb  1 18:59:05 joe acpid: client connected from 22315[0:0]
Feb  1 18:59:05 joe acpid: 1 client rule loaded
Feb  1 18:59:05 joe acpid: client 22315[0:0] has disconnected
Feb  1 18:59:05 joe acpid: client connected from 22313[0:0]
Feb  1 18:59:06 joe acpid: 1 client rule loaded
Feb  1 18:59:06 joe acpid: client 22313[0:0] has disconnected
Feb  1 18:59:06 joe acpid: client connected from 22309[0:0]
Feb  1 18:59:06 joe acpid: 1 client rule loaded
Feb  1 18:59:06 joe acpid: client 22309[0:0] has disconnected
Feb  1 18:59:06 joe acpid: client connected from 22316[0:0]
Feb  1 18:59:06 joe acpid: 1 client rule loaded
Feb  1 18:59:06 joe acpid: client connected from 22322[0:0]
Feb  1 18:59:06 joe acpid: 1 client rule loaded
Feb  1 18:59:06 joe acpid: client 22322[0:0] has disconnected
Feb  1 18:59:06 joe acpid: client connected from 22323[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22323[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22326[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22326[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22327[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22327[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22328[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22328[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22332[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22332[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22330[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22330[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22325[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22325[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22333[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22316[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client 22333[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22334[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22334[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22331[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22331[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22335[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22335[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22337[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22337[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22336[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22336[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22340[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22340[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22350[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22350[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22338[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22348[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22320[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22320[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22319[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client 22319[0:0] has disconnected
Feb  1 18:59:07 joe acpid: client connected from 22351[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22343[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22394[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22347[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22349[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22346[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22345[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22342[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22448[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22341[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22392[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22344[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22324[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22439[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22429[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22441[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22443[0:0]
Feb  1 18:59:07 joe acpid: 1 client rule loaded
Feb  1 18:59:07 joe acpid: client connected from 22445[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22444[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22446[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22455[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22460[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22456[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22453[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22458[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22467[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22461[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22454[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22452[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22472[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22491[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22494[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22498[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22500[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22504[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22506[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22532[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22519[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22521[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22534[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22535[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22543[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22545[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22547[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,533424 seconds 
Feb  1 18:59:08 joe acpid: client 22338[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22348[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22351[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22394[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22347[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22349[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22346[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22342[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22341[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22392[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22439[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22429[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22441[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22445[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22444[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22455[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22456[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22453[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22458[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22467[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22461[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22454[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22452[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22472[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22491[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22494[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22498[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22500[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22504[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22506[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22519[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22534[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22535[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22543[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22545[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client connected from 22565[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client 22448[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22443[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22446[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22460[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22532[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22521[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client 22547[0:0] has disconnected
Feb  1 18:59:08 joe acpid: client connected from 22574[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22573[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:08 joe acpid: client connected from 22572[0:0]
Feb  1 18:59:08 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,564902 seconds 
Feb  1 18:59:09 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,591369 seconds 
Feb  1 18:59:09 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,628892 seconds 
Feb  1 18:59:09 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,219884 seconds 
Feb  1 18:59:09 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,000390 seconds 
Feb  1 18:59:09 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,988627 seconds 
Feb  1 18:59:09 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,963630 seconds 
Feb  1 18:59:09 joe acpid: client 22565[0:0] has disconnected
Feb  1 18:59:09 joe acpid: client 22574[0:0] has disconnected
Feb  1 18:59:09 joe acpid: client 22573[0:0] has disconnected
Feb  1 18:59:09 joe acpid: client 22572[0:0] has disconnected
Feb  1 18:59:09 joe acpid: client connected from 22622[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client 22622[0:0] has disconnected
Feb  1 18:59:09 joe acpid: client connected from 22625[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22624[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,203093 seconds 
Feb  1 18:59:09 joe acpid: client connected from 22631[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22633[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22630[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22629[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22640[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client 22624[0:0] has disconnected
Feb  1 18:59:09 joe acpid: client connected from 22644[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client 22625[0:0] has disconnected
Feb  1 18:59:09 joe acpid: client connected from 22639[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22643[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22645[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22637[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22638[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22641[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,329911 seconds 
Feb  1 18:59:09 joe acpid: client connected from 22661[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22662[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22659[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22663[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22658[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22665[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22664[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22671[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22668[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22669[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22683[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:09 joe acpid: client connected from 22684[0:0]
Feb  1 18:59:09 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client connected from 22679[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client connected from 22667[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client connected from 22660[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client connected from 22682[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client connected from 22685[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client connected from 22666[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client connected from 22678[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client connected from 22672[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client connected from 22704[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client 22629[0:0] has disconnected
Feb  1 18:59:10 joe acpid: client connected from 22680[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client 22631[0:0] has disconnected
Feb  1 18:59:10 joe acpid: client connected from 22702[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,584522 seconds 
Feb  1 18:59:10 joe acpid: client connected from 22708[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client connected from 22710[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client connected from 22712[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client connected from 22703[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client connected from 22709[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client 22640[0:0] has disconnected
Feb  1 18:59:10 joe acpid: client 22644[0:0] has disconnected
Feb  1 18:59:10 joe acpid: client connected from 22711[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client 22633[0:0] has disconnected
Feb  1 18:59:10 joe acpid: client connected from 22706[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client connected from 22707[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe acpid: client 22630[0:0] has disconnected
Feb  1 18:59:10 joe acpid: client connected from 22705[0:0]
Feb  1 18:59:10 joe acpid: 1 client rule loaded
Feb  1 18:59:10 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,816313 seconds 
Feb  1 18:59:10 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,892375 seconds 
Feb  1 18:59:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,499703 seconds 
Feb  1 18:59:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,478990 seconds 
Feb  1 18:59:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,458236 seconds 
Feb  1 18:59:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,468690 seconds 
Feb  1 18:59:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,629997 seconds 
Feb  1 18:59:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,605794 seconds 
Feb  1 18:59:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,556818 seconds 
Feb  1 18:59:11 joe acpid: client 22639[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22643[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22645[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22637[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22638[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22641[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22661[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22662[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22659[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22663[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22658[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22665[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22664[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22671[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22668[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22669[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22683[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22684[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22679[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22667[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22660[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22682[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22685[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22666[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22678[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22672[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22704[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22680[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22702[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22708[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22710[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22712[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22703[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22709[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22711[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22706[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22707[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client 22705[0:0] has disconnected
Feb  1 18:59:11 joe acpid: client connected from 22740[0:0]
Feb  1 18:59:11 joe acpid: 1 client rule loaded
Feb  1 18:59:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,574261 seconds 
Feb  1 18:59:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,579847 seconds 
Feb  1 18:59:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,587433 seconds 
Feb  1 18:59:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,603895 seconds 
Feb  1 18:59:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,610686 seconds 
Feb  1 18:59:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,622732 seconds 
Feb  1 18:59:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,620089 seconds 
Feb  1 18:59:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,615674 seconds 
Feb  1 18:59:18 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,632349 seconds 
Feb  1 18:59:19 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,645225 seconds 
Feb  1 18:59:19 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,660914 seconds 
Feb  1 18:59:19 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,666289 seconds 
Feb  1 18:59:19 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,683616 seconds 
Feb  1 18:59:19 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,699563 seconds 
Feb  1 18:59:19 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,694643 seconds 
Feb  1 18:59:19 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,801697 seconds 
Feb  1 18:59:19 joe gnome-session[22093]: WARNING: Failed to start app: Unable to start application: Kindprozess »gnome-power-manager« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) 
Feb  1 18:59:21 joe acpid: client 22740[0:0] has disconnected
Feb  1 18:59:21 joe acpid: client connected from 22841[0:0]
Feb  1 18:59:21 joe acpid: 1 client rule loaded
Feb  1 18:59:21 joe acpid: client 22841[0:0] has disconnected
Feb  1 18:59:21 joe acpid: client connected from 22842[0:0]
Feb  1 18:59:21 joe acpid: 1 client rule loaded
Feb  1 18:59:21 joe acpid: client 22842[0:0] has disconnected
Feb  1 18:59:21 joe acpid: client connected from 22850[0:0]
Feb  1 18:59:21 joe acpid: 1 client rule loaded
Feb  1 18:59:21 joe acpid: client 22850[0:0] has disconnected
Feb  1 18:59:21 joe acpid: client connected from 22858[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client 22858[0:0] has disconnected
Feb  1 18:59:23 joe acpid: client connected from 22854[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client 22854[0:0] has disconnected
Feb  1 18:59:23 joe acpid: client connected from 22855[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client 22855[0:0] has disconnected
Feb  1 18:59:23 joe acpid: client connected from 22856[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client 22856[0:0] has disconnected
Feb  1 18:59:23 joe gdm-simple-greeter[22814]: Gtk-WARNING: Overriding tab label for notebook 
Feb  1 18:59:23 joe acpid: client connected from 22857[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client 22857[0:0] has disconnected
Feb  1 18:59:23 joe acpid: client connected from 22853[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client 22853[0:0] has disconnected
Feb  1 18:59:23 joe gdm-simple-greeter[22814]: Gtk-WARNING: Overriding tab label for notebook 
Feb  1 18:59:23 joe acpid: client connected from 22859[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client 22859[0:0] has disconnected
Feb  1 18:59:23 joe acpid: client connected from 22886[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client 22886[0:0] has disconnected
Feb  1 18:59:23 joe acpid: client connected from 22879[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client 22879[0:0] has disconnected
Feb  1 18:59:23 joe acpid: client connected from 22889[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client 22889[0:0] has disconnected
Feb  1 18:59:23 joe acpid: client connected from 22894[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client 22894[0:0] has disconnected
Feb  1 18:59:23 joe gdm-simple-greeter[22814]: Gtk-WARNING: Overriding tab label for notebook 
Feb  1 18:59:23 joe last message repeated 2 times
Feb  1 18:59:23 joe acpid: client connected from 22874[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client 22874[0:0] has disconnected
Feb  1 18:59:23 joe acpid: client connected from 22882[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client 22882[0:0] has disconnected
Feb  1 18:59:23 joe acpid: client connected from 22897[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client 22897[0:0] has disconnected
Feb  1 18:59:23 joe acpid: client connected from 22872[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client 22872[0:0] has disconnected
Feb  1 18:59:23 joe acpid: client connected from 22898[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client 22898[0:0] has disconnected
Feb  1 18:59:23 joe acpid: client connected from 22860[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client connected from 22888[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client connected from 22878[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:23 joe acpid: client connected from 22893[0:0]
Feb  1 18:59:23 joe acpid: 1 client rule loaded
Feb  1 18:59:26 joe acpid: client connected from 22885[0:0]
Feb  1 18:59:26 joe acpid: 1 client rule loaded
Feb  1 18:59:26 joe acpid: client connected from 22873[0:0]
Feb  1 18:59:26 joe acpid: 1 client rule loaded
Feb  1 18:59:26 joe acpid: client connected from 22895[0:0]
Feb  1 18:59:26 joe acpid: 1 client rule loaded
Feb  1 18:59:26 joe acpid: client connected from 22881[0:0]
Feb  1 18:59:26 joe acpid: 1 client rule loaded
Feb  1 18:59:26 joe acpid: client connected from 22884[0:0]
Feb  1 18:59:26 joe acpid: 1 client rule loaded
Feb  1 18:59:26 joe acpid: client connected from 22875[0:0]
Feb  1 18:59:29 joe acpid: 1 client rule loaded
Feb  1 18:59:29 joe acpid: client 22860[0:0] has disconnected
Feb  1 18:59:29 joe acpid: client 22888[0:0] has disconnected
Feb  1 18:59:29 joe acpid: client 22878[0:0] has disconnected
Feb  1 18:59:29 joe acpid: client 22893[0:0] has disconnected
Feb  1 18:59:29 joe acpid: client 22885[0:0] has disconnected
Feb  1 18:59:29 joe acpid: client 22873[0:0] has disconnected
Feb  1 18:59:29 joe acpid: client 22881[0:0] has disconnected
Feb  1 18:59:29 joe acpid: client 22884[0:0] has disconnected
Feb  1 18:59:29 joe acpid: client 22875[0:0] has disconnected
Feb  1 18:59:29 joe acpid: client connected from 22891[0:0]
Feb  1 18:59:29 joe acpid: 1 client rule loaded
Feb  1 18:59:29 joe acpid: client 22891[0:0] has disconnected
Feb  1 18:59:29 joe acpid: client connected from 22887[0:0]
Feb  1 18:59:29 joe acpid: 1 client rule loaded
Feb  1 18:59:29 joe acpid: client 22887[0:0] has disconnected
Feb  1 18:59:29 joe acpid: client connected from 22915[0:0]
Feb  1 18:59:29 joe acpid: 1 client rule loaded
Feb  1 18:59:29 joe acpid: client 22915[0:0] has disconnected
Feb  1 18:59:29 joe acpid: client connected from 22890[0:0]
Feb  1 18:59:29 joe acpid: 1 client rule loaded
Feb  1 18:59:29 joe acpid: client 22890[0:0] has disconnected
Feb  1 18:59:29 joe acpid: client connected from 22870[0:0]
Feb  1 18:59:29 joe acpid: 1 client rule loaded
Feb  1 18:59:29 joe acpid: client 22870[0:0] has disconnected
Feb  1 18:59:29 joe acpid: client connected from 22896[0:0]
Feb  1 18:59:29 joe gdm-simple-greeter[22814]: Gtk-WARNING: /build/buildd-gtk+3.0_3.2.3-1-i386-GA85Ik/gtk+3.0-3.2.3/./gtk/gtkwidget.c:6857: widget not within a GtkWindow 
Feb  1 18:59:31 joe acpid: 1 client rule loaded
Feb  1 18:59:31 joe acpid: client 22896[0:0] has disconnected
Feb  1 18:59:31 joe acpid: client connected from 22864[0:0]
Feb  1 18:59:31 joe acpid: 1 client rule loaded
Feb  1 18:59:31 joe acpid: client 22864[0:0] has disconnected
Feb  1 18:59:31 joe acpid: client connected from 22865[0:0]
Feb  1 18:59:31 joe acpid: 1 client rule loaded
Feb  1 18:59:31 joe acpid: client 22865[0:0] has disconnected
Feb  1 18:59:31 joe acpid: client connected from 22866[0:0]
Feb  1 18:59:31 joe acpid: 1 client rule loaded
Feb  1 18:59:31 joe acpid: client 22866[0:0] has disconnected
Feb  1 18:59:31 joe acpid: client connected from 22868[0:0]
Feb  1 18:59:31 joe acpid: 1 client rule loaded
Feb  1 18:59:31 joe acpid: client 22868[0:0] has disconnected
Feb  1 18:59:31 joe acpid: client connected from 22862[0:0]
Feb  1 18:59:31 joe acpid: 1 client rule loaded
Feb  1 18:59:31 joe acpid: client 22862[0:0] has disconnected
Feb  1 18:59:31 joe acpid: client connected from 22863[0:0]
Feb  1 18:59:31 joe acpid: 1 client rule loaded
Feb  1 18:59:31 joe acpid: client 22863[0:0] has disconnected
Feb  1 18:59:31 joe acpid: client connected from 22867[0:0]
Feb  1 18:59:31 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client 22867[0:0] has disconnected
Feb  1 18:59:32 joe acpid: client connected from 22861[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client 22861[0:0] has disconnected
Feb  1 18:59:32 joe acpid: client connected from 22880[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client 22880[0:0] has disconnected
Feb  1 18:59:32 joe acpid: client connected from 22877[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client 22877[0:0] has disconnected
Feb  1 18:59:32 joe acpid: client connected from 22883[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client 22883[0:0] has disconnected
Feb  1 18:59:32 joe acpid: client connected from 22871[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client 22871[0:0] has disconnected
Feb  1 18:59:32 joe acpid: client connected from 22906[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client 22906[0:0] has disconnected
Feb  1 18:59:32 joe acpid: client connected from 22917[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client 22917[0:0] has disconnected
Feb  1 18:59:32 joe acpid: client connected from 22924[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client 22924[0:0] has disconnected
Feb  1 18:59:32 joe acpid: client connected from 22913[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client 22913[0:0] has disconnected
Feb  1 18:59:32 joe acpid: client connected from 22892[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client 22892[0:0] has disconnected
Feb  1 18:59:32 joe acpid: client connected from 22876[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client 22876[0:0] has disconnected
Feb  1 18:59:32 joe acpid: client connected from 22905[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client 22905[0:0] has disconnected
Feb  1 18:59:32 joe acpid: client connected from 22869[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client 22869[0:0] has disconnected
Feb  1 18:59:32 joe acpid: client connected from 22902[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client 22902[0:0] has disconnected
Feb  1 18:59:32 joe acpid: client connected from 22918[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client 22918[0:0] has disconnected
Feb  1 18:59:32 joe acpid: client connected from 22920[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22916[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22927[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22911[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22912[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22909[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22928[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22926[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22899[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22925[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22919[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22901[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22907[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22923[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22921[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22903[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22908[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22914[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22910[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22900[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23021[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22922[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 22904[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23020[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23024[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23027[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23029[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23026[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23030[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23031[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23036[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23022[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23044[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23043[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23038[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23037[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23053[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23055[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23059[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23057[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23086[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23093[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23091[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23088[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23087[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23090[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23098[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23096[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23100[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23102[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23110[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23101[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23111[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23109[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23106[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23120[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23107[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23121[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23119[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23117[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23130[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23151[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:32 joe acpid: client connected from 23150[0:0]
Feb  1 18:59:32 joe acpid: 1 client rule loaded
Feb  1 18:59:33 joe acpid: client connected from 23152[0:0]
Feb  1 18:59:33 joe acpid: 1 client rule loaded
Feb  1 18:59:33 joe acpid: client connected from 23154[0:0]
Feb  1 18:59:33 joe acpid: 1 client rule loaded
Feb  1 18:59:33 joe acpid: client connected from 23160[0:0]
Feb  1 18:59:33 joe acpid: 1 client rule loaded
Feb  1 18:59:33 joe acpid: client connected from 23155[0:0]
Feb  1 18:59:33 joe acpid: 1 client rule loaded
Feb  1 18:59:33 joe acpid: client connected from 23161[0:0]
Feb  1 18:59:33 joe acpid: 1 client rule loaded
Feb  1 18:59:33 joe acpid: client connected from 23162[0:0]
Feb  1 18:59:33 joe acpid: 1 client rule loaded
Feb  1 18:59:33 joe acpid: client connected from 23175[0:0]
Feb  1 18:59:33 joe acpid: 1 client rule loaded
Feb  1 18:59:33 joe acpid: client connected from 23180[0:0]
Feb  1 18:59:33 joe acpid: 1 client rule loaded
Feb  1 18:59:33 joe acpid: client connected from 23182[0:0]
Feb  1 18:59:33 joe acpid: 1 client rule loaded
Feb  1 18:59:33 joe acpid: client connected from 23184[0:0]
Feb  1 18:59:33 joe acpid: 1 client rule loaded
Feb  1 18:59:33 joe acpid: client connected from 23191[0:0]
Feb  1 18:59:33 joe acpid: 1 client rule loaded
Feb  1 18:59:33 joe acpid: client connected from 23193[0:0]
Feb  1 18:59:33 joe acpid: 1 client rule loaded
Feb  1 18:59:33 joe acpid: client connected from 23195[0:0]
Feb  1 18:59:33 joe acpid: 1 client rule loaded
Feb  1 18:59:33 joe acpid: client connected from 23197[0:0]
Feb  1 18:59:33 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client 22895[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 22911[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 22926[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 22908[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23021[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23020[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23024[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23027[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23029[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23026[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23030[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23031[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23036[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23022[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23044[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23043[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23037[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23053[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23055[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23059[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23057[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23088[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23098[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client 23111[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client connected from 23248[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23249[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23252[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23253[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23262[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23273[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23260[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23264[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23265[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23255[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23268[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23274[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23267[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23289[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23291[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23270[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23258[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23257[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23272[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23261[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23256[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23266[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client connected from 23269[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe acpid: client 23248[0:0] has disconnected
Feb  1 18:59:34 joe acpid: client connected from 23294[0:0]
Feb  1 18:59:34 joe acpid: 1 client rule loaded
Feb  1 18:59:34 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,048640 seconds 
Feb  1 18:59:34 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,743397 seconds 
Feb  1 18:59:34 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,188342 seconds 
Feb  1 18:59:34 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,734172 seconds 
Feb  1 18:59:34 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,164203 seconds 
Feb  1 18:59:34 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,155361 seconds 
Feb  1 18:59:34 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,124734 seconds 
Feb  1 18:59:34 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,097519 seconds 
Feb  1 18:59:35 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,473451 seconds 
Feb  1 18:59:35 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,489944 seconds 
Feb  1 18:59:35 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,496461 seconds 
Feb  1 18:59:35 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,496014 seconds 
Feb  1 18:59:35 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,559440 seconds 
Feb  1 18:59:35 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,603200 seconds 
Feb  1 18:59:35 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,975954 seconds 
Feb  1 18:59:35 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,002517 seconds 
Feb  1 18:59:35 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,154228 seconds 
Feb  1 18:59:35 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,163901 seconds 
Feb  1 18:59:35 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,174051 seconds 
Feb  1 18:59:36 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,192656 seconds 
Feb  1 18:59:36 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,209396 seconds 
Feb  1 18:59:36 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,413384 seconds 
Feb  1 18:59:36 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,438810 seconds 
Feb  1 18:59:36 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,463191 seconds 
Feb  1 18:59:36 joe acpid: client 23249[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23252[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23253[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23262[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23273[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23260[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23264[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23265[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23255[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23268[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23274[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23267[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23289[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23291[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23270[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23258[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23257[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23272[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23261[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23256[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23266[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23269[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client 23294[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client connected from 23350[0:0]
Feb  1 18:59:36 joe acpid: 1 client rule loaded
Feb  1 18:59:36 joe acpid: client connected from 23352[0:0]
Feb  1 18:59:36 joe acpid: 1 client rule loaded
Feb  1 18:59:36 joe acpid: client connected from 23353[0:0]
Feb  1 18:59:36 joe acpid: 1 client rule loaded
Feb  1 18:59:36 joe acpid: client 23350[0:0] has disconnected
Feb  1 18:59:36 joe acpid: client connected from 23358[0:0]
Feb  1 18:59:36 joe acpid: 1 client rule loaded
Feb  1 18:59:36 joe acpid: client connected from 23359[0:0]
Feb  1 18:59:36 joe acpid: 1 client rule loaded
Feb  1 18:59:36 joe acpid: client connected from 23362[0:0]
Feb  1 18:59:36 joe acpid: 1 client rule loaded
Feb  1 18:59:36 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,409043 seconds 
Feb  1 18:59:41 joe acpid: client 23352[0:0] has disconnected
Feb  1 18:59:41 joe acpid: client 23353[0:0] has disconnected
Feb  1 18:59:41 joe acpid: client 23359[0:0] has disconnected
Feb  1 18:59:41 joe acpid: client 23362[0:0] has disconnected
Feb  1 18:59:41 joe acpid: client connected from 23357[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23368[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23366[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23375[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client 23368[0:0] has disconnected
Feb  1 18:59:41 joe acpid: client connected from 23370[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23369[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23379[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23360[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23367[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23371[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23376[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23364[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,614650 seconds 
Feb  1 18:59:41 joe acpid: client connected from 23378[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23361[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23373[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23363[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23381[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23386[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23374[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23392[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23389[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23390[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23391[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23387[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23394[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23428[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:41 joe acpid: client connected from 23429[0:0]
Feb  1 18:59:41 joe acpid: 1 client rule loaded
Feb  1 18:59:46 joe acpid: client 23375[0:0] has disconnected
Feb  1 18:59:46 joe acpid: client connected from 23380[0:0]
Feb  1 18:59:46 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client 23360[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23373[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23386[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23428[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23380[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client connected from 23426[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client 23358[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23357[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23366[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23370[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23369[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23379[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23367[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23371[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23376[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23364[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23378[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23361[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23363[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23381[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23374[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client connected from 23393[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23427[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23433[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23435[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23425[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23388[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23430[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client 23430[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client connected from 23434[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23395[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23432[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client 23432[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client connected from 23470[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client 23470[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client connected from 23506[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23502[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23510[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23504[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23508[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23520[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23519[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23515[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23513[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23517[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23521[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23530[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23522[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23516[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23512[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23533[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23539[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23536[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23531[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23546[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23548[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23542[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23547[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23538[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23549[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23544[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23545[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23540[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23541[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23543[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client 23515[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23530[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23522[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client 23516[0:0] has disconnected
Feb  1 18:59:47 joe acpid: client connected from 23537[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23534[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23535[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:47 joe acpid: client connected from 23570[0:0]
Feb  1 18:59:47 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,791543 seconds 
Feb  1 18:59:48 joe acpid: client 23506[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23510[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23504[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23508[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23520[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23519[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23517[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23521[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23512[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23533[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23539[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23536[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23531[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23546[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23548[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23542[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23547[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23538[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23549[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23544[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23545[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23540[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23541[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23543[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23537[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23534[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23535[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client 23570[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client connected from 23612[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23613[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client 23612[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client connected from 23621[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23616[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23617[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,740565 seconds 
Feb  1 18:59:48 joe acpid: client connected from 23619[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23627[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23628[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23626[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23622[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23625[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23620[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23645[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23618[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23623[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23630[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23629[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23646[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23644[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23650[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23654[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23655[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23659[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23661[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23663[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client 23613[0:0] has disconnected
Feb  1 18:59:48 joe acpid: client connected from 23664[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23662[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23668[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23660[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe acpid: client connected from 23665[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,753501 seconds 
Feb  1 18:59:48 joe acpid: client connected from 23658[0:0]
Feb  1 18:59:48 joe acpid: 1 client rule loaded
Feb  1 18:59:48 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,913725 seconds 
Feb  1 18:59:49 joe gdm-simple-greeter[22814]: Gtk-CRITICAL: gtk_widget_get_preferred_height_for_width: assertion `width >= 0' failed 
Feb  1 18:59:49 joe gdm-simple-greeter[22814]: Gtk-WARNING: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height -3 
Feb  1 18:59:49 joe gdm-simple-greeter[22814]: Gtk-CRITICAL: gtk_widget_get_preferred_height_for_width: assertion `width >= 0' failed 
Feb  1 18:59:49 joe gdm-simple-greeter[22814]: Gtk-CRITICAL: gtk_widget_get_preferred_height_for_width: assertion `width >= 0' failed 
Feb  1 18:59:49 joe gdm-simple-greeter[22814]: Gtk-WARNING: gtk_widget_size_allocate(): attempt to allocate widget with width -47 and height -47 
Feb  1 18:59:49 joe acpid: client 23621[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23616[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23617[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23619[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23627[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23628[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23626[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23622[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23625[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23620[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23645[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23618[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23623[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23630[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23629[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23646[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23644[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23650[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23654[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23655[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23659[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23661[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23663[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23664[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23662[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23668[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23660[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23665[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client 23658[0:0] has disconnected
Feb  1 18:59:49 joe acpid: client connected from 23671[0:0]
Feb  1 18:59:49 joe acpid: 1 client rule loaded
Feb  1 18:59:49 joe acpid: client connected from 23669[0:0]
Feb  1 18:59:49 joe acpid: 1 client rule loaded
Feb  1 18:59:49 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,238584 seconds 
Feb  1 18:59:49 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,209850 seconds 
Feb  1 18:59:49 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,226980 seconds 
Feb  1 18:59:49 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,231222 seconds 
Feb  1 18:59:49 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,423241 seconds 
Feb  1 18:59:49 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,450073 seconds 
Feb  1 18:59:49 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,472987 seconds 
Feb  1 18:59:49 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,494624 seconds 
Feb  1 18:59:49 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,520232 seconds 
Feb  1 18:59:49 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,544768 seconds 
Feb  1 18:59:49 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,547446 seconds 
Feb  1 18:59:49 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,553620 seconds 
Feb  1 18:59:49 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,557650 seconds 
Feb  1 18:59:49 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,554592 seconds 
Feb  1 18:59:49 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,559410 seconds 
Feb  1 18:59:49 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,562142 seconds 
Feb  1 18:59:50 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,870783 seconds 
Feb  1 18:59:50 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,887528 seconds 
Feb  1 18:59:50 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,891219 seconds 
Feb  1 18:59:50 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,900428 seconds 
Feb  1 18:59:50 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,910985 seconds 
Feb  1 18:59:50 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,918901 seconds 
Feb  1 18:59:50 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,555495 seconds 
Feb  1 18:59:50 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,597465 seconds 
Feb  1 18:59:51 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,611706 seconds 
Feb  1 18:59:51 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,803106 seconds 
Feb  1 18:59:51 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,811150 seconds 
Feb  1 18:59:51 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,879290 seconds 
Feb  1 18:59:51 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,916027 seconds 
Feb  1 18:59:51 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,933311 seconds 
Feb  1 18:59:51 joe acpid: client 23671[0:0] has disconnected
Feb  1 18:59:51 joe acpid: client 23669[0:0] has disconnected
Feb  1 18:59:51 joe acpid: client connected from 23746[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:51 joe acpid: client connected from 23749[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:51 joe acpid: client connected from 23748[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:51 joe acpid: client connected from 23750[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:51 joe acpid: client 23746[0:0] has disconnected
Feb  1 18:59:51 joe acpid: client connected from 23751[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:51 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,993326 seconds 
Feb  1 18:59:51 joe acpid: client connected from 23759[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:51 joe acpid: client connected from 23762[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:51 joe acpid: client connected from 23760[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:51 joe acpid: client connected from 23765[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:51 joe acpid: client connected from 23758[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:51 joe acpid: client 23749[0:0] has disconnected
Feb  1 18:59:51 joe acpid: client 23748[0:0] has disconnected
Feb  1 18:59:51 joe acpid: client 23750[0:0] has disconnected
Feb  1 18:59:51 joe acpid: client 23751[0:0] has disconnected
Feb  1 18:59:51 joe acpid: client 23759[0:0] has disconnected
Feb  1 18:59:51 joe acpid: client 23762[0:0] has disconnected
Feb  1 18:59:51 joe acpid: client 23760[0:0] has disconnected
Feb  1 18:59:51 joe acpid: client 23765[0:0] has disconnected
Feb  1 18:59:51 joe acpid: client 23758[0:0] has disconnected
Feb  1 18:59:51 joe acpid: client connected from 23761[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:51 joe acpid: client connected from 23763[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:51 joe acpid: client 23761[0:0] has disconnected
Feb  1 18:59:51 joe acpid: client 23763[0:0] has disconnected
Feb  1 18:59:51 joe acpid: client connected from 23764[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:51 joe acpid: client connected from 23757[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:51 joe acpid: client connected from 23776[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:51 joe acpid: client connected from 23779[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:51 joe acpid: client connected from 23782[0:0]
Feb  1 18:59:51 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client 23764[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client 23757[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client 23776[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client 23779[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client 23782[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client connected from 23777[0:0]
Feb  1 18:59:59 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client connected from 23785[0:0]
Feb  1 18:59:59 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client 23777[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client 23785[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client connected from 23790[0:0]
Feb  1 18:59:59 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client 23790[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client connected from 23784[0:0]
Feb  1 18:59:59 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client 23784[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client connected from 23791[0:0]
Feb  1 18:59:59 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client 23791[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client connected from 23796[0:0]
Feb  1 18:59:59 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client 23796[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client connected from 23797[0:0]
Feb  1 18:59:59 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client 23797[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client connected from 23780[0:0]
Feb  1 18:59:59 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client 23780[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client connected from 23804[0:0]
Feb  1 18:59:59 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client 23804[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client connected from 23789[0:0]
Feb  1 18:59:59 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client 23789[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client connected from 23805[0:0]
Feb  1 18:59:59 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client 23805[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client connected from 23806[0:0]
Feb  1 18:59:59 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client 23806[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client connected from 23793[0:0]
Feb  1 18:59:59 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client 23793[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client connected from 23807[0:0]
Feb  1 18:59:59 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client 23807[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client connected from 23786[0:0]
Feb  1 18:59:59 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client 23786[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client connected from 23783[0:0]
Feb  1 18:59:59 joe acpid: 1 client rule loaded
Feb  1 18:59:59 joe acpid: client 23783[0:0] has disconnected
Feb  1 18:59:59 joe acpid: client connected from 23794[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client 23794[0:0] has disconnected
Feb  1 19:00:00 joe acpid: client connected from 23803[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23799[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23802[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23787[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23800[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23798[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23795[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23857[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23778[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23861[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23860[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23865[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23867[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23858[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23864[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23863[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23862[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23859[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23856[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23855[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23869[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23871[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23872[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23873[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23897[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23870[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23900[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23896[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23868[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23926[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23904[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23906[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23902[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23910[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23908[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23920[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23913[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23925[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23911[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23909[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23921[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23914[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23923[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23924[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23918[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23915[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23919[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23917[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23927[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23922[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23966[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client 23795[0:0] has disconnected
Feb  1 19:00:00 joe acpid: client connected from 23962[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23963[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23974[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23965[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23968[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23967[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23971[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23977[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23969[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23973[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23984[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23986[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23997[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 23999[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 24001[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:00 joe acpid: client connected from 24004[0:0]
Feb  1 19:00:00 joe acpid: 1 client rule loaded
Feb  1 19:00:01 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,922588 seconds 
Feb  1 19:00:01 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,906687 seconds 
Feb  1 19:00:01 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,913888 seconds 
Feb  1 19:00:01 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,616967 seconds 
Feb  1 19:00:01 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,271676 seconds 
Feb  1 19:00:01 joe acpid: client 23803[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23799[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23802[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23787[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23800[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23798[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23857[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23778[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23861[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23860[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23865[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23867[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23858[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23864[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23863[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23862[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23859[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23856[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23855[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23869[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23871[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23872[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23873[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23897[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23870[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23900[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23896[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23868[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23926[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23904[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23906[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23902[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23910[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23908[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23920[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23913[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23925[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23911[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23909[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23921[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23914[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23923[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23924[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23918[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23915[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23919[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23917[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23927[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23922[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23966[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23962[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23963[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23974[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23965[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23968[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23967[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23971[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23977[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23969[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23973[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23984[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23986[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23997[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 23999[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 24001[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client 24004[0:0] has disconnected
Feb  1 19:00:01 joe acpid: client connected from 24202[0:0]
Feb  1 19:00:01 joe acpid: 1 client rule loaded
Feb  1 19:00:01 joe acpid: client connected from 24216[0:0]
Feb  1 19:00:01 joe acpid: 1 client rule loaded
Feb  1 19:00:01 joe acpid: client connected from 24183[0:0]
Feb  1 19:00:01 joe acpid: 1 client rule loaded
Feb  1 19:00:01 joe acpid: client connected from 24209[0:0]
Feb  1 19:00:01 joe acpid: 1 client rule loaded
Feb  1 19:00:01 joe acpid: client connected from 24166[0:0]
Feb  1 19:00:01 joe acpid: 1 client rule loaded
Feb  1 19:00:01 joe acpid: client connected from 24210[0:0]
Feb  1 19:00:01 joe acpid: 1 client rule loaded
Feb  1 19:00:01 joe acpid: client connected from 24208[0:0]
Feb  1 19:00:01 joe acpid: 1 client rule loaded
Feb  1 19:00:01 joe acpid: client connected from 24177[0:0]
Feb  1 19:00:01 joe acpid: 1 client rule loaded
Feb  1 19:00:01 joe acpid: client connected from 24205[0:0]
Feb  1 19:00:01 joe acpid: 1 client rule loaded
Feb  1 19:00:01 joe acpid: client connected from 24095[0:0]
Feb  1 19:00:01 joe acpid: 1 client rule loaded
Feb  1 19:00:01 joe acpid: client connected from 24096[0:0]
Feb  1 19:00:01 joe acpid: 1 client rule loaded
Feb  1 19:00:01 joe acpid: client connected from 24206[0:0]
Feb  1 19:00:01 joe acpid: 1 client rule loaded
Feb  1 19:00:01 joe acpid: client connected from 24098[0:0]
Feb  1 19:00:01 joe acpid: 1 client rule loaded
Feb  1 19:00:01 joe acpid: client connected from 24176[0:0]
Feb  1 19:00:01 joe acpid: 1 client rule loaded
Feb  1 19:00:01 joe acpid: client connected from 24097[0:0]
Feb  1 19:00:01 joe acpid: 1 client rule loaded
Feb  1 19:00:01 joe acpid: client connected from 24102[0:0]
Feb  1 19:00:01 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24218[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24175[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24198[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24172[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24170[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24179[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24163[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24178[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24164[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24213[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24173[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24197[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24160[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24169[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24155[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24167[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24152[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24162[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24149[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24159[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24134[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24150[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24153[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24138[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24156[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24089[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24137[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24090[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24201[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24139[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24081[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24082[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24136[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24128[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24083[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24126[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24079[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24131[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24118[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24119[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24092[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24130[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24105[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24100[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24124[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24107[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24122[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24101[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24117[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24106[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24215[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24127[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24093[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24121[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24180[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe acpid: client connected from 24080[0:0]
Feb  1 19:00:02 joe acpid: 1 client rule loaded
Feb  1 19:00:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,544462 seconds 
Feb  1 19:00:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,617112 seconds 
Feb  1 19:00:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,809149 seconds 
Feb  1 19:00:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,896482 seconds 
Feb  1 19:00:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,691382 seconds 
Feb  1 19:00:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,331632 seconds 
Feb  1 19:00:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,300824 seconds 
Feb  1 19:00:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,254995 seconds 
Feb  1 19:00:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,191830 seconds 
Feb  1 19:00:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,218755 seconds 
Feb  1 19:00:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,244928 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,257701 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,279509 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,299830 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,317242 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,338358 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,367599 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,391605 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,417646 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,459728 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,491356 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,528591 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,549267 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,569598 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,602731 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,631236 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,636115 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,653684 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,757785 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,773847 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,789169 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,797362 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,816673 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,831993 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,847901 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,860518 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,914567 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,931554 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,949959 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,967522 seconds 
Feb  1 19:00:03 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,986898 seconds 
Feb  1 19:00:04 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,972080 seconds 
Feb  1 19:00:04 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,981446 seconds 
Feb  1 19:00:04 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,992794 seconds 
Feb  1 19:00:16 joe acpid: client 24202[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24216[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24183[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24209[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24166[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24210[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24208[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24177[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24205[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24095[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24096[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24206[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24098[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24176[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24097[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24102[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24218[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24175[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24198[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24172[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24170[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24179[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24163[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24178[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24164[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24213[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24173[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24197[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24160[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24169[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24155[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24167[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24152[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24162[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24149[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24159[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24134[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24150[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24153[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24138[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24156[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24089[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24137[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24090[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24201[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24139[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24081[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24082[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24136[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24128[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24083[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24126[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24079[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24131[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24118[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24119[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24092[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24130[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24105[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24100[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24124[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24107[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24122[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24101[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24117[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24106[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24215[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24127[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24093[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24121[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24180[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client 24080[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client connected from 24420[0:0]
Feb  1 19:00:16 joe acpid: 1 client rule loaded
Feb  1 19:00:16 joe acpid: client 24420[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client connected from 24424[0:0]
Feb  1 19:00:16 joe acpid: 1 client rule loaded
Feb  1 19:00:16 joe acpid: client 24424[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client connected from 24423[0:0]
Feb  1 19:00:16 joe acpid: 1 client rule loaded
Feb  1 19:00:16 joe acpid: client 24423[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client connected from 24415[0:0]
Feb  1 19:00:16 joe acpid: 1 client rule loaded
Feb  1 19:00:16 joe acpid: client 24415[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client connected from 24413[0:0]
Feb  1 19:00:16 joe acpid: 1 client rule loaded
Feb  1 19:00:16 joe acpid: client 24413[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client connected from 24419[0:0]
Feb  1 19:00:16 joe acpid: 1 client rule loaded
Feb  1 19:00:16 joe acpid: client 24419[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client connected from 24410[0:0]
Feb  1 19:00:16 joe acpid: 1 client rule loaded
Feb  1 19:00:16 joe acpid: client 24410[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client connected from 24405[0:0]
Feb  1 19:00:16 joe acpid: 1 client rule loaded
Feb  1 19:00:16 joe acpid: client 24405[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client connected from 24414[0:0]
Feb  1 19:00:16 joe acpid: 1 client rule loaded
Feb  1 19:00:16 joe acpid: client 24414[0:0] has disconnected
Feb  1 19:00:16 joe acpid: client connected from 24425[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client 24425[0:0] has disconnected
Feb  1 19:00:17 joe acpid: client connected from 24377[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client 24377[0:0] has disconnected
Feb  1 19:00:17 joe acpid: client connected from 24391[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24395[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24364[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24396[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24407[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24402[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24380[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24409[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24411[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24386[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24379[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24390[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24378[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24383[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24371[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24348[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24389[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24354[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24398[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24357[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24366[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24349[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24372[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24382[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24356[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24365[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24363[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24381[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24359[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24360[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24368[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24392[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24399[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24369[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24375[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24370[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24397[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24385[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24361[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24367[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24406[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24408[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24373[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24421[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24351[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24350[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24352[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24400[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24353[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24374[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24401[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24418[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24384[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24347[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24404[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24362[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24453[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24417[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24444[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24441[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24439[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24429[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24457[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24427[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24430[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24459[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24434[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24435[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24450[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24452[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24455[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24448[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24387[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24432[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24443[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24442[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24456[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24447[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24458[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24440[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24454[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24376[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24445[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24416[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24393[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24355[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24451[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24403[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24422[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24433[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24462[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24436[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24394[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24412[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24446[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24388[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24460[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24358[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24461[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24431[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24437[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24449[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24438[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24426[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24428[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24591[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24593[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24601[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24594[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24596[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24599[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24603[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24598[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24605[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24602[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:17 joe acpid: client connected from 24610[0:0]
Feb  1 19:00:17 joe acpid: 1 client rule loaded
Feb  1 19:00:33 joe acpid: client 24391[0:0] has disconnected
Feb  1 19:00:33 joe acpid: client 24395[0:0] has disconnected
Feb  1 19:00:33 joe acpid: client 24364[0:0] has disconnected
Feb  1 19:00:33 joe acpid: client 24396[0:0] has disconnected
Feb  1 19:00:33 joe acpid: client 24407[0:0] has disconnected
Feb  1 19:00:33 joe acpid: client 24402[0:0] has disconnected
Feb  1 19:00:33 joe acpid: client 24380[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24409[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24411[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24386[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24379[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24390[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24378[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24383[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24371[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24348[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24389[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24354[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24398[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24357[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24366[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24349[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24372[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24382[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24356[0:0] has disconnected
Feb  1 19:00:34 joe acpid: client 24365[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24363[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24381[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24359[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24360[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24368[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24392[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24399[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24369[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24375[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24370[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24397[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24385[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24361[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24367[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24406[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24408[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24373[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24421[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24351[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24350[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24352[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24400[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24353[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24374[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24401[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24418[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24384[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24347[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24404[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24362[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24453[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24417[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24444[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24441[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24439[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24429[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24457[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24427[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24430[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24459[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24434[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24435[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24450[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24452[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24455[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24448[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24387[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24432[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24443[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24442[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24456[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24447[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24458[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24440[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24454[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24376[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24445[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24416[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24393[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24355[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24451[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24403[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24422[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24433[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24462[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24436[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24394[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24412[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24446[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24388[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24460[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24358[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24461[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24431[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24437[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24449[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24438[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24426[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24428[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24591[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24593[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24601[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24594[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24596[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24599[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24603[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24598[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24605[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24602[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24610[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24767[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24767[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24768[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24768[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24772[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24772[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24773[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24773[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24779[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24779[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24770[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24770[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24782[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24782[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24784[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24784[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24787[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24787[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24789[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24789[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24793[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24793[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24796[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24821[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24790[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24794[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24781[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24780[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24776[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24786[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24788[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24819[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24769[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24826[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24791[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24783[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24830[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24817[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24815[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24771[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24818[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24823[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24816[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24813[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24775[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24824[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24843[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24849[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24827[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24844[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24845[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24825[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24847[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24851[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24848[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24828[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24850[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24829[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24852[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24865[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24875[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24868[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24867[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24871[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24874[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24883[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24877[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24878[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24880[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24869[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24876[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24881[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24882[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24872[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24889[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24891[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24887[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24888[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24879[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24885[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24886[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24910[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24911[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24909[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24920[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24815[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24813[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24845[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24825[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24878[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24912[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24914[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24917[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24916[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24918[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24929[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24930[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24927[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24817[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24818[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24849[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24827[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24847[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24851[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24879[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24886[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24928[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24796[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24821[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24790[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24781[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24776[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24786[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24788[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24769[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24791[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24783[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24771[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24824[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24844[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24848[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24828[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24850[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24865[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24875[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24871[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24877[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24880[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24876[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24917[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24935[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24941[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24941[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24938[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24945[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24936[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24944[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24946[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24940[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24949[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24948[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24937[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24942[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24947[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24950[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24958[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client connected from 24952[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24780[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24826[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24823[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24775[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24852[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24874[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24883[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24869[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24887[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24916[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24936[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24954[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24816[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24867[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24882[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24955[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24830[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24953[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24794[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client connected from 24977[0:0]
Feb  1 19:00:35 joe acpid: 1 client rule loaded
Feb  1 19:00:35 joe acpid: client 24889[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24891[0:0] has disconnected
Feb  1 19:00:35 joe acpid: client 24888[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client connected from 24976[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client 24881[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24872[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24929[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client connected from 24979[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client 24819[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24843[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24829[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24868[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24885[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24910[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24911[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24909[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24920[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24912[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24914[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24918[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24930[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24928[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24938[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24944[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24948[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24950[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24958[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24954[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24976[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24979[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client connected from 24975[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client 24935[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24945[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24946[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24940[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client connected from 24983[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client 24952[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client connected from 24957[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 24980[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 24984[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 24981[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 24990[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 24989[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 24994[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 24995[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client 24975[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client connected from 24822[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client 24927[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24949[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24937[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24942[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24947[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24955[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24953[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24977[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24983[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client 24980[0:0] has disconnected
Feb  1 19:00:36 joe acpid: client connected from 25014[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 25018[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 25019[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 25015[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 25021[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 25028[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 25027[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 25024[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 25025[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 25016[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:36 joe acpid: client connected from 25034[0:0]
Feb  1 19:00:36 joe acpid: 1 client rule loaded
Feb  1 19:00:37 joe acpid: client 24957[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 24984[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 24981[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 24990[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 24989[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 24994[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 24995[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 24822[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 25014[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 25018[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 25019[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 25015[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 25021[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 25028[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 25027[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 25024[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 25025[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 25016[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client 25034[0:0] has disconnected
Feb  1 19:00:37 joe acpid: client connected from 25173[0:0]
Feb  1 19:00:37 joe acpid: 1 client rule loaded
Feb  1 19:00:37 joe acpid: client connected from 25172[0:0]
Feb  1 19:00:37 joe acpid: 1 client rule loaded
Feb  1 19:00:37 joe acpid: client connected from 25171[0:0]
Feb  1 19:00:37 joe acpid: 1 client rule loaded
Feb  1 19:00:37 joe acpid: client connected from 25187[0:0]
Feb  1 19:00:37 joe acpid: 1 client rule loaded
Feb  1 19:00:37 joe acpid: client connected from 25190[0:0]
Feb  1 19:00:37 joe acpid: 1 client rule loaded
Feb  1 19:00:37 joe acpid: client connected from 25188[0:0]
Feb  1 19:00:37 joe acpid: 1 client rule loaded
Feb  1 19:00:37 joe acpid: client connected from 25179[0:0]
Feb  1 19:00:37 joe acpid: 1 client rule loaded
Feb  1 19:00:37 joe acpid: client connected from 25178[0:0]
Feb  1 19:00:37 joe acpid: 1 client rule loaded
Feb  1 19:00:37 joe acpid: client connected from 25198[0:0]
Feb  1 19:00:37 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25205[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25186[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25184[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25183[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25193[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client 25173[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client connected from 25194[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25199[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25195[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25185[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25204[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25206[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25202[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25196[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25191[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25201[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25207[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25177[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25181[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25182[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25192[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25180[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25200[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25244[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25237[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25239[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25241[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client 25171[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client connected from 25245[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25234[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25235[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25251[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25253[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,426410 seconds 
Feb  1 19:00:38 joe acpid: client connected from 25238[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25247[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client 25172[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client connected from 25248[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25250[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25236[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25246[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25242[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25240[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25249[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25252[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,809422 seconds 
Feb  1 19:00:38 joe acpid: client connected from 25233[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25313[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25279[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25274[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25312[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25314[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25305[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25310[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25324[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25330[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25315[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25311[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25326[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25276[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25280[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25282[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25284[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25281[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25278[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25277[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client 25178[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client connected from 25286[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client 25179[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client connected from 25273[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25243[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25328[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25285[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client 25187[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25191[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client connected from 25283[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25308[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25303[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25306[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25307[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client 25190[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client connected from 25309[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25327[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client 25186[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25185[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client connected from 25302[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client 25188[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25177[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client connected from 25304[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client 25194[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25182[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client connected from 25325[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,980725 seconds 
Feb  1 19:00:38 joe acpid: client connected from 25329[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client 25198[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25205[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25184[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25183[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25193[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25199[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25195[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25204[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25206[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25202[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25196[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25201[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25207[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25181[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25192[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25180[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25200[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25244[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25237[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25241[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25245[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25238[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client 25247[0:0] has disconnected
Feb  1 19:00:38 joe acpid: client connected from 25349[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25350[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:38 joe acpid: client connected from 25348[0:0]
Feb  1 19:00:38 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,975628 seconds 
Feb  1 19:00:39 joe acpid: client 25239[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25234[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25235[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25251[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25253[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25248[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25250[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25236[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25246[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25242[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25240[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25249[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25252[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25233[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25313[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25279[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25274[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25312[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25314[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25305[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25310[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25324[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25330[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25315[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25311[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25326[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25276[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25280[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25282[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25284[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25281[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25278[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25277[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25286[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25273[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25243[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25328[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25285[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25283[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25308[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25303[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25306[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25307[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25309[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25327[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25302[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25304[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25325[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25329[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25349[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25350[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client 25348[0:0] has disconnected
Feb  1 19:00:39 joe acpid: client connected from 25357[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25360[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25356[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25363[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25372[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25359[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25362[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25379[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25364[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25374[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25370[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25378[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25371[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25361[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25369[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25377[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25355[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25392[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25376[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:39 joe acpid: client connected from 25391[0:0]
Feb  1 19:00:39 joe acpid: 1 client rule loaded
Feb  1 19:00:53 joe acpid: client 25357[0:0] has disconnected
Feb  1 19:00:53 joe acpid: client 25360[0:0] has disconnected
Feb  1 19:00:53 joe acpid: client 25356[0:0] has disconnected
Feb  1 19:00:53 joe acpid: client 25363[0:0] has disconnected
Feb  1 19:00:53 joe acpid: client 25372[0:0] has disconnected
Feb  1 19:00:53 joe acpid: client 25359[0:0] has disconnected
Feb  1 19:00:53 joe acpid: client 25362[0:0] has disconnected
Feb  1 19:00:53 joe acpid: client 25379[0:0] has disconnected
Feb  1 19:00:53 joe acpid: client 25364[0:0] has disconnected
Feb  1 19:00:53 joe acpid: client 25374[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25370[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25378[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25371[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25361[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25369[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25377[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25355[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25392[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25376[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25391[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25492[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25492[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25493[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25493[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25494[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25494[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25517[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25517[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25518[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25518[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25516[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25516[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25519[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25519[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25524[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25524[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25526[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25526[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25529[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25529[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25525[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25525[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25527[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25527[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25544[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25580[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25536[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25531[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25579[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25618[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25562[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25573[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25576[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25560[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25530[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25578[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25557[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25582[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25581[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25577[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25555[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25584[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25583[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25622[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25549[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25567[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25553[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25537[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25574[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25586[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25541[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25594[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25611[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25593[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25590[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25589[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25570[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25533[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25595[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25596[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25591[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25532[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25599[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25566[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25598[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25600[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25543[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25604[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25601[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25603[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25606[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25588[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25548[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25539[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25605[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25597[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25558[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25564[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25551[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25627[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25632[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25621[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25631[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25626[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25542[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25561[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25602[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25629[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25579[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25576[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25557[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25555[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25590[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25615[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25592[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25580[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25536[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25562[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25573[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25578[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25582[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25577[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25586[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25594[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25587[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25633[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25541[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25611[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25593[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25606[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25571[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25583[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25537[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25574[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25595[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25563[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25544[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25531[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25560[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25530[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25581[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25549[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25567[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25596[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25532[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25599[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25566[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25598[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25600[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25603[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25588[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25558[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25627[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25635[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25629[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25630[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25584[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25543[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25551[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25630[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25559[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25570[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25604[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client 25635[0:0] has disconnected
Feb  1 19:00:54 joe acpid: client connected from 25575[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25552[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client connected from 25636[0:0]
Feb  1 19:00:54 joe acpid: 1 client rule loaded
Feb  1 19:00:54 joe acpid: client 25553[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client connected from 25637[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client 25533[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25571[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client connected from 25620[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client 25618[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25622[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25589[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25591[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25601[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25597[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25564[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25632[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25621[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25631[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25626[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25542[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25561[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25602[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25615[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25592[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25563[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25559[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25575[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25552[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client connected from 25540[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25609[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25547[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25569[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client 25539[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25587[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client connected from 25624[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25572[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25554[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25568[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25538[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client 25548[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client connected from 25534[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client 25605[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25633[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25636[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25620[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25540[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client 25609[0:0] has disconnected
Feb  1 19:00:55 joe acpid: client connected from 25550[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25617[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25535[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25546[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25610[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25545[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25556[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25608[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25614[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25634[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25625[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25612[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25616[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25619[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25628[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25613[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25623[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25607[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25565[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25769[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25775[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25770[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25777[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25773[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25776[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25778[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25782[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25771[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25787[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25789[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25799[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:55 joe acpid: client connected from 25585[0:0]
Feb  1 19:00:55 joe acpid: 1 client rule loaded
Feb  1 19:00:56 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,820114 seconds 
Feb  1 19:00:57 joe acpid: client 25637[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25547[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25569[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25624[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25572[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25554[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25568[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25538[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25534[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25550[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25617[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25535[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25546[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25610[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25545[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25556[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25608[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25614[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25634[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25625[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25612[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25616[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25619[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25628[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25613[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25623[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25607[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25565[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25769[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25775[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25770[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25777[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25773[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25776[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25778[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25782[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25771[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25787[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25789[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25799[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25585[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client connected from 25924[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25934[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25933[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25931[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25925[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25928[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25926[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25935[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25927[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25930[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25929[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25951[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25948[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25956[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25958[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25962[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25960[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25953[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25949[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25955[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25957[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25952[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25947[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25961[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25954[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25946[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25950[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25959[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25981[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25987[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25980[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25984[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25988[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25992[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25990[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25991[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25989[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25985[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25982[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client connected from 25983[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe acpid: client 25924[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25933[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25925[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25928[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25926[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25935[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client 25929[0:0] has disconnected
Feb  1 19:00:57 joe acpid: client connected from 25986[0:0]
Feb  1 19:00:57 joe acpid: 1 client rule loaded
Feb  1 19:00:57 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,435012 seconds 
Feb  1 19:00:58 joe acpid: client 25934[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25931[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25927[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25930[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client connected from 26010[0:0]
Feb  1 19:00:58 joe acpid: 1 client rule loaded
Feb  1 19:00:58 joe acpid: client connected from 26006[0:0]
Feb  1 19:00:58 joe acpid: 1 client rule loaded
Feb  1 19:00:58 joe acpid: client connected from 26012[0:0]
Feb  1 19:00:58 joe acpid: 1 client rule loaded
Feb  1 19:00:58 joe acpid: client connected from 26008[0:0]
Feb  1 19:00:58 joe acpid: 1 client rule loaded
Feb  1 19:00:58 joe acpid: client connected from 26009[0:0]
Feb  1 19:00:58 joe acpid: 1 client rule loaded
Feb  1 19:00:58 joe acpid: client connected from 26007[0:0]
Feb  1 19:00:58 joe acpid: 1 client rule loaded
Feb  1 19:00:58 joe acpid: client connected from 26013[0:0]
Feb  1 19:00:58 joe acpid: 1 client rule loaded
Feb  1 19:00:58 joe acpid: client connected from 26011[0:0]
Feb  1 19:00:58 joe acpid: 1 client rule loaded
Feb  1 19:00:58 joe acpid: client 25951[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25948[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25956[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25958[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25962[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25960[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25953[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25949[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25955[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25957[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25952[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25947[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25961[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25954[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25946[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25950[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25959[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25981[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25987[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25980[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25984[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25988[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25992[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25990[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25991[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25989[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25985[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25982[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25983[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client 25986[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client connected from 26026[0:0]
Feb  1 19:00:58 joe acpid: 1 client rule loaded
Feb  1 19:00:58 joe acpid: client 26010[0:0] has disconnected
Feb  1 19:00:58 joe acpid: client connected from 26027[0:0]
Feb  1 19:00:58 joe acpid: 1 client rule loaded
Feb  1 19:00:58 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,835009 seconds 
Feb  1 19:00:58 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,879610 seconds 
Feb  1 19:00:58 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,890345 seconds 
Feb  1 19:00:58 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,904335 seconds 
Feb  1 19:00:58 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,921441 seconds 
Feb  1 19:00:58 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,933014 seconds 
Feb  1 19:00:58 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,958407 seconds 
Feb  1 19:00:58 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,995197 seconds 
Feb  1 19:01:10 joe acpid: client 26006[0:0] has disconnected
Feb  1 19:01:10 joe acpid: client 26012[0:0] has disconnected
Feb  1 19:01:10 joe acpid: client 26008[0:0] has disconnected
Feb  1 19:01:10 joe acpid: client 26009[0:0] has disconnected
Feb  1 19:01:10 joe acpid: client 26007[0:0] has disconnected
Feb  1 19:01:10 joe acpid: client 26013[0:0] has disconnected
Feb  1 19:01:10 joe acpid: client 26011[0:0] has disconnected
Feb  1 19:01:10 joe acpid: client 26026[0:0] has disconnected
Feb  1 19:01:10 joe acpid: client 26027[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26095[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26095[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26101[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26101[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26120[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26120[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26098[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26098[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26113[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26113[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26104[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26104[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26103[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26103[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26102[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26102[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26109[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26109[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26118[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26118[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26119[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26119[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26152[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26152[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26150[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26150[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26157[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26157[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26156[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26156[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26105[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26175[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26108[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26181[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26179[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26106[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26096[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26107[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26171[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26115[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26112[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26166[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26176[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26114[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26174[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26123[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26122[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26117[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26178[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26097[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26153[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26126[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26125[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26110[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26151[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26124[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26099[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26168[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26158[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26167[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26169[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26160[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26170[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26197[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26180[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26155[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26159[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26173[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26211[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26198[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26213[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26215[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26195[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26151[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26194[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26175[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client 26176[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client 26174[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client 26178[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26216[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26209[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26222[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26210[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26208[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26207[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26212[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26214[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26229[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26231[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client 26181[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client 26107[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client 26171[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client 26125[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client 26124[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client 26158[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client 26169[0:0] has disconnected
Feb  1 19:01:11 joe acpid: client connected from 26233[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26240[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26235[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26239[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26241[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26246[0:0]
Feb  1 19:01:11 joe acpid: 1 client rule loaded
Feb  1 19:01:11 joe acpid: client connected from 26244[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26242[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26236[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26245[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26238[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26250[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26247[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26252[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client 26197[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26211[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26198[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26215[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26194[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26216[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26210[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26212[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client connected from 26249[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client 26108[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26106[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26166[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26110[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26099[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26168[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26167[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26173[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26213[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26195[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26209[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26229[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client connected from 26253[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client 26160[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26180[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26214[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26233[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client connected from 26255[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client 26097[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26155[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26159[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26222[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26208[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26207[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26231[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26244[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26242[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client connected from 26256[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26263[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26265[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26268[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26273[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26259[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26279[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26280[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26294[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26293[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26284[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26269[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26282[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26290[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26288[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client 26179[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26096[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26114[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26153[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26126[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26240[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26241[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26246[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26265[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client connected from 26285[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client 26105[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26115[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26112[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26123[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26117[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26170[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26239[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26236[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26245[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26238[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26252[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client connected from 26257[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26291[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26276[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26248[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26283[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26264[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26296[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26278[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26292[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26274[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26295[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26272[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26277[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26289[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26275[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26267[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26261[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26254[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26271[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26251[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26287[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26258[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26286[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26260[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26281[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26270[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26262[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client 26235[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26255[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26273[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26274[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client connected from 26266[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26375[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client 26259[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client connected from 26374[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client 26253[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client connected from 26378[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26381[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client 26250[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client 26247[0:0] has disconnected
Feb  1 19:01:12 joe acpid: client connected from 26386[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26376[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26379[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26389[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26390[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26388[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26403[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26393[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26412[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26408[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:12 joe acpid: client connected from 26410[0:0]
Feb  1 19:01:12 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client 26122[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26249[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26256[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26263[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26268[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26279[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26280[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26294[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26293[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26284[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26269[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26282[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26290[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26288[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26285[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26257[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26291[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26276[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26248[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26283[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26264[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26296[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26278[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26292[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26295[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26272[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26277[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26289[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26275[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26267[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26261[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26254[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26271[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26251[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26287[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26258[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26286[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26260[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26281[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26270[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26262[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26266[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26375[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26374[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26378[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26381[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26386[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26376[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26379[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26389[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26390[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26388[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26403[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26393[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26412[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26408[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client 26410[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client connected from 26545[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26546[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26549[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client 26545[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client connected from 26551[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client 26546[0:0] has disconnected
Feb  1 19:01:14 joe acpid: client connected from 26550[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26555[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26553[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26564[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26566[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26554[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26563[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26570[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26562[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,919533 seconds 
Feb  1 19:01:14 joe acpid: client connected from 26575[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26565[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26576[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26580[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26584[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26572[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26571[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26577[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26585[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26574[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26569[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26567[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26581[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26586[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26582[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26573[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26579[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26568[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26619[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26614[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26618[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26611[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26609[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26613[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26616[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26610[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26615[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26620[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26635[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:14 joe acpid: client connected from 26636[0:0]
Feb  1 19:01:14 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26637[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26645[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26646[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26638[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26612[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26640[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client 26549[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26555[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client connected from 26634[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26641[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26639[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26617[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,336425 seconds 
Feb  1 19:01:15 joe acpid: client connected from 26657[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26658[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26659[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client 26551[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26550[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26553[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26564[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26566[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26554[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26563[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26562[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26575[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26576[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26580[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26572[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26571[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26585[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26569[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26567[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26581[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26586[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26582[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26573[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26579[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26614[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26615[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client connected from 26666[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26656[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26662[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26661[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26664[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26663[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client 26568[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client connected from 26665[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client 26610[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client connected from 26671[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26693[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26655[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26704[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26667[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26700[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26672[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26689[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26679[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26720[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26690[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26695[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26721[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client 26613[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client connected from 26681[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client 26618[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client connected from 26694[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client 26574[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client connected from 26723[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client 26584[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26577[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26619[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26611[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client connected from 26680[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26685[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26696[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26697[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26687[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26701[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26692[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client 26616[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client connected from 26673[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26682[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client 26570[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26565[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client connected from 26684[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26727[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26669[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client 26609[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client connected from 26686[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26725[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26724[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client 26636[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client connected from 26698[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26674[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26668[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26691[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26729[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26702[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26683[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26654[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26660[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26728[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client 26620[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26637[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26638[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26612[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26640[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26639[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26617[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client connected from 26762[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26763[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client connected from 26670[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:15 joe acpid: client 26635[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client 26641[0:0] has disconnected
Feb  1 19:01:15 joe acpid: client connected from 26761[0:0]
Feb  1 19:01:15 joe acpid: 1 client rule loaded
Feb  1 19:01:32 joe acpid: client 26723[0:0] has disconnected
Feb  1 19:01:32 joe acpid: client 26670[0:0] has disconnected
Feb  1 19:01:32 joe acpid: client connected from 26774[0:0]
Feb  1 19:01:32 joe acpid: 1 client rule loaded
Feb  1 19:01:32 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,997063 seconds 
Feb  1 19:01:32 joe acpid: client 26686[0:0] has disconnected
Feb  1 19:01:32 joe acpid: client 26761[0:0] has disconnected
Feb  1 19:01:32 joe acpid: client 26774[0:0] has disconnected
Feb  1 19:01:32 joe acpid: client connected from 26829[0:0]
Feb  1 19:01:32 joe acpid: 1 client rule loaded
Feb  1 19:01:32 joe acpid: client connected from 26825[0:0]
Feb  1 19:01:33 joe acpid: 1 client rule loaded
Feb  1 19:01:33 joe acpid: client 26645[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26646[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26634[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26657[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26658[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26659[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26666[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26656[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26662[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26661[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26664[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26663[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26665[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26671[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26693[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26655[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26704[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26667[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26700[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26672[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26689[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26679[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26720[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26690[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26695[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26721[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26681[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26694[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26680[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26685[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26696[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26697[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26687[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26701[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26692[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26673[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26682[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26684[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26727[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26669[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26725[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26724[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26698[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26674[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26668[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26691[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26729[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26702[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26683[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26654[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26660[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26728[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26762[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26763[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26829[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client 26825[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client connected from 26833[0:0]
Feb  1 19:01:33 joe acpid: 1 client rule loaded
Feb  1 19:01:33 joe acpid: client 26833[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client connected from 26831[0:0]
Feb  1 19:01:33 joe acpid: 1 client rule loaded
Feb  1 19:01:33 joe acpid: client 26831[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client connected from 26828[0:0]
Feb  1 19:01:33 joe acpid: 1 client rule loaded
Feb  1 19:01:33 joe acpid: client 26828[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client connected from 26827[0:0]
Feb  1 19:01:33 joe acpid: 1 client rule loaded
Feb  1 19:01:33 joe acpid: client 26827[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client connected from 26837[0:0]
Feb  1 19:01:33 joe acpid: 1 client rule loaded
Feb  1 19:01:33 joe acpid: client 26837[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client connected from 26843[0:0]
Feb  1 19:01:33 joe acpid: 1 client rule loaded
Feb  1 19:01:33 joe acpid: client 26843[0:0] has disconnected
Feb  1 19:01:33 joe acpid: client connected from 26830[0:0]
Feb  1 19:01:33 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26830[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 26840[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26840[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 26824[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26824[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 26842[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26842[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 26834[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26834[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 26844[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26844[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 26826[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26826[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 26832[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26832[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 26841[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26841[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 26862[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26862[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 26838[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26838[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 26873[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26873[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 26836[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26836[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 26866[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26866[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 26865[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26865[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 26864[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26864[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 26886[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26868[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26876[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26875[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26888[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26869[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26878[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26882[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26871[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26892[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26874[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26897[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26872[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26870[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26895[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26883[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26894[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26889[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26880[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26931[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26932[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26937[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26885[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26928[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26934[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26930[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26881[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26936[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26941[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26938[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26891[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26940[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26921[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26925[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26879[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26949[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26935[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26943[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26942[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26893[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26926[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26948[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26947[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26924[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26929[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26945[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26968[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26946[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26887[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 26760[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26886[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26937[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26941[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26968[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 27115[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27057[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27067[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27060[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27184[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26932[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26934[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26943[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 27166[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26949[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 27087[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27070[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27180[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27170[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27120[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27159[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26882[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26895[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 27141[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27165[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27124[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27084[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27167[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27046[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27061[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27122[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27119[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27137[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27050[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27146[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27136[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27045[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27145[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27055[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27144[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27058[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 26868[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26871[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26874[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26883[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26894[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26885[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26930[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26925[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26942[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26893[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26947[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26946[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 26887[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 27159[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 27165[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 27124[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client 27084[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 27148[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client 27122[0:0] has disconnected
Feb  1 19:01:34 joe acpid: client connected from 27183[0:0]
Feb  1 19:01:34 joe acpid: 1 client rule loaded
Feb  1 19:01:34 joe acpid: client connected from 27066[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27053[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 26876[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26875[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26888[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26897[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26872[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26880[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26931[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26928[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26881[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26938[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26891[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26940[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26921[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26879[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26926[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26948[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26929[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26945[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26760[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27115[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27067[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27060[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27166[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27120[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27133[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 26869[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26936[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26935[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27088[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 27087[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27070[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27180[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27170[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27134[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 26892[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26889[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27141[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27139[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27117[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 26924[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27057[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27184[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27046[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27163[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27125[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27142[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 26878[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 26870[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27167[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27061[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27119[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27137[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27144[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27086[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27126[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27108[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 27045[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27163[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27149[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 27148[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27133[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27161[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27158[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27085[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27138[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27078[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27073[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 27146[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27145[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27055[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27058[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27183[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27066[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27053[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27088[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27134[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27139[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27117[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27125[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27086[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27149[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27175[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 27050[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27136[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27076[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27047[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27107[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27072[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27092[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27048[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27081[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27093[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 27142[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27126[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27108[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27161[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27138[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27078[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27094[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27111[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27079[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 27076[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27109[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27179[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27185[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27075[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27090[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 27085[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27094[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27112[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 27081[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27082[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 27092[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27172[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 27107[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27215[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client 27158[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27073[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27175[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27047[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27072[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27048[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27093[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27111[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27179[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27185[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27082[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client 27172[0:0] has disconnected
Feb  1 19:01:35 joe acpid: client connected from 27217[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27219[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27222[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27223[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27220[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27231[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27228[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27227[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27232[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:35 joe acpid: client connected from 27234[0:0]
Feb  1 19:01:35 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client 27079[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27109[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27075[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27090[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27112[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27215[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27217[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27219[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27222[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27223[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27220[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27231[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27228[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27227[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27232[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27234[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client connected from 27370[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27372[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27371[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27373[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27379[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27380[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27381[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27378[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,989519 seconds 
Feb  1 19:01:37 joe acpid: client 27370[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27372[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27371[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27373[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client connected from 27387[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27393[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27392[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27396[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27412[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27390[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27395[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27399[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27404[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27402[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client 27379[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27380[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client connected from 27397[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27409[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27401[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27411[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27406[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27403[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27386[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27389[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27413[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27391[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27398[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27405[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27437[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27407[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client connected from 27410[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:37 joe acpid: client 27381[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client 27378[0:0] has disconnected
Feb  1 19:01:37 joe acpid: client connected from 27435[0:0]
Feb  1 19:01:37 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27436[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27447[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27438[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27450[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27445[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27452[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27448[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27473[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27475[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27455[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27460[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27449[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27457[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27458[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27459[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27446[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27451[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27454[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27476[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27474[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client 27389[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client connected from 27484[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27488[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27482[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27486[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27489[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client 27393[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27392[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27395[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27399[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27404[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27402[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27401[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27411[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27406[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27386[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27413[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27391[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27398[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client connected from 27485[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client 27387[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27412[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27397[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27405[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27407[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27435[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27438[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client connected from 27483[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27487[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client 27445[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27452[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27446[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client connected from 27509[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client 27450[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client connected from 27507[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client 27455[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27449[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27451[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27454[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client connected from 27511[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27518[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client 27447[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27460[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client connected from 27514[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27517[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27519[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27516[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27501[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27505[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client 27457[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client connected from 27508[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27513[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27502[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27512[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client 27396[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27390[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27409[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27403[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27437[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27410[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27436[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27448[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27458[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client 27459[0:0] has disconnected
Feb  1 19:01:38 joe acpid: client connected from 27503[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27504[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27515[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:38 joe acpid: client connected from 27506[0:0]
Feb  1 19:01:38 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client 27473[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27475[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27476[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client connected from 27601[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27604[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27606[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client 27474[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27484[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27488[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27482[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27486[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27489[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27485[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27483[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27487[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27509[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27507[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27511[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27518[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27514[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27517[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27519[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27516[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27501[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27505[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27508[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27513[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27502[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27512[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27503[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27504[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27515[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27506[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27601[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27604[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client 27606[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client connected from 27607[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client 27607[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client connected from 27609[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client 27609[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client connected from 27613[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client 27613[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client connected from 27614[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client 27614[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client connected from 27611[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client 27611[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client connected from 27616[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client 27616[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client connected from 27602[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client 27602[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client connected from 27621[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client 27621[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client connected from 27617[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client 27617[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client connected from 27610[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client 27610[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client connected from 27620[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client 27620[0:0] has disconnected
Feb  1 19:01:53 joe acpid: client connected from 27603[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27615[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27605[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27618[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27646[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27644[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27642[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27645[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27647[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27641[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27648[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27640[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27664[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27649[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27668[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27666[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27663[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27643[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27665[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27662[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27667[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27661[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27660[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27694[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27695[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27696[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27709[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27705[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27710[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27702[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:53 joe acpid: client connected from 27699[0:0]
Feb  1 19:01:53 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27698[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27701[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27706[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27708[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27703[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27720[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27723[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27722[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27730[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27732[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27729[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27731[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27728[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27726[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27733[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27725[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27738[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27735[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27736[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27750[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27751[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27757[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27758[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27754[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27760[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27752[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27755[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27763[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27759[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27762[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27767[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27795[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27761[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27765[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27772[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27790[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27797[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27794[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27801[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27771[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27800[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27791[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client 27603[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27605[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27644[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27642[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27645[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27648[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27664[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27643[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27660[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27709[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27702[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27698[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27701[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27703[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27720[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27723[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27722[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27730[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27732[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27729[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27731[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27728[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27733[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27725[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27736[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27751[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27755[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27759[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27762[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27790[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client connected from 27799[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client 27618[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27750[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client connected from 27773[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client 27695[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27710[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27708[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client connected from 27820[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27766[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27808[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client 27615[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27647[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27640[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27649[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27668[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27666[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27662[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27705[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27706[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27738[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27757[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27754[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27752[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27772[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27800[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client connected from 27812[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client 27667[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27771[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client connected from 27816[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client 27646[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27663[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27665[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27735[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client connected from 27810[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client 27801[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client connected from 27819[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27821[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27769[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client 27773[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client connected from 27792[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client 27795[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27797[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client connected from 27768[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client 27641[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27696[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27767[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client connected from 27809[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client 27661[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27694[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27699[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27726[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27758[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27760[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27763[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27761[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27765[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27794[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27791[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27820[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27812[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27816[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27810[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27819[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client connected from 27813[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client 27799[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client connected from 27818[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client 27808[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client connected from 27835[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27832[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client 27766[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27821[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27769[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27792[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27768[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27813[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client connected from 27829[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client 27809[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27818[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client connected from 27840[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27830[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27839[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27833[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27846[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27852[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27845[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27850[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27844[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27734[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27827[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27853[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27854[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27510[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27860[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27862[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27500[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27865[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27893[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27892[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27897[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27904[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27914[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27894[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27912[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27900[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27899[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27909[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client connected from 27896[0:0]
Feb  1 19:01:54 joe acpid: 1 client rule loaded
Feb  1 19:01:54 joe acpid: client 27835[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27832[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27829[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27830[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27839[0:0] has disconnected
Feb  1 19:01:54 joe acpid: client 27833[0:0] has disconnected
Feb  1 19:01:55 joe acpid: client connected from 27903[0:0]
Feb  1 19:01:55 joe acpid: 1 client rule loaded
Feb  1 19:01:55 joe acpid: client connected from 27901[0:0]
Feb  1 19:01:55 joe acpid: 1 client rule loaded
Feb  1 19:01:55 joe acpid: client connected from 27908[0:0]
Feb  1 19:01:55 joe acpid: 1 client rule loaded
Feb  1 19:01:55 joe acpid: client connected from 27911[0:0]
Feb  1 19:01:55 joe acpid: 1 client rule loaded
Feb  1 19:01:55 joe acpid: client connected from 27928[0:0]
Feb  1 19:01:55 joe acpid: 1 client rule loaded
Feb  1 19:01:55 joe acpid: client connected from 27910[0:0]
Feb  1 19:01:55 joe acpid: 1 client rule loaded
Feb  1 19:01:55 joe acpid: client connected from 27927[0:0]
Feb  1 19:01:55 joe acpid: 1 client rule loaded
Feb  1 19:01:55 joe acpid: client connected from 27926[0:0]
Feb  1 19:01:55 joe acpid: 1 client rule loaded
Feb  1 19:01:55 joe acpid: client connected from 27925[0:0]
Feb  1 19:01:55 joe acpid: 1 client rule loaded
Feb  1 19:01:55 joe acpid: client connected from 27924[0:0]
Feb  1 19:01:55 joe acpid: 1 client rule loaded
Feb  1 19:01:55 joe acpid: client connected from 27934[0:0]
Feb  1 19:01:55 joe acpid: 1 client rule loaded
Feb  1 19:01:55 joe acpid: client connected from 27933[0:0]
Feb  1 19:01:55 joe acpid: 1 client rule loaded
Feb  1 19:01:55 joe acpid: client connected from 27938[0:0]
Feb  1 19:01:55 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client 27840[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27846[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27852[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27845[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27850[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27844[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27734[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27827[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27853[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27854[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27510[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27860[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27862[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27500[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27865[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27893[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27892[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27897[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27904[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27914[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27894[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27912[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27900[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27899[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27909[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27896[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27903[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27901[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27908[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27911[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27928[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27910[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27927[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27926[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27925[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27924[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27934[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27933[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 27938[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client connected from 28082[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28084[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28083[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28086[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client 28082[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client 28084[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client connected from 28091[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28092[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28090[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28096[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28097[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28104[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28093[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28102[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28117[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28103[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28099[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28108[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28107[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28118[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28105[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28119[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28116[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28110[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,596005 seconds 
Feb  1 19:01:57 joe acpid: client connected from 28114[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28098[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28111[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28113[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28120[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28124[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28122[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28109[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28101[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28100[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28152[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28149[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28153[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client connected from 28148[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:57 joe acpid: client 28083[0:0] has disconnected
Feb  1 19:01:57 joe acpid: client connected from 28154[0:0]
Feb  1 19:01:57 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client 28086[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client connected from 28150[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28151[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,837260 seconds 
Feb  1 19:01:58 joe acpid: client connected from 28166[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28165[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client 28090[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client connected from 28178[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28184[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28195[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28186[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28179[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28173[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28163[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28171[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28174[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28176[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28167[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28177[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28164[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28183[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28188[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28182[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28192[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28180[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28194[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28185[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28187[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28193[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28169[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28190[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client 28102[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28108[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28111[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client connected from 28172[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28170[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28168[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28191[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client 28092[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28093[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28099[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28105[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28116[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28114[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28109[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client connected from 28225[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client 28103[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28098[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client connected from 28227[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client 28107[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28110[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28120[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28122[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client connected from 28263[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28245[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28232[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28256[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client 28091[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28096[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28097[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28104[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28117[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28118[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28119[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28113[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28124[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28101[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28100[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28149[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28153[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28148[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28150[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client connected from 28262[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28247[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client 28152[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28154[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28151[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28232[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client 28256[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client connected from 28228[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client 28263[0:0] has disconnected
Feb  1 19:01:58 joe acpid: client connected from 28298[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28233[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:01:58 joe acpid: client connected from 28250[0:0]
Feb  1 19:01:58 joe acpid: 1 client rule loaded
Feb  1 19:02:11 joe acpid: client 28166[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28184[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28186[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28173[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28163[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28171[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28176[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28177[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28183[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28190[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28168[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28245[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28262[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28247[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28228[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28298[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28233[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28250[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client connected from 28253[0:0]
Feb  1 19:02:11 joe acpid: 1 client rule loaded
Feb  1 19:02:11 joe acpid: client 28165[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28178[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28195[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28179[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28174[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28167[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28164[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28188[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28182[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28192[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28180[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28194[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28185[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28187[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28193[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28169[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28172[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28170[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28191[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28225[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28227[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client 28253[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client connected from 28235[0:0]
Feb  1 19:02:11 joe acpid: 1 client rule loaded
Feb  1 19:02:11 joe acpid: client 28235[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client connected from 28301[0:0]
Feb  1 19:02:11 joe acpid: 1 client rule loaded
Feb  1 19:02:11 joe acpid: client 28301[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client connected from 28303[0:0]
Feb  1 19:02:11 joe acpid: 1 client rule loaded
Feb  1 19:02:11 joe acpid: client 28303[0:0] has disconnected
Feb  1 19:02:11 joe acpid: client connected from 28248[0:0]
Feb  1 19:02:11 joe acpid: 1 client rule loaded
Feb  1 19:02:11 joe acpid: client 28248[0:0] has disconnected
Feb  1 19:02:12 joe acpid: client connected from 28236[0:0]
Feb  1 19:02:12 joe acpid: 1 client rule loaded
Feb  1 19:02:12 joe acpid: client 28236[0:0] has disconnected
Feb  1 19:02:12 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,917227 seconds 
Feb  1 19:02:12 joe acpid: client connected from 28299[0:0]
Feb  1 19:02:12 joe acpid: 1 client rule loaded
Feb  1 19:02:12 joe acpid: client 28299[0:0] has disconnected
Feb  1 19:02:12 joe acpid: client connected from 28296[0:0]
Feb  1 19:02:12 joe acpid: 1 client rule loaded
Feb  1 19:02:12 joe acpid: client 28296[0:0] has disconnected
Feb  1 19:02:12 joe acpid: client connected from 28251[0:0]
Feb  1 19:02:12 joe acpid: 1 client rule loaded
Feb  1 19:02:12 joe acpid: client 28251[0:0] has disconnected
Feb  1 19:02:12 joe acpid: client connected from 28241[0:0]
Feb  1 19:02:12 joe acpid: 1 client rule loaded
Feb  1 19:02:12 joe acpid: client 28241[0:0] has disconnected
Feb  1 19:02:12 joe acpid: client connected from 28297[0:0]
Feb  1 19:02:12 joe acpid: 1 client rule loaded
Feb  1 19:02:12 joe acpid: client 28297[0:0] has disconnected
Feb  1 19:02:12 joe acpid: client connected from 28254[0:0]
Feb  1 19:02:12 joe acpid: 1 client rule loaded
Feb  1 19:02:12 joe acpid: client 28254[0:0] has disconnected
Feb  1 19:02:16 joe acpid: client connected from 28249[0:0]
Feb  1 19:02:16 joe acpid: 1 client rule loaded
Feb  1 19:02:16 joe acpid: client 28249[0:0] has disconnected
Feb  1 19:02:16 joe acpid: client connected from 28264[0:0]
Feb  1 19:02:16 joe acpid: 1 client rule loaded
Feb  1 19:02:16 joe acpid: client 28264[0:0] has disconnected
Feb  1 19:02:16 joe acpid: client connected from 28252[0:0]
Feb  1 19:02:16 joe acpid: 1 client rule loaded
Feb  1 19:02:16 joe acpid: client 28252[0:0] has disconnected
Feb  1 19:02:16 joe acpid: client connected from 28258[0:0]
Feb  1 19:02:17 joe acpid: 1 client rule loaded
Feb  1 19:02:17 joe acpid: client 28258[0:0] has disconnected
Feb  1 19:02:17 joe acpid: client connected from 28261[0:0]
Feb  1 19:02:17 joe acpid: 1 client rule loaded
Feb  1 19:02:17 joe acpid: client 28261[0:0] has disconnected
Feb  1 19:02:17 joe acpid: client connected from 28226[0:0]
Feb  1 19:02:17 joe acpid: 1 client rule loaded
Feb  1 19:02:17 joe acpid: client 28226[0:0] has disconnected
Feb  1 19:02:17 joe acpid: client connected from 28260[0:0]
Feb  1 19:02:17 joe acpid: 1 client rule loaded
Feb  1 19:02:17 joe acpid: client 28260[0:0] has disconnected
Feb  1 19:02:17 joe acpid: client connected from 28242[0:0]
Feb  1 19:02:17 joe acpid: 1 client rule loaded
Feb  1 19:02:17 joe acpid: client 28242[0:0] has disconnected
Feb  1 19:02:17 joe acpid: client connected from 28234[0:0]
Feb  1 19:02:17 joe acpid: 1 client rule loaded
Feb  1 19:02:17 joe acpid: client 28234[0:0] has disconnected
Feb  1 19:02:17 joe acpid: client connected from 28259[0:0]
Feb  1 19:02:17 joe acpid: 1 client rule loaded
Feb  1 19:02:17 joe acpid: client 28259[0:0] has disconnected
Feb  1 19:02:17 joe acpid: client connected from 28244[0:0]
Feb  1 19:02:17 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28244[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28305[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28305[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28265[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28265[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28255[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28255[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28302[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28302[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28304[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28304[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28257[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28257[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28295[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28295[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28246[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28246[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28243[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28243[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28361[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28361[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28367[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28367[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28363[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28363[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28362[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28362[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28369[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28369[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28364[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28364[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28366[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client 28366[0:0] has disconnected
Feb  1 19:02:18 joe acpid: client connected from 28368[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28365[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28441[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28443[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28440[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28446[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28448[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28452[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28445[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28451[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28453[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28488[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28460[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28454[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28481[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28476[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28479[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28478[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28484[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28490[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28480[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28492[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28491[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28487[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28493[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28500[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28504[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28505[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28502[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28507[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28508[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28501[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28514[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28520[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28526[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28518[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28530[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28516[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28535[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28528[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28522[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28524[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28531[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28534[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28527[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28536[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28515[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28529[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28540[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28533[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28519[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28539[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28538[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:18 joe acpid: client connected from 28541[0:0]
Feb  1 19:02:18 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28521[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client 28493[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client connected from 28537[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28559[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28565[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28563[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28564[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28570[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28574[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28575[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28577[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28571[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28594[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28605[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28589[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28590[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client 28448[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28445[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28453[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28491[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28500[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28504[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28505[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28534[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client connected from 28585[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client 28446[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28452[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28481[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28490[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28507[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28501[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28535[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28531[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28527[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28529[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28533[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client connected from 28592[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client 28443[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client connected from 28597[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client 28537[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client connected from 28596[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28606[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28593[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28588[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28601[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28599[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28587[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28581[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28629[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client 28365[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28441[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28488[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28460[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28478[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28502[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28520[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28518[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28515[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28605[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28596[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client connected from 28586[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28636[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28634[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28603[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28626[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28591[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28584[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28604[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28639[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28600[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28637[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28640[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client 28368[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28440[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28451[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28454[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28476[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28479[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28484[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28480[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28492[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28487[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28508[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28514[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28526[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28530[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28516[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28528[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28522[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28524[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28536[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28540[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28541[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28563[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28564[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28594[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28593[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28588[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28634[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client connected from 28641[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28632[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28642[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28635[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28628[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client 28519[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28538[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28570[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28575[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28629[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client connected from 28633[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client 28539[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28559[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28565[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28577[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28571[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28589[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28590[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28606[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28601[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28599[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28581[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client connected from 28631[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client 28521[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28574[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28585[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28592[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28597[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28587[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28603[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28626[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28591[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28584[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28604[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28639[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28600[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28640[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28632[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28631[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client connected from 28638[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client 28586[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28635[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client connected from 28630[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client 28630[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client connected from 28643[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client 28638[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client connected from 28660[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28661[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28672[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28670[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client 28643[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28660[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client connected from 28668[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28674[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client 28636[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28637[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28628[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28633[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client connected from 28669[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28663[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28671[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28673[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client 28642[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client 28670[0:0] has disconnected
Feb  1 19:02:19 joe acpid: client connected from 28666[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28667[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28676[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28664[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28688[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28690[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28689[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28694[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28695[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28698[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28580[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28572[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28712[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28710[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28714[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:19 joe acpid: client connected from 28716[0:0]
Feb  1 19:02:19 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client 28641[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28661[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28672[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28668[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28674[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28669[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28663[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28671[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28673[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28666[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28667[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28676[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28664[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28688[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28690[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28689[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28694[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28695[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28698[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28580[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28572[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28712[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28710[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28714[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28716[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client connected from 28961[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client 28961[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client connected from 29030[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client 29030[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client connected from 29017[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client 29017[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client connected from 29070[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client 29070[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client connected from 29022[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client 29022[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client connected from 29072[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client 29072[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client connected from 29075[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client 29075[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client connected from 29082[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client 29082[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client connected from 29067[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client 29067[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client connected from 29084[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client 29084[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client connected from 29095[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client 29095[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client connected from 29034[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 29013[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 29128[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 29077[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28889[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 29071[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28894[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28976[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28973[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 29114[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28909[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28899[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28993[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28860[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 29122[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 29031[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28947[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 29101[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28876[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28933[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28892[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28901[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 29100[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 29042[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28880[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28962[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 29069[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28875[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 29116[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28857[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 29045[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 29038[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28900[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28938[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28891[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28907[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28879[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 29103[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28963[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client 28973[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client connected from 29023[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28971[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28921[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28925[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client 28857[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 29038[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client connected from 28896[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28928[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28948[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client 29034[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28889[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28993[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 29122[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client connected from 28934[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client connected from 28927[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:33 joe acpid: client 29128[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 29071[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28909[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 28899[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client 29031[0:0] has disconnected
Feb  1 19:02:33 joe acpid: client connected from 28982[0:0]
Feb  1 19:02:33 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29105[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client 29114[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28860[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28892[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28934[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28927[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client connected from 28922[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29048[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client 28928[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28948[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28982[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client connected from 28881[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29016[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28897[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28862[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29001[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28859[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28908[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client 28896[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client connected from 28975[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28930[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28906[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28902[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client 29013[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29077[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28976[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29101[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28876[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28933[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29100[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29042[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28880[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29069[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28875[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29116[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29045[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28900[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28938[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28907[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28963[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29023[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28925[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29048[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28897[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28862[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client connected from 29104[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client 28894[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28947[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28879[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29016[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29001[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client connected from 29025[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client 29103[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28975[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28902[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client connected from 28856[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client 29105[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client connected from 29115[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client 28901[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28962[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28891[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28971[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28881[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client connected from 28978[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client 28856[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client connected from 29021[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client 28978[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client connected from 29019[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client 28906[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client connected from 29026[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client 28922[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28908[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29104[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client connected from 29043[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29032[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29074[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client 29074[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client connected from 29108[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29073[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client 28921[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28930[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29115[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29019[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29026[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29043[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29032[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client connected from 28983[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29076[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29119[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29066[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29029[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28995[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29036[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28972[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client 28859[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29025[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29021[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29108[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client connected from 29046[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28986[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29028[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28985[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28950[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29096[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29080[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28990[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29093[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28980[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28951[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29014[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29098[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29117[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28936[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28931[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28998[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28932[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28966[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28958[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28988[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28883[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28957[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29040[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29109[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29000[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28965[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28953[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28884[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29035[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28904[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29033[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29125[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28991[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client 28983[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29066[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29029[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28995[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 29036[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28972[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client 28986[0:0] has disconnected
Feb  1 19:02:34 joe acpid: client connected from 28887[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28994[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28866[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29111[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28924[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29123[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29121[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 28997[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29159[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29153[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29155[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29170[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29160[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29157[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29161[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29168[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29166[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29167[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:34 joe acpid: client connected from 29156[0:0]
Feb  1 19:02:34 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client 29073[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29076[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29119[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29046[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29028[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28985[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28950[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29096[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29080[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28990[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29093[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28980[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28951[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29014[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29098[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29117[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28936[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28931[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28998[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28932[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28966[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28958[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28988[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28883[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28957[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29040[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29109[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29000[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28965[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28953[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28884[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29035[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28904[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29033[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29125[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28991[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28887[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28994[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28866[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29111[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28924[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29123[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29121[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 28997[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29159[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29153[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29155[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29170[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29160[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29157[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29161[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29168[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29166[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29167[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29156[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client connected from 29323[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29325[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29326[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29332[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29324[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29339[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29338[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29345[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29333[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29330[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29346[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29341[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29347[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29342[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29335[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29328[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29340[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29343[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29344[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29336[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29363[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29365[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29364[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29367[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29368[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29369[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29374[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29372[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29373[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29366[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client 29325[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client connected from 29371[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29370[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,470420 seconds 
Feb  1 19:02:37 joe acpid: client connected from 29385[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29384[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29393[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29409[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29407[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29389[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29387[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29391[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29388[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29390[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29383[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29408[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29405[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29406[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29419[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client 29345[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client connected from 29423[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29415[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client 29323[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29332[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29333[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29330[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29341[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29347[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29342[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29335[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29328[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29340[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29343[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29344[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client connected from 29422[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client 29324[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29346[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client connected from 29413[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client 29338[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client connected from 29414[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29420[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29425[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29470[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29426[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29446[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29445[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29468[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29471[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client 29326[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29339[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client connected from 29421[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29418[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29460[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29474[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29443[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29461[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client 29336[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client connected from 29466[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29463[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29473[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29465[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,599392 seconds 
Feb  1 19:02:37 joe acpid: client connected from 29459[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29458[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29456[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29438[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29469[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client 29409[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client 29405[0:0] has disconnected
Feb  1 19:02:37 joe acpid: client connected from 29472[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29476[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29475[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29505[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29495[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29496[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:37 joe acpid: client connected from 29506[0:0]
Feb  1 19:02:37 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29441[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29442[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29444[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29464[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29513[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29454[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client 29372[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29371[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29370[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29422[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client connected from 29439[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29455[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29440[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client 29367[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29374[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29384[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29387[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client connected from 29453[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client 29363[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29365[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29364[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29368[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29369[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29373[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29366[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29385[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29393[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29407[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29389[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29391[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29388[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29390[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29383[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29406[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29423[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29415[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29414[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29421[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29418[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client connected from 29527[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29516[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29514[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29520[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client 29425[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client connected from 29511[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29522[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client 29408[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29419[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29413[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29420[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29426[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client connected from 29517[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client 29445[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client connected from 29529[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29524[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29526[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client 29458[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client connected from 29519[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29528[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client 29466[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29463[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client connected from 29521[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29523[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client 29465[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client connected from 29525[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29510[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29512[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client 29474[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client 29472[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client connected from 29531[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client connected from 29518[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:38 joe acpid: client 29446[0:0] has disconnected
Feb  1 19:02:38 joe acpid: client connected from 29530[0:0]
Feb  1 19:02:38 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client 29470[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29468[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29471[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29460[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29443[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29461[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29473[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29459[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29456[0:0] has disconnected
Feb  1 19:02:53 joe dbus[1463]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Feb  1 19:02:53 joe acpid: client 29438[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29469[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29476[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29475[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29505[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29495[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29496[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29506[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29441[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29442[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29444[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29464[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29513[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29454[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29439[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29455[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29440[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29453[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29527[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29516[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29514[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29520[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29511[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29522[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29517[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29529[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29524[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29526[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29519[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29528[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29521[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29523[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29525[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29510[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29512[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29531[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29518[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client 29530[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client connected from 29668[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client 29668[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client connected from 29672[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client 29672[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client connected from 29673[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client 29673[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client connected from 29674[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client 29674[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client connected from 29685[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client 29685[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client connected from 29688[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client 29688[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client connected from 29669[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client 29669[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client connected from 29677[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client 29677[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client connected from 29678[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client 29678[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client connected from 29691[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client 29691[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client connected from 29684[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client 29684[0:0] has disconnected
Feb  1 19:02:53 joe acpid: client connected from 29686[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client connected from 29692[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client connected from 29679[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client connected from 29675[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client connected from 29671[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client connected from 29690[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client connected from 29683[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client connected from 29670[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client connected from 29689[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:53 joe acpid: client connected from 29682[0:0]
Feb  1 19:02:53 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29710[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29711[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29712[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29716[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29718[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29720[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29722[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29726[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29730[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29729[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29725[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29746[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29719[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29747[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29727[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29721[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29720[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29724[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29744[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29743[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29749[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29754[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29755[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29757[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29760[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29758[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29764[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29686[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29692[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29670[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29689[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29718[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29762[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29741[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29756[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29752[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29742[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29745[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29761[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29740[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29763[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29783[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29788[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29782[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29793[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29792[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29787[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29786[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29789[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29795[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29790[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29794[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29784[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29671[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29683[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29682[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29722[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29727[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29721[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29724[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29744[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29743[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29749[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29757[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29758[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29752[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29745[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29806[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29807[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29812[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29811[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29821[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29819[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29810[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29816[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29823[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29815[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29788[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29809[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29824[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29830[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29710[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29783[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29782[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29794[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29784[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29813[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29834[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29820[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29822[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29675[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29690[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29712[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29726[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29730[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29729[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29746[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29719[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29747[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29754[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29755[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29760[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29764[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29741[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29756[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29742[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29793[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29786[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29812[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29811[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29810[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29835[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29679[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29790[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29819[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29827[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29829[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29711[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29716[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29725[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29762[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29761[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29740[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29763[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29792[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29789[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29795[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29820[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29827[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29826[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29787[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29807[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29816[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29818[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29833[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29828[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29857[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29806[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29821[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29815[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29809[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29830[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29834[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29828[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29832[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29866[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29813[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29882[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29879[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29822[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29835[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29861[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29823[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29829[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29864[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29826[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29868[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29867[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29870[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29856[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29860[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29883[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29875[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29872[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29873[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29904[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29909[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29910[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29878[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29863[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29876[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29865[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29880[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29824[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29818[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29833[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29857[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29882[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29861[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29868[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29867[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client 29870[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29881[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29874[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29832[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29869[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29908[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29858[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29911[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29905[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29912[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client 29866[0:0] has disconnected
Feb  1 19:02:54 joe acpid: client connected from 29914[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29917[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:54 joe acpid: client connected from 29903[0:0]
Feb  1 19:02:54 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29913[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client 29879[0:0] has disconnected
Feb  1 19:02:55 joe acpid: client 29864[0:0] has disconnected
Feb  1 19:02:55 joe acpid: client 29856[0:0] has disconnected
Feb  1 19:02:55 joe acpid: client 29873[0:0] has disconnected
Feb  1 19:02:55 joe acpid: client 29878[0:0] has disconnected
Feb  1 19:02:55 joe acpid: client connected from 29915[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29930[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29933[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29932[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29934[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29937[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29935[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29748[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29906[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29963[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29965[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29962[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client 29860[0:0] has disconnected
Feb  1 19:02:55 joe acpid: client 29869[0:0] has disconnected
Feb  1 19:02:55 joe acpid: client 29903[0:0] has disconnected
Feb  1 19:02:55 joe acpid: client connected from 29971[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29966[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29964[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29975[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29974[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29980[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29979[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29977[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29984[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:55 joe acpid: client connected from 29987[0:0]
Feb  1 19:02:55 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client 29883[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29875[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29872[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29904[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29909[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29910[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29863[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29876[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29865[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29880[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29881[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29874[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29908[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29858[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29911[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29905[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29912[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29914[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29917[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29913[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29915[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29930[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29933[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29932[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29934[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29937[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29935[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29748[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29906[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29963[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29965[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29962[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29971[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29966[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29964[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29975[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29974[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29980[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29979[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29977[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29984[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client 29987[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client connected from 30142[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client 30142[0:0] has disconnected
Feb  1 19:02:57 joe acpid: client connected from 30148[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30143[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30154[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30156[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30144[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30157[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30158[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30164[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30165[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30169[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30146[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30163[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30170[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30168[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30175[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30159[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30150[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30152[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30172[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30147[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30173[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30161[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30167[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30151[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30206[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30194[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30198[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30212[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30195[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30204[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30202[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30207[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:57 joe acpid: client connected from 30200[0:0]
Feb  1 19:02:57 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30205[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30210[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30201[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30197[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30203[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30199[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30211[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30226[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30209[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30227[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30228[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30229[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30243[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client 30143[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client connected from 30247[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client 30148[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30154[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30156[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30144[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30157[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30158[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30165[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30147[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client connected from 30245[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client 30170[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30168[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30175[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30167[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client connected from 30239[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30238[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30246[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client 30164[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30169[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30146[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30163[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30159[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30152[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30173[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30161[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30151[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client connected from 30244[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30241[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30240[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client 30150[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30172[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client connected from 30237[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30242[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30263[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30270[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30261[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30268[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30262[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30272[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30273[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30265[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30276[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30275[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30278[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30277[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30279[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30280[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30260[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30282[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30267[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30266[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30274[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client 30200[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client connected from 30264[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client 30197[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30203[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30211[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client connected from 30271[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30299[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client 30206[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30194[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30212[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30195[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30204[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30202[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30207[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30210[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30201[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30199[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30226[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30209[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client connected from 30300[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30301[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30315[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client 30228[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30229[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30247[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30238[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client connected from 30314[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client 30239[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30246[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30240[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30242[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client connected from 30312[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30328[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30310[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30330[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30326[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30316[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30319[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30317[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client 30227[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30243[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client connected from 30320[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client 30245[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client connected from 30311[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30322[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30321[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30323[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30327[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30329[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30309[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30313[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client 30198[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30205[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client connected from 30325[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client 30244[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client 30237[0:0] has disconnected
Feb  1 19:02:58 joe acpid: client connected from 30318[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:02:58 joe acpid: client connected from 30324[0:0]
Feb  1 19:02:58 joe acpid: 1 client rule loaded
Feb  1 19:03:12 joe acpid: client 30241[0:0] has disconnected
Feb  1 19:03:12 joe acpid: client 30260[0:0] has disconnected
Feb  1 19:03:12 joe acpid: client 30271[0:0] has disconnected
Feb  1 19:03:12 joe acpid: client connected from 30413[0:0]
Feb  1 19:03:12 joe acpid: 1 client rule loaded
Feb  1 19:03:12 joe acpid: client connected from 30415[0:0]
Feb  1 19:03:12 joe acpid: 1 client rule loaded
Feb  1 19:03:12 joe acpid: client connected from 30412[0:0]
Feb  1 19:03:12 joe acpid: 1 client rule loaded
Feb  1 19:03:12 joe acpid: client connected from 30417[0:0]
Feb  1 19:03:12 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe dbus[1463]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb  1 19:03:13 joe acpid: client 30263[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30270[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30261[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30268[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30262[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30272[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30273[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30265[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30276[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30275[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30278[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30277[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30279[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30280[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30282[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30267[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30266[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30274[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30264[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30299[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30300[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30301[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30315[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30314[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30312[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30328[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30310[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30330[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30326[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30316[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30319[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30317[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30320[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30311[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30322[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30321[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30323[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30327[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30329[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30309[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30313[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30325[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30318[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30324[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30413[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30415[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30412[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30417[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client connected from 30418[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client 30418[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client connected from 30421[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client 30421[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client connected from 30422[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client 30422[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client connected from 30420[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client 30420[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client connected from 30414[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client 30414[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client connected from 30427[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client 30427[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client connected from 30416[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client 30416[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client connected from 30425[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client 30425[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client connected from 30430[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client 30430[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client connected from 30443[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client 30443[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client connected from 30419[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client 30419[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client connected from 30439[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30429[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30432[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30424[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30441[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30468[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30442[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30438[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30469[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30471[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30437[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30431[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30426[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30436[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30433[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30435[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client 30424[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client connected from 30473[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client 30439[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client connected from 30472[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30470[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30480[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30482[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30484[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30485[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30489[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30488[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30491[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30493[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30497[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30504[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30496[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30490[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30501[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30503[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30499[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30517[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30520[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30532[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30527[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client 30442[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30437[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30436[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30435[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client connected from 30537[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30534[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30538[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30528[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30531[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30521[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30522[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30529[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30518[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30524[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30500[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30530[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30525[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30495[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30519[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30539[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30541[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client 30469[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30482[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client 30484[0:0] has disconnected
Feb  1 19:03:13 joe acpid: client connected from 30516[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30535[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30561[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30536[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30560[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30567[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30570[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30571[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30498[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:13 joe acpid: client connected from 30586[0:0]
Feb  1 19:03:13 joe acpid: 1 client rule loaded
Feb  1 19:03:14 joe acpid: client connected from 30565[0:0]
Feb  1 19:03:14 joe acpid: 1 client rule loaded
Feb  1 19:03:14 joe acpid: client connected from 30592[0:0]
Feb  1 19:03:14 joe acpid: 1 client rule loaded
Feb  1 19:03:14 joe acpid: client connected from 30562[0:0]
Feb  1 19:03:14 joe acpid: 1 client rule loaded
Feb  1 19:03:14 joe acpid: client connected from 30593[0:0]
Feb  1 19:03:14 joe acpid: 1 client rule loaded
Feb  1 19:03:14 joe acpid: client connected from 30585[0:0]
Feb  1 19:03:14 joe acpid: 1 client rule loaded
Feb  1 19:03:14 joe acpid: client connected from 30573[0:0]
Feb  1 19:03:14 joe acpid: 1 client rule loaded
Feb  1 19:03:14 joe acpid: client connected from 30579[0:0]
Feb  1 19:03:14 joe acpid: 1 client rule loaded
Feb  1 19:03:14 joe acpid: client connected from 30568[0:0]
Feb  1 19:03:14 joe acpid: 1 client rule loaded
Feb  1 19:03:14 joe acpid: client connected from 30564[0:0]
Feb  1 19:03:14 joe acpid: 1 client rule loaded
Feb  1 19:03:14 joe acpid: client connected from 30574[0:0]
Feb  1 19:03:14 joe acpid: 1 client rule loaded
Feb  1 19:03:14 joe acpid: client connected from 30583[0:0]
Feb  1 19:03:14 joe acpid: 1 client rule loaded
Feb  1 19:03:14 joe acpid: client connected from 30566[0:0]
Feb  1 19:03:14 joe acpid: 1 client rule loaded
Feb  1 19:03:21 joe acpid: client 30429[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30432[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30441[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30468[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30438[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30471[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30431[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30426[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30433[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30473[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30472[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30470[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30480[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30485[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30489[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30488[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30491[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30493[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30497[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30504[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30496[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30490[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30501[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30503[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30499[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30517[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30520[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30532[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30527[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30537[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30534[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30538[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30528[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30531[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30521[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30522[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30529[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30518[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30524[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30500[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30530[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30525[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30495[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30519[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30539[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30541[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30516[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30535[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30561[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30536[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30560[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30567[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30570[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30571[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30498[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30586[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30565[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30592[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30562[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30593[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30585[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30573[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30579[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30568[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30564[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30574[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30583[0:0] has disconnected
Feb  1 19:03:21 joe acpid: client 30566[0:0] has disconnected
Feb  1 19:03:22 joe acpid: client connected from 30755[0:0]
Feb  1 19:03:22 joe acpid: 1 client rule loaded
Feb  1 19:03:22 joe acpid: client 30755[0:0] has disconnected
Feb  1 19:03:22 joe acpid: client connected from 30763[0:0]
Feb  1 19:03:22 joe acpid: 1 client rule loaded
Feb  1 19:03:22 joe acpid: client 30763[0:0] has disconnected
Feb  1 19:03:22 joe acpid: client connected from 30757[0:0]
Feb  1 19:03:22 joe acpid: 1 client rule loaded
Feb  1 19:03:22 joe acpid: client 30757[0:0] has disconnected
Feb  1 19:03:22 joe acpid: client connected from 30762[0:0]
Feb  1 19:03:22 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30762[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30768[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30768[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30766[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30766[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30767[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30767[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30788[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30788[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30770[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30770[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30761[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30761[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30760[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30760[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30787[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30787[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30771[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30771[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30786[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30786[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30758[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30758[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30780[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30780[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30779[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30779[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30764[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30764[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30776[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30776[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30775[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30775[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30782[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30782[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30783[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30783[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30765[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client 30765[0:0] has disconnected
Feb  1 19:03:23 joe acpid: client connected from 30789[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client connected from 30822[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client connected from 30772[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client connected from 30821[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client connected from 30820[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client connected from 30759[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client connected from 30774[0:0]
Feb  1 19:03:23 joe acpid: 1 client rule loaded
Feb  1 19:03:23 joe acpid: client connected from 30814[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30784[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30777[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30817[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30816[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30846[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30818[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30830[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30815[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30833[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30831[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30819[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30841[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30838[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30835[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30834[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30840[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30842[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30839[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30844[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30856[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30859[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30861[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30862[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30857[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30866[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30864[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30865[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30858[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30881[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30863[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client 30774[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30814[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30835[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30834[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client connected from 30883[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client 30820[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client connected from 30879[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30884[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30885[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client 30772[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30777[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30856[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30859[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30864[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client connected from 30876[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client 30821[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30759[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30844[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30865[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30858[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client connected from 30880[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30882[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30897[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30877[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30896[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30900[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30903[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30902[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30901[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30899[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30908[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30909[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30904[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30911[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30921[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30917[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30912[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30915[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30914[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30919[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30916[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client 30822[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30784[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30816[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30846[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30830[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30833[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30841[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30861[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30883[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30884[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30876[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30880[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30882[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30896[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30900[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client connected from 30920[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30905[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30906[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30910[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30949[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30948[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30956[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30958[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30950[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30952[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30964[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30963[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30960[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30966[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30953[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 31007[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 31008[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30977[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 31004[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30967[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30972[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30969[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30978[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client 30817[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30819[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30840[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30881[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30885[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30897[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30901[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client connected from 30979[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30957[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30968[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30971[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 31003[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30976[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30970[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30965[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 30974[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client connected from 31005[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client 30815[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30831[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30877[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30964[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client connected from 31010[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client 30857[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30866[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30863[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30902[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client connected from 30955[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client 30839[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30862[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30879[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30904[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client connected from 30961[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client 30914[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30916[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30920[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client connected from 31009[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client 30921[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30905[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30910[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client connected from 30973[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client 30911[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client connected from 30975[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client 30842[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30912[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client connected from 31002[0:0]
Feb  1 19:03:24 joe acpid: 1 client rule loaded
Feb  1 19:03:24 joe acpid: client 30789[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30915[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client 30906[0:0] has disconnected
Feb  1 19:03:24 joe acpid: client connected from 31011[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client 30818[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30838[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30903[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30899[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30908[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30909[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30917[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30919[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30948[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30956[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30958[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30952[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30953[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30978[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30957[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30974[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 31010[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client connected from 31023[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31022[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31025[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client 31008[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 31004[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30972[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30976[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 31025[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client connected from 31026[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31029[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31028[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31034[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client 30970[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30961[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30973[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 31029[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client connected from 31038[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31036[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client 30949[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30950[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30966[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 31007[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30968[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 30971[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 31003[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client 31002[0:0] has disconnected
Feb  1 19:03:25 joe acpid: client connected from 31035[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31039[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31044[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31045[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31051[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31049[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31050[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31047[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31055[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31048[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31060[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31061[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31062[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31077[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31083[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31079[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31081[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31099[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31101[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31096[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31104[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31115[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31118[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31117[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:25 joe acpid: client connected from 31122[0:0]
Feb  1 19:03:25 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client 30963[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 30960[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 30977[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 30967[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 30969[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 30979[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 30965[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31005[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 30955[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31009[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 30975[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31011[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31023[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31022[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31026[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31028[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31034[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31038[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31036[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31035[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31039[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31044[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31045[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31051[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31049[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31050[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31047[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31055[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31048[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31060[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31061[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31062[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31077[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31083[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31079[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31081[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31099[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31101[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31096[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31104[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31115[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31118[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31117[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31122[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client connected from 31263[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31267[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31265[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31264[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31273[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31271[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31282[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31276[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31274[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31277[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31278[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31272[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client 31263[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31267[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31265[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client 31264[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client connected from 31275[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31281[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31298[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31292[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31302[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31310[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31294[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31307[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31293[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31299[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31296[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31301[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31303[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31305[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31308[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31300[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31306[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31311[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31309[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client 31275[0:0] has disconnected
Feb  1 19:03:27 joe acpid: client connected from 31297[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31304[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:27 joe acpid: client connected from 31295[0:0]
Feb  1 19:03:27 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31344[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31337[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31333[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31336[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31339[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client 31273[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31271[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31282[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31276[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31274[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31278[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31272[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31281[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client connected from 31342[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31343[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client 31277[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client connected from 31338[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31355[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31340[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31359[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31341[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31356[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31360[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31357[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31373[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31379[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31375[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client 31298[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31311[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client connected from 31361[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31382[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31358[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31354[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31380[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31378[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31372[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31371[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31376[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31377[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31374[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client 31292[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31302[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31310[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31307[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31299[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31301[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31305[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31308[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31300[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31306[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31304[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31295[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client connected from 31400[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client 31294[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31293[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31296[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31303[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31309[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31297[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31344[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31337[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client 31343[0:0] has disconnected
Feb  1 19:03:28 joe acpid: client connected from 31401[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31402[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31403[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:28 joe acpid: client connected from 31415[0:0]
Feb  1 19:03:28 joe acpid: 1 client rule loaded
Feb  1 19:03:41 joe acpid: client connected from 31419[0:0]
Feb  1 19:03:41 joe acpid: 1 client rule loaded
Feb  1 19:03:41 joe acpid: client connected from 31398[0:0]
Feb  1 19:03:41 joe acpid: 1 client rule loaded
Feb  1 19:03:41 joe acpid: client connected from 31406[0:0]
Feb  1 19:03:41 joe acpid: 1 client rule loaded
Feb  1 19:03:41 joe acpid: client connected from 31397[0:0]
Feb  1 19:03:41 joe acpid: 1 client rule loaded
Feb  1 19:03:41 joe acpid: client connected from 31445[0:0]
Feb  1 19:03:41 joe acpid: 1 client rule loaded
Feb  1 19:03:41 joe acpid: client connected from 31395[0:0]
Feb  1 19:03:41 joe acpid: 1 client rule loaded
Feb  1 19:03:41 joe acpid: client 31333[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31336[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31339[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31342[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31338[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31355[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31340[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31359[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31341[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31356[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31360[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31357[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31373[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31379[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31375[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31361[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31382[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31358[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31354[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31380[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31378[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31372[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31371[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31376[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31377[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31374[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31400[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31401[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31402[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31403[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31415[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31419[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31398[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31406[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31397[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31445[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client 31395[0:0] has disconnected
Feb  1 19:03:41 joe acpid: client connected from 31396[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31396[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31407[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31407[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31412[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31412[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31411[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31411[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31414[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31414[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31413[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31413[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31410[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31410[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31418[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31418[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31399[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31399[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31450[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31450[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31446[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31446[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31453[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31453[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31404[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31404[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31447[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31447[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31449[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31449[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31452[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31452[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31448[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31511[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31497[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31451[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31523[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31501[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31496[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31517[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31509[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31505[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31503[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31504[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31527[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31528[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31521[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31500[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31516[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31510[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31515[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31554[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31563[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31498[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31577[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31555[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31575[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31557[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31524[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31558[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31508[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31526[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31559[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31522[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31512[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31578[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31574[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31506[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31520[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31514[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31502[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31576[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31553[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31560[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31565[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31552[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31518[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31562[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31584[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31587[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31586[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31595[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31590[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31596[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31592[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31603[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31591[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31588[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31605[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31607[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31608[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31610[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31601[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31604[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31621[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31617[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31625[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31631[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31618[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31509[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client 31565[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client connected from 31623[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31633[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31632[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31644[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31630[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31611[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31658[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31656[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31643[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client connected from 31638[0:0]
Feb  1 19:03:42 joe acpid: 1 client rule loaded
Feb  1 19:03:42 joe acpid: client 31511[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client 31498[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client 31524[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client 31559[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client 31514[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client 31518[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client 31595[0:0] has disconnected
Feb  1 19:03:42 joe acpid: client 31608[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31636[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31496[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31500[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31516[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31510[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31575[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31558[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31526[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31574[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31520[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31502[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31576[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31553[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31587[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31586[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31590[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31607[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31630[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31635[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31644[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31637[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31633[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31626[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31624[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31641[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31632[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31634[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31523[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31517[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31554[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31563[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31555[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31557[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31508[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31578[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31506[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31562[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31584[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31591[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31656[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31634[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31685[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31448[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31451[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31501[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31505[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31521[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31515[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31577[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31522[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31512[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31552[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31596[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31603[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31588[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31685[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31696[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31497[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31527[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31610[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31692[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31504[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31592[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31625[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31704[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31528[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31605[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31601[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31631[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31704[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31690[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31604[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31617[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31635[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31624[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31641[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31692[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31697[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31503[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31560[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31621[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31618[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31623[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31611[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31658[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31643[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31636[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31695[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31698[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31638[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31691[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31637[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31626[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31696[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31690[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31691[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31689[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31689[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31699[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31703[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31697[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31695[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31688[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31688[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31700[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31684[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31693[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31702[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31706[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31708[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31686[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31724[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31728[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31705[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31408[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31733[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31735[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31698[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31699[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31703[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31700[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31684[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31693[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31762[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31737[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31417[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31702[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31761[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31754[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31753[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31765[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31705[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31760[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client 31686[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client 31408[0:0] has disconnected
Feb  1 19:03:43 joe acpid: client connected from 31764[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31763[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31778[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31781[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31783[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31785[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31786[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31789[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31790[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31788[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31793[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31796[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31798[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31801[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31799[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31804[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31823[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31831[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31830[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31834[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:43 joe acpid: client connected from 31836[0:0]
Feb  1 19:03:43 joe acpid: 1 client rule loaded
Feb  1 19:03:45 joe acpid: client 31706[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31708[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31724[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31728[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31733[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31735[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31762[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31737[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31417[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31761[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31754[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31753[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31765[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31760[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31764[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31763[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31778[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31781[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31783[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31785[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31786[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31789[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31790[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31788[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31793[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31796[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31798[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31801[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31799[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31804[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31823[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31831[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31830[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31834[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31836[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client connected from 31979[0:0]
Feb  1 19:03:45 joe acpid: 1 client rule loaded
Feb  1 19:03:45 joe acpid: client connected from 31978[0:0]
Feb  1 19:03:45 joe acpid: 1 client rule loaded
Feb  1 19:03:45 joe acpid: client connected from 31982[0:0]
Feb  1 19:03:45 joe acpid: 1 client rule loaded
Feb  1 19:03:45 joe acpid: client connected from 31981[0:0]
Feb  1 19:03:45 joe acpid: 1 client rule loaded
Feb  1 19:03:45 joe acpid: client connected from 31988[0:0]
Feb  1 19:03:45 joe acpid: 1 client rule loaded
Feb  1 19:03:45 joe acpid: client connected from 31986[0:0]
Feb  1 19:03:45 joe acpid: 1 client rule loaded
Feb  1 19:03:45 joe acpid: client 31978[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client connected from 31987[0:0]
Feb  1 19:03:45 joe acpid: 1 client rule loaded
Feb  1 19:03:45 joe acpid: client 31979[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client 31982[0:0] has disconnected
Feb  1 19:03:45 joe acpid: client connected from 31989[0:0]
Feb  1 19:03:45 joe acpid: 1 client rule loaded
Feb  1 19:03:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,987910 seconds 
Feb  1 19:03:46 joe acpid: client 31981[0:0] has disconnected
Feb  1 19:03:46 joe acpid: client 31986[0:0] has disconnected
Feb  1 19:03:46 joe acpid: client connected from 32005[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32003[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32011[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32008[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32001[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 31997[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32006[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32013[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32016[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32010[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32015[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32020[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 31999[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32009[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32000[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32045[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 31998[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32007[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32057[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32022[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client 31988[0:0] has disconnected
Feb  1 19:03:46 joe acpid: client 31989[0:0] has disconnected
Feb  1 19:03:46 joe acpid: client connected from 32019[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32014[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32051[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client 31987[0:0] has disconnected
Feb  1 19:03:46 joe acpid: client connected from 32002[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32055[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32025[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32054[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32023[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32026[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32021[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32004[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32028[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32061[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32062[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,586263 seconds 
Feb  1 19:03:46 joe acpid: client connected from 32080[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32052[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32056[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32058[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32078[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32063[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32059[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32084[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32076[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32087[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32077[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32079[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32081[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32082[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32085[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32083[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe acpid: client connected from 32086[0:0]
Feb  1 19:03:46 joe acpid: 1 client rule loaded
Feb  1 19:03:46 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,938567 seconds 
Feb  1 19:03:57 joe acpid: client 32005[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32003[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32011[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32008[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32001[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 31997[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32006[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32013[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32016[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32010[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32015[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32020[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 31999[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32009[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32000[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32045[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 31998[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32007[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32057[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32022[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32019[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32014[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32051[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32002[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32055[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32025[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32054[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32023[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32026[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32021[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32004[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32028[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32061[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32062[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32080[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32052[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32056[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32058[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32078[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32063[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32059[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32084[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32076[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32087[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32077[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32079[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32081[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32082[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32085[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32083[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client 32086[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client connected from 32166[0:0]
Feb  1 19:03:57 joe acpid: 1 client rule loaded
Feb  1 19:03:57 joe acpid: client 32166[0:0] has disconnected
Feb  1 19:03:57 joe acpid: client connected from 32172[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32172[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32173[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32173[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32167[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32167[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32168[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32168[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32178[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32178[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32174[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32174[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32180[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32180[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32179[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32179[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32190[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32190[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32183[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32183[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32198[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32198[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32191[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32191[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32189[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32189[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32177[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32177[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32184[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32184[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32185[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32185[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32187[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32188[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32182[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32169[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32171[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32193[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32197[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32195[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32170[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32196[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32217[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32224[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32240[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32221[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32229[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32223[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32222[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32233[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32230[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32237[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32235[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32228[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32232[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32236[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32238[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32251[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32255[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32262[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32252[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32228[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client 32236[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client 32255[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32250[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32260[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32263[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32258[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32259[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32261[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32266[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32273[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32272[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32279[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32276[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32297[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32285[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32278[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32295[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32287[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32290[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32284[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32281[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32291[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32282[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32292[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32277[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32298[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32286[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32171[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client 32193[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client 32197[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client 32170[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32288[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32187[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client 32230[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client 32250[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client 32259[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32296[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client 32223[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client 32235[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client 32238[0:0] has disconnected
Feb  1 19:03:58 joe acpid: client connected from 32280[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:58 joe acpid: client connected from 32274[0:0]
Feb  1 19:03:58 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32299[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client 32196[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32229[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32237[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32232[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32252[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32258[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32261[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32272[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32279[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32276[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32285[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32278[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32287[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32290[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32281[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32291[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32282[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32298[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32286[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32274[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32299[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client connected from 32293[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32320[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32321[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32323[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32328[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client 32188[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32169[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32217[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32224[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32240[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32221[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32233[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32251[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32262[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32260[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32263[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32266[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32273[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32284[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32292[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32277[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32296[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32293[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32320[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client connected from 32326[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client 32288[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client connected from 32332[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32333[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32337[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32334[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32336[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client 32295[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client connected from 32343[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32346[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32347[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client 32182[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32195[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32222[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32297[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32280[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32321[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client connected from 32327[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32373[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32360[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32363[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32376[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32387[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32383[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32379[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32390[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32338[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32335[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32365[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32356[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32350[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32384[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32368[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32355[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32371[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32361[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32382[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32393[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32367[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32391[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32381[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32353[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32364[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32340[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client 32323[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32328[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32326[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32332[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32333[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32337[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32334[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32373[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32379[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client connected from 32354[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32359[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32375[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32388[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client 32336[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32343[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32346[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32347[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32327[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32360[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32363[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32376[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32387[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32383[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32390[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32335[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32356[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32384[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client connected from 32377[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32341[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32389[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client 32368[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32355[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32371[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32382[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32353[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32359[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client connected from 32392[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32352[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32386[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32345[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client 32345[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client connected from 32380[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32374[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32370[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32369[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32348[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client 32388[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client connected from 32358[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32366[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client 32338[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32365[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32393[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32367[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32391[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32364[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32340[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32354[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32377[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32341[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32389[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32386[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client connected from 32372[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32351[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32378[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32357[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32385[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32362[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32329[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32463[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32467[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client 32381[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32352[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32374[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32370[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client connected from 32470[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client 32350[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32361[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32375[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client 32392[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client connected from 32468[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32465[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client 32348[0:0] has disconnected
Feb  1 19:03:59 joe acpid: client connected from 32464[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32473[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32471[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32472[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32481[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32483[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32507[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32509[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32512[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32514[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32510[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:03:59 joe acpid: client connected from 32518[0:0]
Feb  1 19:03:59 joe acpid: 1 client rule loaded
Feb  1 19:04:01 joe acpid: client 32380[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32369[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32358[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32366[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32372[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32351[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32378[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32357[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32385[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32362[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32329[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32463[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32467[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32470[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32468[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32465[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32464[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32473[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32471[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32472[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32481[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32483[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32507[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32509[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32512[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32514[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32510[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client 32518[0:0] has disconnected
Feb  1 19:04:01 joe acpid: client connected from 32662[0:0]
Feb  1 19:04:01 joe acpid: 1 client rule loaded
Feb  1 19:04:01 joe acpid: client connected from 32663[0:0]
Feb  1 19:04:01 joe acpid: 1 client rule loaded
Feb  1 19:04:01 joe acpid: client connected from 32666[0:0]
Feb  1 19:04:01 joe acpid: 1 client rule loaded
Feb  1 19:04:01 joe acpid: client connected from 32665[0:0]
Feb  1 19:04:01 joe acpid: 1 client rule loaded
Feb  1 19:04:01 joe acpid: client connected from 32670[0:0]
Feb  1 19:04:01 joe acpid: 1 client rule loaded
Feb  1 19:04:01 joe acpid: client connected from 32673[0:0]
Feb  1 19:04:01 joe acpid: 1 client rule loaded
Feb  1 19:04:01 joe acpid: client connected from 32672[0:0]
Feb  1 19:04:01 joe acpid: 1 client rule loaded
Feb  1 19:04:01 joe acpid: client connected from 32674[0:0]
Feb  1 19:04:01 joe acpid: 1 client rule loaded
Feb  1 19:04:01 joe acpid: client connected from 32669[0:0]
Feb  1 19:04:01 joe acpid: 1 client rule loaded
Feb  1 19:04:01 joe acpid: client connected from 32675[0:0]
Feb  1 19:04:01 joe acpid: 1 client rule loaded
Feb  1 19:04:01 joe acpid: client connected from 32671[0:0]
Feb  1 19:04:01 joe acpid: 1 client rule loaded
Feb  1 19:04:01 joe acpid: client connected from 32667[0:0]
Feb  1 19:04:01 joe acpid: 1 client rule loaded
Feb  1 19:04:01 joe acpid: client connected from 32676[0:0]
Feb  1 19:04:01 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,299692 seconds 
Feb  1 19:04:02 joe acpid: client 32662[0:0] has disconnected
Feb  1 19:04:02 joe acpid: client 32663[0:0] has disconnected
Feb  1 19:04:02 joe acpid: client 32666[0:0] has disconnected
Feb  1 19:04:02 joe acpid: client 32665[0:0] has disconnected
Feb  1 19:04:02 joe acpid: client 32670[0:0] has disconnected
Feb  1 19:04:02 joe acpid: client 32673[0:0] has disconnected
Feb  1 19:04:02 joe acpid: client 32672[0:0] has disconnected
Feb  1 19:04:02 joe acpid: client 32674[0:0] has disconnected
Feb  1 19:04:02 joe acpid: client 32669[0:0] has disconnected
Feb  1 19:04:02 joe acpid: client 32675[0:0] has disconnected
Feb  1 19:04:02 joe acpid: client 32671[0:0] has disconnected
Feb  1 19:04:02 joe acpid: client 32667[0:0] has disconnected
Feb  1 19:04:02 joe acpid: client 32676[0:0] has disconnected
Feb  1 19:04:02 joe acpid: client connected from 32696[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe acpid: client connected from 32693[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe acpid: client connected from 32695[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe acpid: client connected from 32700[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe acpid: client connected from 32699[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,311104 seconds 
Feb  1 19:04:02 joe acpid: client connected from 32712[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe acpid: client connected from 32697[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe acpid: client connected from 32702[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe acpid: client connected from 32704[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe acpid: client connected from 32707[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe acpid: client connected from 32710[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe acpid: client connected from 32706[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe acpid: client connected from 32698[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe acpid: client connected from 32713[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe acpid: client connected from 32709[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe acpid: client connected from 32708[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe acpid: client connected from 32701[0:0]
Feb  1 19:04:02 joe acpid: 1 client rule loaded
Feb  1 19:04:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,533654 seconds 
Feb  1 19:04:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,557880 seconds 
Feb  1 19:04:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,571411 seconds 
Feb  1 19:04:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,584585 seconds 
Feb  1 19:04:02 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,586722 seconds 
Feb  1 19:04:10 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,608318 seconds 
Feb  1 19:04:10 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,622232 seconds 
Feb  1 19:04:10 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,635058 seconds 
Feb  1 19:04:10 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,700610 seconds 
Feb  1 19:04:10 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,714970 seconds 
Feb  1 19:04:10 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,727536 seconds 
Feb  1 19:04:10 joe acpid: client 32696[0:0] has disconnected
Feb  1 19:04:10 joe acpid: client 32693[0:0] has disconnected
Feb  1 19:04:10 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,786180 seconds 
Feb  1 19:04:10 joe acpid: client 32695[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client 32700[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client 32699[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client 32712[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client 32697[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client 32702[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client 32704[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client 32707[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client 32710[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client 32706[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client 32698[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client 32713[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client 32709[0:0] has disconnected
Feb  1 19:04:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,086800 seconds 
Feb  1 19:04:11 joe acpid: client 32708[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client 32701[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client connected from 32760[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client 32760[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client connected from 302[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client 302[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client connected from 303[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client 303[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client connected from 32764[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client 32764[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client connected from 32765[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client 32765[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client connected from 306[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client 306[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client connected from 32761[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client 32761[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client connected from 319[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client 319[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client connected from 32767[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client 32767[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client connected from 307[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client 307[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client connected from 32763[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client 32763[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client connected from 339[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 32766[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 308[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 313[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 318[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 341[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 314[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 317[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 311[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 338[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 309[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 340[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 346[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 342[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 343[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 344[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 345[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 363[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 365[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 375[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 370[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 369[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 377[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 371[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 374[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 381[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 359[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 379[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 383[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 389[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 367[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 382[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 373[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 364[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 361[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 362[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 360[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 385[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 387[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 410[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 408[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 380[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 388[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 376[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,657067 seconds 
Feb  1 19:04:11 joe acpid: client connected from 409[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 416[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 421[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 418[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 420[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 423[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 425[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 417[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 424[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 419[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 422[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 466[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 468[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 485[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 470[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 480[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client 359[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client 360[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client connected from 510[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client 313[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client 318[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client 387[0:0] has disconnected
Feb  1 19:04:11 joe acpid: client connected from 509[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 469[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 473[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 478[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 520[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 481[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 482[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 517[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,981858 seconds 
Feb  1 19:04:11 joe acpid: client connected from 483[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 486[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 467[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 488[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 518[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 514[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:11 joe acpid: client connected from 471[0:0]
Feb  1 19:04:11 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 484[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 516[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 476[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 515[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 511[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 508[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 479[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 475[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 512[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 513[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 487[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client 32766[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 308[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 314[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 317[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 311[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 338[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 309[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 340[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 342[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 343[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 344[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 345[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 363[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 365[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 375[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 370[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 369[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 377[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 371[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 374[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 381[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 379[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 383[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 389[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 367[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 382[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 373[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 364[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 361[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 362[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 385[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 410[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 408[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 380[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 388[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 376[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 409[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 416[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 421[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 418[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 420[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 423[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 425[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 417[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 424[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 419[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 422[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 466[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 468[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 485[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 470[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 480[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 469[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 473[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 520[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 481[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 482[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 517[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 486[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 488[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 518[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 471[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 484[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 516[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 476[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 511[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 512[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client connected from 519[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client 339[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 341[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 346[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 479[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client connected from 544[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client 510[0:0] has disconnected
Feb  1 19:04:12 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,243967 seconds 
Feb  1 19:04:12 joe acpid: client 509[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 478[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 483[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 467[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 514[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 515[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 508[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 475[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client 513[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client connected from 551[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client 551[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client connected from 547[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client 547[0:0] has disconnected
Feb  1 19:04:12 joe acpid: client connected from 548[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 554[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 552[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 555[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 559[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 558[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 543[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 546[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:12 joe acpid: client connected from 560[0:0]
Feb  1 19:04:12 joe acpid: 1 client rule loaded
Feb  1 19:04:13 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,866615 seconds 
Feb  1 19:04:13 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,861005 seconds 
Feb  1 19:04:13 joe acpid: client 487[0:0] has disconnected
Feb  1 19:04:13 joe acpid: client 519[0:0] has disconnected
Feb  1 19:04:13 joe acpid: client 544[0:0] has disconnected
Feb  1 19:04:13 joe acpid: client 548[0:0] has disconnected
Feb  1 19:04:13 joe acpid: client 554[0:0] has disconnected
Feb  1 19:04:13 joe acpid: client 552[0:0] has disconnected
Feb  1 19:04:13 joe acpid: client 555[0:0] has disconnected
Feb  1 19:04:13 joe acpid: client 559[0:0] has disconnected
Feb  1 19:04:13 joe acpid: client 558[0:0] has disconnected
Feb  1 19:04:13 joe acpid: client 543[0:0] has disconnected
Feb  1 19:04:13 joe acpid: client 546[0:0] has disconnected
Feb  1 19:04:13 joe acpid: client 560[0:0] has disconnected
Feb  1 19:04:13 joe acpid: client connected from 684[0:0]
Feb  1 19:04:13 joe acpid: 1 client rule loaded
Feb  1 19:04:13 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,160886 seconds 
Feb  1 19:04:13 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,171909 seconds 
Feb  1 19:04:13 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,184858 seconds 
Feb  1 19:04:13 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,200664 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,233437 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,242545 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,251486 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,263023 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,271597 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,281561 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,289698 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,294084 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,318589 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,326878 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,333736 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,340783 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,350239 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,365186 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,348646 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,360721 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,374369 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,382511 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,394062 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,416657 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,425711 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,435272 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,445897 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,457437 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,468715 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,478594 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,488991 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,501917 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,520836 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,540868 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,556646 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,547304 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,559177 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,570206 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,581508 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,591528 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,602036 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,612811 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,623139 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,634447 seconds 
Feb  1 19:04:14 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,648953 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,663736 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,686220 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,702004 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,717665 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,730126 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,754197 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,773689 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,797135 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,809097 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,835199 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,855874 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,880803 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,876971 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,898399 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,918444 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,942839 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,961038 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 0,982969 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,009445 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,030834 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,049963 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,062345 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,074185 seconds 
Feb  1 19:04:15 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,086119 seconds 
Feb  1 19:04:21 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,104784 seconds 
Feb  1 19:04:27 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,159836 seconds 
Feb  1 19:04:27 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,188074 seconds 
Feb  1 19:04:27 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,212451 seconds 
Feb  1 19:04:27 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,227384 seconds 
Feb  1 19:04:27 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,726692 seconds 
Feb  1 19:04:27 joe acpid: client 684[0:0] has disconnected
Feb  1 19:04:27 joe acpid: client connected from 936[0:0]
Feb  1 19:04:27 joe acpid: 1 client rule loaded
Feb  1 19:04:27 joe acpid: client 936[0:0] has disconnected
Feb  1 19:04:27 joe acpid: client connected from 939[0:0]
Feb  1 19:04:27 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,644884 seconds 
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 939[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 942[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 942[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 938[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 938[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 943[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 943[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 940[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 940[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 953[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 953[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 937[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 937[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 952[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 952[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 949[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 949[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 950[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 950[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 951[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 951[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 961[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 961[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 960[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 960[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 963[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 963[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 962[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 962[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 967[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 967[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 964[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 966[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 970[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 972[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 969[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 974[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 975[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 976[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 977[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 994[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 980[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 985[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1002[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 981[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 979[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 986[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 988[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 995[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 973[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 993[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 997[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 999[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 978[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 983[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 984[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1000[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 987[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 982[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 996[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 990[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 998[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 991[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 992[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1102[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1073[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1061[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1029[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1031[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1063[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1026[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1065[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1090[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1085[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1044[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1076[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1093[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1066[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1043[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1083[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1011[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1054[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1053[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1069[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1094[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1055[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1081[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1042[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1091[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1051[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1052[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1028[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client 1065[0:0] has disconnected
Feb  1 19:04:28 joe acpid: client connected from 1087[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1070[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1027[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1018[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1004[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1089[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:28 joe acpid: client connected from 1017[0:0]
Feb  1 19:04:28 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1016[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1001[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1086[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1078[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1092[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1007[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1057[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1006[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1103[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1101[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1021[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1037[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1060[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1075[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1038[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1036[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1074[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client 974[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1102[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client connected from 1100[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1003[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1084[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1030[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1033[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1035[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1062[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1072[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1008[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1046[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1015[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1014[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 965[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1049[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1097[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1041[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1064[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client 964[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 966[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 970[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 972[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 969[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 975[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 976[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 977[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 994[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 980[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 985[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1002[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 981[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 979[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 986[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 988[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 995[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 973[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 993[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 997[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 999[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 978[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 983[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 984[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1000[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 987[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 982[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 996[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 990[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 998[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 991[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 992[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1073[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1061[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1029[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1031[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1063[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1026[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1090[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1085[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1044[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1076[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1093[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1066[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1043[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1083[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1011[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1054[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1053[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1069[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1094[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1055[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1081[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1042[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1091[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1051[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1052[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1028[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1087[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1070[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1027[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1018[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1004[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1089[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1017[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1016[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1001[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1086[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1078[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1092[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1007[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1057[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1006[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1103[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1101[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1021[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1037[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1060[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1075[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1038[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1036[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1074[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1100[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1084[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1030[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1033[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1062[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1008[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1046[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1015[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 965[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1064[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client connected from 1098[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client 1003[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1072[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1097[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1041[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1098[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client connected from 1020[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client 1020[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client connected from 1096[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client 1096[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client connected from 1082[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client 1082[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client connected from 1025[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1095[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client 1095[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client connected from 1088[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1080[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client 1080[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client connected from 1022[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client 1022[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client connected from 1058[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client 1058[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client connected from 1010[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1009[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client 1035[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1014[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1049[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1025[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client 1088[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client connected from 1045[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1039[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1012[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1005[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1079[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1040[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1077[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1050[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1024[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1068[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1067[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1099[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1034[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1056[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client 1010[0:0] has disconnected
Feb  1 19:04:29 joe acpid: client connected from 1071[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1048[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1032[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1059[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1023[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:29 joe acpid: client connected from 1047[0:0]
Feb  1 19:04:29 joe acpid: 1 client rule loaded
Feb  1 19:04:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,374537 seconds 
Feb  1 19:04:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,386630 seconds 
Feb  1 19:04:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,405118 seconds 
Feb  1 19:04:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,428857 seconds 
Feb  1 19:04:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,448027 seconds 
Feb  1 19:04:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,463861 seconds 
Feb  1 19:04:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,484330 seconds 
Feb  1 19:04:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,504144 seconds 
Feb  1 19:04:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,521569 seconds 
Feb  1 19:04:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,555661 seconds 
Feb  1 19:04:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,574054 seconds 
Feb  1 19:04:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,595765 seconds 
Feb  1 19:04:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,616194 seconds 
Feb  1 19:04:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,636398 seconds 
Feb  1 19:04:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,708066 seconds 
Feb  1 19:04:30 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,731621 seconds 
Feb  1 19:04:41 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,320607 seconds 
Feb  1 19:04:41 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,337747 seconds 
Feb  1 19:04:41 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,345131 seconds 
Feb  1 19:04:41 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,163732 seconds 
Feb  1 19:04:41 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,817510 seconds 
Feb  1 19:04:41 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,830449 seconds 
Feb  1 19:04:41 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,853243 seconds 
Feb  1 19:04:41 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,871614 seconds 
Feb  1 19:04:42 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,633941 seconds 
Feb  1 19:04:42 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,554969 seconds 
Feb  1 19:04:42 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,558699 seconds 
Feb  1 19:04:42 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,559222 seconds 
Feb  1 19:04:42 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,550564 seconds 
Feb  1 19:04:42 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,553928 seconds 
Feb  1 19:04:42 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,551964 seconds 
Feb  1 19:04:42 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,563236 seconds 
Feb  1 19:04:42 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,572501 seconds 
Feb  1 19:04:42 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,586604 seconds 
Feb  1 19:04:42 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,598758 seconds 
Feb  1 19:04:42 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,610076 seconds 
Feb  1 19:04:42 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,621106 seconds 
Feb  1 19:04:42 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,631967 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,642618 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,652254 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,663862 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,675518 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,689228 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,699513 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,649322 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,663439 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,676111 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,686644 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,696644 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,710424 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,721447 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,728867 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,742677 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,751769 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,766938 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,775537 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,790823 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,801578 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,813373 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,825434 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,840136 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,852020 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,865123 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,876588 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,891516 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,900495 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,913201 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,926519 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,939162 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,940984 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,956708 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,968810 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,984341 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 1,993097 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,008687 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,017468 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,030273 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,042688 seconds 
Feb  1 19:04:43 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,059716 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,069585 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,086221 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,095757 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,113252 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,124838 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,134868 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,147888 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,158390 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,170203 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,183454 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,195939 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,208683 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,219431 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,232321 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,245844 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,259341 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,272036 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,284036 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,297509 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,307880 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,321577 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,332230 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,346275 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,359574 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,373608 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,384121 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,397793 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,412978 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,427944 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,442672 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,455350 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,466157 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,480686 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,493032 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,503982 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,518125 seconds 
Feb  1 19:04:44 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,532996 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,644799 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,664574 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,684580 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,710789 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,737758 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,762547 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,784025 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,806041 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,831854 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,856562 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,877901 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,902667 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,923855 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,950490 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,965592 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,982107 seconds 
Feb  1 19:04:45 joe gdm3[2382]: WARNING: GdmDisplay: display lasted 2,997344 seconds 
Feb  1 19:04:51 joe acpid: client 1009[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1045[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1039[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1012[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1005[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1079[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1040[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1077[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1050[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1024[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1068[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1067[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1099[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1034[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1056[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1071[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1048[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1032[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1059[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1023[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client 1047[0:0] has disconnected
Feb  1 19:04:51 joe acpid: client connected from 2635[0:0]
Feb  1 19:04:51 joe acpid: 1 client rule loaded
Feb  1 19:04:51 joe acpid: client connected from 2639[0:0]
Feb  1 19:04:51 joe acpid: 1 client rule loaded
Feb  1 19:04:51 joe acpid: client connected from 2644[0:0]
Feb  1 19:04:51 joe acpid: 1 client rule loaded
Feb  1 19:04:51 joe acpid: client connected from 2642[0:0]
Feb  1 19:04:51 joe acpid: 1 client rule loaded
Feb  1 19:04:51 joe acpid: client connected from 2649[0:0]
Feb  1 19:04:51 joe acpid: 1 client rule loaded
Feb  1 19:04:51 joe acpid: client connected from 2647[0:0]
Feb  1 19:04:51 joe acpid: 1 client rule loaded
Feb  1 19:04:51 joe acpid: client connected from 2637[0:0]
Feb  1 19:04:51 joe acpid: 1 client rule loaded
Feb  1 19:04:51 joe acpid: client connected from 2648[0:0]
Feb  1 19:04:51 joe acpid: 1 client rule loaded
Feb  1 19:04:51 joe acpid: client connected from 2651[0:0]
Feb  1 19:04:51 joe acpid: 1 client rule loaded
Feb  1 19:04:51 joe acpid: client connected from 2636[0:0]
Feb  1 19:04:51 joe acpid: 1 client rule loaded
Feb  1 19:04:51 joe acpid: client connected from 2643[0:0]
Feb  1 19:04:51 joe acpid: 1 client rule loaded
Feb  1 19:04:51 joe acpid: client connected from 2645[0:0]
Feb  1 19:04:51 joe acpid: 1 client rule loaded
Feb  1 19:04:51 joe acpid: client connected from 2646[0:0]
Feb  1 19:04:51 joe acpid: 1 client rule loaded
Feb  1 19:04:51 joe acpid: client connected from 2638[0:0]
Feb  1 19:04:51 joe acpid: 1 client rule loaded
Feb  1 19:04:52 joe acpid: client 2635[0:0] has disconnected
Feb  1 19:04:52 joe acpid: client 2639[0:0] has disconnected
Feb  1 19:04:52 joe acpid: client connected from 2640[0:0]
Feb  1 19:04:52 joe acpid: 1 client rule loaded
Feb  1 19:04:52 joe acpid: client connected from 2650[0:0]
Feb  1 19:04:52 joe acpid: 1 client rule loaded
Feb  1 19:04:56 joe acpid: client 2644[0:0] has disconnected
Feb  1 19:04:56 joe acpid: client 2642[0:0] has disconnected
Feb  1 19:04:56 joe acpid: client 2649[0:0] has disconnected
Feb  1 19:04:56 joe acpid: client 2647[0:0] has disconnected
Feb  1 19:04:56 joe acpid: client 2637[0:0] has disconnected
Feb  1 19:04:56 joe acpid: client 2648[0:0] has disconnected
Feb  1 19:04:56 joe acpid: client 2651[0:0] has disconnected
Feb  1 19:04:56 joe acpid: client 2636[0:0] has disconnected
Feb  1 19:04:56 joe acpid: client 2643[0:0] has disconnected
Feb  1 19:04:56 joe acpid: client 2645[0:0] has disconnected
Feb  1 19:04:56 joe acpid: client 2646[0:0] has disconnected
Feb  1 19:04:56 joe acpid: client 2638[0:0] has disconnected
Feb  1 19:04:56 joe acpid: client 2640[0:0] has disconnected
Feb  1 19:04:56 joe acpid: client 2650[0:0] has disconnected
Feb  1 19:04:56 joe acpid: client connected from 2914[0:0]
Feb  1 19:04:56 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client 2914[0:0] has disconnected
Feb  1 19:05:01 joe acpid: client connected from 3154[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3153[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3156[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client 3154[0:0] has disconnected
Feb  1 19:05:01 joe acpid: client 3153[0:0] has disconnected
Feb  1 19:05:01 joe acpid: client 3156[0:0] has disconnected
Feb  1 19:05:01 joe acpid: client connected from 3163[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client 3163[0:0] has disconnected
Feb  1 19:05:01 joe acpid: client connected from 3165[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client 3165[0:0] has disconnected
Feb  1 19:05:01 joe acpid: client connected from 3159[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3160[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3166[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3164[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3167[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3168[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3169[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3162[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3161[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3172[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3175[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3155[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3176[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3178[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3179[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3157[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3180[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3177[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3185[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3173[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3181[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3184[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3182[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3188[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3190[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3189[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3194[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3191[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3192[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3193[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3186[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3174[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:01 joe acpid: client connected from 3187[0:0]
Feb  1 19:05:01 joe acpid: 1 client rule loaded
Feb  1 19:05:10 joe acpid: client 3159[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3160[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3166[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3164[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3167[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3168[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3169[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3162[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3161[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3172[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3175[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3155[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3176[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3178[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3179[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3157[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3180[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3177[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3185[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3173[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3181[0:0] has disconnected
Feb  1 19:05:10 joe acpid: client 3184[0:0] has disconnected
Feb  1 19:05:11 joe acpid: client 3182[0:0] has disconnected
Feb  1 19:05:11 joe acpid: client 3188[0:0] has disconnected
Feb  1 19:05:11 joe acpid: client 3190[0:0] has disconnected
Feb  1 19:05:11 joe acpid: client 3189[0:0] has disconnected
Feb  1 19:05:11 joe acpid: client 3194[0:0] has disconnected
Feb  1 19:05:11 joe acpid: client 3191[0:0] has disconnected
Feb  1 19:05:11 joe acpid: client 3192[0:0] has disconnected
Feb  1 19:05:11 joe acpid: client 3193[0:0] has disconnected
Feb  1 19:05:11 joe acpid: client 3186[0:0] has disconnected
Feb  1 19:05:11 joe acpid: client 3174[0:0] has disconnected
Feb  1 19:05:11 joe acpid: client 3187[0:0] has disconnected
Feb  1 19:05:11 joe acpid: client connected from 3469[0:0]
Feb  1 19:05:11 joe acpid: 1 client rule loaded
Feb  1 19:05:11 joe acpid: client 3469[0:0] has disconnected
Feb  1 19:05:11 joe acpid: client connected from 3471[0:0]
Feb  1 19:05:11 joe acpid: 1 client rule loaded
Feb  1 19:05:11 joe acpid: client 3471[0:0] has disconnected
Feb  1 19:05:11 joe acpid: client connected from 3468[0:0]
Feb  1 19:05:11 joe acpid: 1 client rule loaded
Feb  1 19:05:11 joe acpid: client 3468[0:0] has disconnected
Feb  1 19:05:12 joe acpid: client connected from 3478[0:0]
Feb  1 19:05:12 joe acpid: 1 client rule loaded
Feb  1 19:05:12 joe acpid: client 3478[0:0] has disconnected
Feb  1 19:05:12 joe acpid: client connected from 3482[0:0]
Feb  1 19:05:12 joe acpid: 1 client rule loaded
Feb  1 19:05:12 joe acpid: client 3482[0:0] has disconnected
Feb  1 19:05:12 joe acpid: client connected from 3475[0:0]
Feb  1 19:05:12 joe acpid: 1 client rule loaded
Feb  1 19:05:12 joe acpid: client 3475[0:0] has disconnected
Feb  1 19:05:12 joe acpid: client connected from 3474[0:0]
Feb  1 19:05:12 joe acpid: 1 client rule loaded
Feb  1 19:05:12 joe acpid: client 3474[0:0] has disconnected
Feb  1 19:05:12 joe acpid: client connected from 3481[0:0]
Feb  1 19:05:12 joe acpid: 1 client rule loaded
Feb  1 19:05:12 joe acpid: client 3481[0:0] has disconnected
Feb  1 19:05:12 joe acpid: client connected from 3483[0:0]
Feb  1 19:05:12 joe acpid: 1 client rule loaded
Feb  1 19:05:12 joe acpid: client 3483[0:0] has disconnected
Feb  1 19:05:12 joe acpid: client connected from 3479[0:0]
Feb  1 19:05:13 joe acpid: 1 client rule loaded
Feb  1 19:05:13 joe acpid: client 3479[0:0] has disconnected
Feb  1 19:05:15 joe acpid: client connected from 3477[0:0]
Feb  1 19:05:15 joe acpid: 1 client rule loaded
Feb  1 19:05:15 joe acpid: client 3477[0:0] has disconnected
Feb  1 19:05:15 joe acpid: client connected from 3480[0:0]
Feb  1 19:05:15 joe acpid: 1 client rule loaded
Feb  1 19:05:15 joe acpid: client 3480[0:0] has disconnected
Feb  1 19:05:15 joe acpid: client connected from 3500[0:0]
Feb  1 19:05:15 joe acpid: 1 client rule loaded
Feb  1 19:05:17 joe acpid: client 3500[0:0] has disconnected
Feb  1 19:05:17 joe acpid: client connected from 3486[0:0]
Feb  1 19:05:17 joe acpid: 1 client rule loaded
Feb  1 19:05:17 joe acpid: client 3486[0:0] has disconnected
Feb  1 19:05:17 joe acpid: client connected from 3498[0:0]
Feb  1 19:05:17 joe acpid: 1 client rule loaded
Feb  1 19:05:17 joe acpid: client 3498[0:0] has disconnected
Feb  1 19:05:17 joe acpid: client connected from 3487[0:0]
Feb  1 19:05:17 joe acpid: 1 client rule loaded
Feb  1 19:05:17 joe acpid: client 3487[0:0] has disconnected
Feb  1 19:05:17 joe acpid: client connected from 3499[0:0]
Feb  1 19:05:17 joe acpid: 1 client rule loaded
Feb  1 19:05:17 joe acpid: client 3499[0:0] has disconnected
Feb  1 19:05:17 joe acpid: client connected from 3513[0:0]
Feb  1 19:05:17 joe acpid: 1 client rule loaded
Feb  1 19:05:17 joe acpid: client 3513[0:0] has disconnected
Feb  1 19:05:17 joe acpid: client connected from 3510[0:0]
Feb  1 19:05:17 joe acpid: 1 client rule loaded
Feb  1 19:05:17 joe acpid: client 3510[0:0] has disconnected
Feb  1 19:05:17 joe acpid: client connected from 3504[0:0]
Feb  1 19:05:17 joe acpid: 1 client rule loaded
Feb  1 19:05:17 joe acpid: client 3504[0:0] has disconnected
Feb  1 19:05:18 joe acpid: client connected from 3502[0:0]
Feb  1 19:05:18 joe acpid: 1 client rule loaded
Feb  1 19:05:18 joe acpid: client 3502[0:0] has disconnected
Feb  1 19:05:18 joe acpid: client connected from 3512[0:0]
Feb  1 19:05:18 joe acpid: 1 client rule loaded
Feb  1 19:05:18 joe acpid: client 3512[0:0] has disconnected
Feb  1 19:05:18 joe acpid: client connected from 3503[0:0]
Feb  1 19:05:18 joe acpid: 1 client rule loaded
Feb  1 19:05:18 joe acpid: client 3503[0:0] has disconnected
Feb  1 19:05:18 joe acpid: client connected from 3476[0:0]
Feb  1 19:05:18 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client 3476[0:0] has disconnected
Feb  1 19:05:20 joe acpid: client connected from 3841[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client 3841[0:0] has disconnected
Feb  1 19:05:20 joe acpid: client connected from 3840[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client 3840[0:0] has disconnected
Feb  1 19:05:20 joe acpid: client connected from 3835[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client 3835[0:0] has disconnected
Feb  1 19:05:20 joe acpid: client connected from 3844[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client 3844[0:0] has disconnected
Feb  1 19:05:20 joe acpid: client connected from 3849[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client 3849[0:0] has disconnected
Feb  1 19:05:20 joe acpid: client connected from 3851[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client 3851[0:0] has disconnected
Feb  1 19:05:20 joe acpid: client connected from 3843[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client 3843[0:0] has disconnected
Feb  1 19:05:20 joe acpid: client connected from 3854[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client 3854[0:0] has disconnected
Feb  1 19:05:20 joe acpid: client connected from 3850[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client 3850[0:0] has disconnected
Feb  1 19:05:20 joe acpid: client connected from 3856[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client 3856[0:0] has disconnected
Feb  1 19:05:20 joe acpid: client connected from 3848[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client 3848[0:0] has disconnected
Feb  1 19:05:20 joe acpid: client connected from 3852[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client 3852[0:0] has disconnected
Feb  1 19:05:20 joe acpid: client connected from 3855[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client 3855[0:0] has disconnected
Feb  1 19:05:20 joe acpid: client connected from 3842[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client 3842[0:0] has disconnected
Feb  1 19:05:20 joe acpid: client connected from 3833[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client 3833[0:0] has disconnected
Feb  1 19:05:20 joe acpid: client connected from 3845[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 3846[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 3847[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 3862[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 3837[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 3872[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 3896[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 3870[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 3865[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 3871[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 3869[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 3868[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 3864[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 3866[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 3892[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 3895[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4092[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 3894[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4090[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4093[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4091[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4115[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4116[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4113[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4118[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4112[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4119[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4144[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4114[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4120[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4141[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4174[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4168[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4167[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4143[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4148[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4173[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4137[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4162[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4169[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4145[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4153[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4163[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4164[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4149[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4170[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4142[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4155[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4151[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4138[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4161[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4152[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4172[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4147[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4146[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4139[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:20 joe acpid: client connected from 4140[0:0]
Feb  1 19:05:20 joe acpid: 1 client rule loaded
Feb  1 19:05:30 joe acpid: client 3845[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 3846[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 3847[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 3862[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 3837[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 3872[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 3896[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 3870[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 3865[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 3871[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 3869[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 3868[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 3864[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 3866[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 3892[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 3895[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4092[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 3894[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4090[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4093[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4091[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4115[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4116[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4113[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4118[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4112[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4119[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4144[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4114[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4120[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4141[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4174[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4168[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4167[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4143[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4148[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4173[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4137[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4162[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4169[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4145[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4153[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4163[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4164[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4149[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4170[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4142[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4155[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4151[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4138[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4161[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4152[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4172[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4147[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4146[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4139[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client 4140[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client connected from 4902[0:0]
Feb  1 19:05:30 joe acpid: 1 client rule loaded
Feb  1 19:05:30 joe acpid: client 4902[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client connected from 4906[0:0]
Feb  1 19:05:30 joe acpid: 1 client rule loaded
Feb  1 19:05:30 joe acpid: client 4906[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client connected from 4914[0:0]
Feb  1 19:05:30 joe acpid: 1 client rule loaded
Feb  1 19:05:30 joe acpid: client 4914[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client connected from 4903[0:0]
Feb  1 19:05:30 joe acpid: 1 client rule loaded
Feb  1 19:05:30 joe acpid: client 4903[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client connected from 4910[0:0]
Feb  1 19:05:30 joe acpid: 1 client rule loaded
Feb  1 19:05:30 joe acpid: client 4910[0:0] has disconnected
Feb  1 19:05:30 joe acpid: client connected from 4912[0:0]
Feb  1 19:05:30 joe acpid: 1 client rule loaded
Feb  1 19:05:31 joe acpid: client 4912[0:0] has disconnected
Feb  1 19:05:31 joe acpid: client connected from 4915[0:0]
Feb  1 19:05:31 joe acpid: 1 client rule loaded
Feb  1 19:05:31 joe acpid: client 4915[0:0] has disconnected
Feb  1 19:05:31 joe acpid: client connected from 4904[0:0]
Feb  1 19:05:31 joe acpid: 1 client rule loaded
Feb  1 19:05:31 joe acpid: client 4904[0:0] has disconnected
Feb  1 19:05:31 joe acpid: client connected from 4907[0:0]
Feb  1 19:05:31 joe acpid: 1 client rule loaded
Feb  1 19:05:31 joe acpid: client 4907[0:0] has disconnected
Feb  1 19:05:32 joe acpid: client connected from 4917[0:0]
Feb  1 19:05:32 joe acpid: 1 client rule loaded
Feb  1 19:05:32 joe acpid: client 4917[0:0] has disconnected
Feb  1 19:05:32 joe acpid: client connected from 4905[0:0]
Feb  1 19:05:32 joe acpid: 1 client rule loaded
Feb  1 19:05:32 joe acpid: client 4905[0:0] has disconnected
Feb  1 19:05:32 joe acpid: client connected from 4909[0:0]
Feb  1 19:05:32 joe acpid: 1 client rule loaded
Feb  1 19:05:32 joe acpid: client 4909[0:0] has disconnected
Feb  1 19:05:32 joe acpid: client connected from 4918[0:0]
Feb  1 19:05:32 joe acpid: 1 client rule loaded
Feb  1 19:05:32 joe acpid: client 4918[0:0] has disconnected
Feb  1 19:05:32 joe acpid: client connected from 4911[0:0]
Feb  1 19:05:32 joe acpid: 1 client rule loaded
Feb  1 19:05:32 joe acpid: client 4911[0:0] has disconnected
Feb  1 19:05:32 joe acpid: client connected from 4913[0:0]
Feb  1 19:05:32 joe acpid: 1 client rule loaded
Feb  1 19:05:32 joe acpid: client 4913[0:0] has disconnected
Feb  1 19:05:32 joe acpid: client connected from 4916[0:0]
Feb  1 19:05:32 joe acpid: 1 client rule loaded
Feb  1 19:05:32 joe acpid: client 4916[0:0] has disconnected
Feb  1 19:05:32 joe acpid: client connected from 5039[0:0]
Feb  1 19:05:32 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client 5039[0:0] has disconnected
Feb  1 19:05:35 joe acpid: client connected from 5281[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5292[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5282[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5285[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5287[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5290[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5283[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5289[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5288[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5286[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5295[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5293[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5291[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5309[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5316[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5313[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5312[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5311[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5310[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client 5281[0:0] has disconnected
Feb  1 19:05:35 joe acpid: client 5292[0:0] has disconnected
Feb  1 19:05:35 joe acpid: client 5285[0:0] has disconnected
Feb  1 19:05:35 joe acpid: client connected from 5315[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5338[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5333[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5334[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5332[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5326[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5327[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client 5282[0:0] has disconnected
Feb  1 19:05:35 joe acpid: client 5283[0:0] has disconnected
Feb  1 19:05:35 joe acpid: client 5288[0:0] has disconnected
Feb  1 19:05:35 joe acpid: client 5286[0:0] has disconnected
Feb  1 19:05:35 joe acpid: client 5295[0:0] has disconnected
Feb  1 19:05:35 joe acpid: client connected from 5331[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5308[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5330[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5314[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5337[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5329[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5336[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5328[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client 5287[0:0] has disconnected
Feb  1 19:05:35 joe acpid: client 5289[0:0] has disconnected
Feb  1 19:05:35 joe acpid: client 5293[0:0] has disconnected
Feb  1 19:05:35 joe acpid: client connected from 5353[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client connected from 5354[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client 5291[0:0] has disconnected
Feb  1 19:05:35 joe acpid: client connected from 5352[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:35 joe acpid: client 5290[0:0] has disconnected
Feb  1 19:05:35 joe acpid: client connected from 5351[0:0]
Feb  1 19:05:35 joe acpid: 1 client rule loaded
Feb  1 19:05:43 joe acpid: client 5309[0:0] has disconnected
Feb  1 19:05:43 joe acpid: client 5316[0:0] has disconnected
Feb  1 19:05:43 joe acpid: client 5313[0:0] has disconnected
Feb  1 19:05:43 joe acpid: client 5312[0:0] has disconnected
Feb  1 19:05:43 joe acpid: client 5311[0:0] has disconnected
Feb  1 19:05:43 joe acpid: client 5310[0:0] has disconnected
Feb  1 19:05:43 joe acpid: client 5315[0:0] has disconnected
Feb  1 19:05:43 joe acpid: client 5338[0:0] has disconnected
Feb  1 19:05:43 joe acpid: client 5333[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client 5334[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client 5332[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client 5326[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client 5327[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client 5331[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client 5308[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client 5330[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client 5314[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client 5337[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client 5329[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client 5336[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client 5328[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client 5353[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client 5354[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client 5352[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client 5351[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client connected from 5591[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client 5591[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client connected from 5589[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client 5589[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client connected from 5594[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client 5594[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client connected from 5590[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client 5590[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client connected from 5599[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client 5599[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client connected from 5596[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client 5596[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client connected from 5602[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client 5602[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client connected from 5604[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client 5604[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client connected from 5601[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client 5601[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client connected from 5598[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client 5598[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client connected from 5595[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client 5595[0:0] has disconnected
Feb  1 19:05:44 joe acpid: client connected from 5741[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client connected from 5742[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client connected from 5739[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client connected from 5740[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client connected from 5748[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client connected from 5749[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:44 joe acpid: client connected from 5750[0:0]
Feb  1 19:05:44 joe acpid: 1 client rule loaded
Feb  1 19:05:46 joe acpid: client 5741[0:0] has disconnected
Feb  1 19:05:46 joe acpid: client 5742[0:0] has disconnected
Feb  1 19:05:46 joe acpid: client 5739[0:0] has disconnected
Feb  1 19:05:46 joe acpid: client 5740[0:0] has disconnected
Feb  1 19:05:46 joe acpid: client 5748[0:0] has disconnected
Feb  1 19:05:46 joe acpid: client 5749[0:0] has disconnected
Feb  1 19:05:46 joe acpid: client 5750[0:0] has disconnected
Feb  1 19:05:46 joe acpid: client connected from 5974[0:0]
Feb  1 19:05:46 joe acpid: 1 client rule loaded
Feb  1 19:05:46 joe acpid: client connected from 5980[0:0]
Feb  1 19:05:46 joe acpid: 1 client rule loaded
Feb  1 19:05:46 joe acpid: client connected from 5978[0:0]
Feb  1 19:05:46 joe acpid: 1 client rule loaded
Feb  1 19:05:46 joe acpid: client connected from 5975[0:0]
Feb  1 19:05:46 joe acpid: 1 client rule loaded
Feb  1 19:05:46 joe acpid: client connected from 5976[0:0]
Feb  1 19:05:46 joe acpid: 1 client rule loaded
Feb  1 19:05:46 joe acpid: client connected from 5977[0:0]
Feb  1 19:05:46 joe acpid: 1 client rule loaded
Feb  1 19:05:46 joe acpid: client connected from 5981[0:0]
Feb  1 19:05:46 joe acpid: 1 client rule loaded
Feb  1 19:05:46 joe acpid: client connected from 5979[0:0]
Feb  1 19:05:46 joe acpid: 1 client rule loaded
Feb  1 19:05:46 joe acpid: client connected from 5989[0:0]
Feb  1 19:05:46 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client 5974[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client 5980[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client 5978[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client 5975[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client 5976[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client 5977[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client 5981[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client 5979[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client 5989[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client connected from 6223[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client 6223[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client connected from 6227[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client 6227[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client connected from 6226[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client 6226[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client connected from 6244[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client 6244[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client connected from 6237[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client 6237[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client connected from 6238[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client 6238[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client connected from 6230[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client 6230[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client connected from 6225[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client 6225[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client connected from 6233[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client 6233[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client connected from 6247[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client 6247[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client connected from 6248[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client 6248[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client connected from 6235[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client 6235[0:0] has disconnected
Feb  1 19:05:54 joe acpid: client connected from 6242[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client connected from 6245[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client connected from 6229[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client connected from 6224[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client connected from 6243[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client connected from 6239[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client connected from 6222[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client connected from 6232[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client connected from 6234[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:54 joe acpid: client connected from 6240[0:0]
Feb  1 19:05:54 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client 6242[0:0] has disconnected
Feb  1 19:05:58 joe acpid: client 6245[0:0] has disconnected
Feb  1 19:05:58 joe acpid: client 6229[0:0] has disconnected
Feb  1 19:05:58 joe acpid: client 6224[0:0] has disconnected
Feb  1 19:05:58 joe acpid: client 6243[0:0] has disconnected
Feb  1 19:05:58 joe acpid: client 6239[0:0] has disconnected
Feb  1 19:05:58 joe acpid: client 6222[0:0] has disconnected
Feb  1 19:05:58 joe acpid: client 6232[0:0] has disconnected
Feb  1 19:05:58 joe acpid: client 6234[0:0] has disconnected
Feb  1 19:05:58 joe acpid: client 6240[0:0] has disconnected
Feb  1 19:05:58 joe acpid: client connected from 6724[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6727[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6735[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6739[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6746[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6732[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6729[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6737[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6731[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6728[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6744[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6730[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6742[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6736[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6734[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6748[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6766[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6741[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6740[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6768[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:58 joe acpid: client connected from 6765[0:0]
Feb  1 19:05:58 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client connected from 6767[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client connected from 6745[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client connected from 6764[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client connected from 6763[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client connected from 6769[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client connected from 6779[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client connected from 6782[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client connected from 6781[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client connected from 6784[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client connected from 6780[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client connected from 6783[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client 6724[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6727[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client connected from 6793[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client connected from 6791[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client connected from 6802[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client 6730[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6734[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6745[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client connected from 6792[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client 6731[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client connected from 6804[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client connected from 6794[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client connected from 6803[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client 6736[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client connected from 6800[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client 6737[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client connected from 6795[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client 6735[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6728[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6742[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client connected from 6796[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client 6729[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6744[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client connected from 6801[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client 6739[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client connected from 6798[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client 6748[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6764[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client connected from 6799[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client connected from 6797[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:05:59 joe acpid: client 6746[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6732[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6766[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6741[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6740[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6768[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6765[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6767[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6763[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6769[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6779[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client 6783[0:0] has disconnected
Feb  1 19:05:59 joe acpid: client connected from 6820[0:0]
Feb  1 19:05:59 joe acpid: 1 client rule loaded
Feb  1 19:06:05 joe acpid: client 6782[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6781[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6784[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6780[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6793[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6791[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6802[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6792[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6804[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6794[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6803[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6800[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6795[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6796[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6801[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6798[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6799[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6797[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client 6820[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client connected from 7070[0:0]
Feb  1 19:06:05 joe acpid: 1 client rule loaded
Feb  1 19:06:05 joe acpid: client 7070[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client connected from 7067[0:0]
Feb  1 19:06:05 joe acpid: 1 client rule loaded
Feb  1 19:06:05 joe acpid: client 7067[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client connected from 7071[0:0]
Feb  1 19:06:05 joe acpid: 1 client rule loaded
Feb  1 19:06:05 joe acpid: client 7071[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client connected from 7069[0:0]
Feb  1 19:06:05 joe acpid: 1 client rule loaded
Feb  1 19:06:05 joe acpid: client 7069[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client connected from 7068[0:0]
Feb  1 19:06:05 joe acpid: 1 client rule loaded
Feb  1 19:06:05 joe acpid: client 7068[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client connected from 7083[0:0]
Feb  1 19:06:05 joe acpid: 1 client rule loaded
Feb  1 19:06:05 joe acpid: client 7083[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client connected from 7078[0:0]
Feb  1 19:06:05 joe acpid: 1 client rule loaded
Feb  1 19:06:05 joe acpid: client 7078[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client connected from 7080[0:0]
Feb  1 19:06:05 joe acpid: 1 client rule loaded
Feb  1 19:06:05 joe acpid: client 7080[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client connected from 7081[0:0]
Feb  1 19:06:05 joe acpid: 1 client rule loaded
Feb  1 19:06:05 joe acpid: client 7081[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client connected from 7082[0:0]
Feb  1 19:06:05 joe acpid: 1 client rule loaded
Feb  1 19:06:05 joe acpid: client 7082[0:0] has disconnected
Feb  1 19:06:05 joe acpid: client connected from 7079[0:0]
Feb  1 19:06:05 joe acpid: 1 client rule loaded
Feb  1 19:06:11 joe acpid: client 7079[0:0] has disconnected
Feb  1 19:06:11 joe acpid: client connected from 7322[0:0]
Feb  1 19:06:11 joe acpid: 1 client rule loaded
Feb  1 19:06:11 joe acpid: client connected from 7324[0:0]
Feb  1 19:06:11 joe acpid: 1 client rule loaded
Feb  1 19:06:11 joe acpid: client connected from 7326[0:0]
Feb  1 19:06:11 joe acpid: 1 client rule loaded
Feb  1 19:06:11 joe acpid: client 7322[0:0] has disconnected
Feb  1 19:06:11 joe acpid: client 7324[0:0] has disconnected
Feb  1 19:06:11 joe acpid: client 7326[0:0] has disconnected
Feb  1 19:06:11 joe acpid: client connected from 7323[0:0]
Feb  1 19:06:11 joe acpid: 1 client rule loaded
Feb  1 19:06:11 joe acpid: client 7323[0:0] has disconnected
Feb  1 19:06:11 joe acpid: client connected from 7329[0:0]
Feb  1 19:06:11 joe acpid: 1 client rule loaded
Feb  1 19:06:11 joe acpid: client 7329[0:0] has disconnected
Feb  1 19:06:11 joe acpid: client connected from 7330[0:0]
Feb  1 19:06:11 joe acpid: 1 client rule loaded
Feb  1 19:06:11 joe acpid: client 7330[0:0] has disconnected
Feb  1 19:06:12 joe acpid: client connected from 7565[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7578[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7573[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7585[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7574[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7558[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7559[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7566[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7564[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7575[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7560[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7562[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7563[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7580[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7570[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7561[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7583[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7571[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7577[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7581[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7569[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7567[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:12 joe acpid: client connected from 7582[0:0]
Feb  1 19:06:12 joe acpid: 1 client rule loaded
Feb  1 19:06:15 joe acpid: client connected from 7611[0:0]
Feb  1 19:06:15 joe acpid: 1 client rule loaded
Feb  1 19:06:17 joe acpid: client connected from 7618[0:0]
Feb  1 19:06:17 joe acpid: 1 client rule loaded
Feb  1 19:06:17 joe acpid: client connected from 7622[0:0]
Feb  1 19:06:17 joe acpid: 1 client rule loaded
Feb  1 19:06:17 joe acpid: client connected from 7625[0:0]
Feb  1 19:06:17 joe acpid: 1 client rule loaded
Feb  1 19:06:17 joe acpid: client connected from 7621[0:0]
Feb  1 19:06:17 joe acpid: 1 client rule loaded
Feb  1 19:06:17 joe acpid: client connected from 7626[0:0]
Feb  1 19:06:17 joe acpid: 1 client rule loaded
Feb  1 19:06:17 joe acpid: client 7565[0:0] has disconnected
Feb  1 19:06:17 joe acpid: client 7578[0:0] has disconnected
Feb  1 19:06:17 joe acpid: client 7573[0:0] has disconnected
Feb  1 19:06:17 joe acpid: client 7585[0:0] has disconnected
Feb  1 19:06:17 joe acpid: client 7574[0:0] has disconnected
Feb  1 19:06:17 joe acpid: client 7558[0:0] has disconnected
Feb  1 19:06:17 joe acpid: client 7559[0:0] has disconnected
Feb  1 19:06:17 joe acpid: client 7566[0:0] has disconnected
Feb  1 19:06:17 joe acpid: client 7564[0:0] has disconnected
Feb  1 19:06:18 joe acpid: client 7575[0:0] has disconnected
Feb  1 19:06:18 joe acpid: client 7560[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7562[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7563[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7580[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7570[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7561[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7583[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7571[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7577[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7581[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7569[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7567[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7582[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7611[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7618[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7622[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7625[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7621[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client 7626[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client connected from 7624[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client 7624[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client connected from 7619[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client 7619[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client connected from 7620[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client 7620[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client connected from 7610[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client 7610[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client connected from 7614[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client 7614[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client connected from 7627[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client 7627[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client connected from 7616[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client 7616[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client connected from 7617[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client 7617[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client connected from 7613[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client 7613[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client connected from 7882[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client 7882[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client connected from 7880[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client 7880[0:0] has disconnected
Feb  1 19:06:19 joe acpid: client connected from 7874[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client connected from 7873[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client connected from 7892[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client connected from 7884[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client connected from 7875[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client connected from 7891[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client connected from 7893[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client connected from 7883[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:19 joe acpid: client connected from 7881[0:0]
Feb  1 19:06:19 joe acpid: 1 client rule loaded
Feb  1 19:06:23 joe acpid: client 7874[0:0] has disconnected
Feb  1 19:06:23 joe acpid: client 7873[0:0] has disconnected
Feb  1 19:06:23 joe acpid: client 7892[0:0] has disconnected
Feb  1 19:06:23 joe acpid: client 7884[0:0] has disconnected
Feb  1 19:06:23 joe acpid: client 7875[0:0] has disconnected
Feb  1 19:06:23 joe acpid: client 7891[0:0] has disconnected
Feb  1 19:06:23 joe acpid: client 7893[0:0] has disconnected
Feb  1 19:06:23 joe acpid: client 7883[0:0] has disconnected
Feb  1 19:06:23 joe acpid: client 7881[0:0] has disconnected
Feb  1 19:06:23 joe acpid: client connected from 8121[0:0]
Feb  1 19:06:23 joe acpid: 1 client rule loaded
Feb  1 19:06:23 joe acpid: client connected from 8116[0:0]
Feb  1 19:06:23 joe acpid: 1 client rule loaded
Feb  1 19:06:23 joe acpid: client connected from 8119[0:0]
Feb  1 19:06:23 joe acpid: 1 client rule loaded
Feb  1 19:06:23 joe acpid: client connected from 8120[0:0]
Feb  1 19:06:23 joe acpid: 1 client rule loaded
Feb  1 19:06:23 joe acpid: client connected from 8117[0:0]
Feb  1 19:06:23 joe acpid: 1 client rule loaded
Feb  1 19:06:23 joe acpid: client connected from 8118[0:0]
Feb  1 19:06:23 joe acpid: 1 client rule loaded
Feb  1 19:06:23 joe acpid: client connected from 8130[0:0]
Feb  1 19:06:23 joe acpid: 1 client rule loaded
Feb  1 19:06:29 joe acpid: client 8121[0:0] has disconnected
Feb  1 19:06:29 joe acpid: client 8116[0:0] has disconnected
Feb  1 19:06:29 joe acpid: client 8119[0:0] has disconnected
Feb  1 19:06:29 joe acpid: client 8120[0:0] has disconnected
Feb  1 19:06:29 joe acpid: client 8117[0:0] has disconnected
Feb  1 19:06:29 joe acpid: client 8118[0:0] has disconnected
Feb  1 19:06:29 joe acpid: client 8130[0:0] has disconnected
Feb  1 19:06:29 joe acpid: client connected from 8364[0:0]
Feb  1 19:06:29 joe acpid: 1 client rule loaded
Feb  1 19:06:29 joe acpid: client connected from 8365[0:0]
Feb  1 19:06:29 joe acpid: 1 client rule loaded
Feb  1 19:06:29 joe acpid: client 8364[0:0] has disconnected
Feb  1 19:06:29 joe acpid: client 8365[0:0] has disconnected
Feb  1 19:06:29 joe acpid: client connected from 8362[0:0]
Feb  1 19:06:29 joe acpid: 1 client rule loaded
Feb  1 19:06:29 joe acpid: client 8362[0:0] has disconnected
Feb  1 19:06:29 joe acpid: client connected from 8371[0:0]
Feb  1 19:06:29 joe acpid: 1 client rule loaded
Feb  1 19:06:29 joe acpid: client 8371[0:0] has disconnected
Feb  1 19:06:29 joe acpid: client connected from 8368[0:0]
Feb  1 19:06:29 joe acpid: 1 client rule loaded
Feb  1 19:06:29 joe acpid: client 8368[0:0] has disconnected
Feb  1 19:06:29 joe acpid: client connected from 8369[0:0]
Feb  1 19:06:29 joe acpid: 1 client rule loaded
Feb  1 19:06:29 joe acpid: client 8369[0:0] has disconnected
Feb  1 19:06:29 joe acpid: client connected from 8367[0:0]
Feb  1 19:06:29 joe acpid: 1 client rule loaded
Feb  1 19:06:29 joe acpid: client 8367[0:0] has disconnected
Feb  1 19:06:29 joe acpid: client connected from 8363[0:0]
Feb  1 19:06:29 joe acpid: 1 client rule loaded
Feb  1 19:06:29 joe acpid: client 8363[0:0] has disconnected
Feb  1 19:06:29 joe acpid: client connected from 8373[0:0]
Feb  1 19:06:29 joe acpid: 1 client rule loaded
Feb  1 19:06:35 joe acpid: client 8373[0:0] has disconnected
Feb  1 19:06:35 joe acpid: client connected from 8617[0:0]
Feb  1 19:06:35 joe acpid: 1 client rule loaded
Feb  1 19:06:35 joe acpid: client connected from 8628[0:0]
Feb  1 19:06:35 joe acpid: 1 client rule loaded
Feb  1 19:06:35 joe acpid: client connected from 8625[0:0]
Feb  1 19:06:35 joe acpid: 1 client rule loaded
Feb  1 19:06:35 joe acpid: client connected from 8616[0:0]
Feb  1 19:06:35 joe acpid: 1 client rule loaded
Feb  1 19:06:35 joe acpid: client 8617[0:0] has disconnected
Feb  1 19:06:35 joe acpid: client 8628[0:0] has disconnected
Feb  1 19:06:35 joe acpid: client 8625[0:0] has disconnected
Feb  1 19:06:35 joe acpid: client 8616[0:0] has disconnected
Feb  1 19:06:35 joe acpid: client connected from 8620[0:0]
Feb  1 19:06:35 joe acpid: 1 client rule loaded
Feb  1 19:06:35 joe acpid: client 8620[0:0] has disconnected
Feb  1 19:06:35 joe acpid: client connected from 8630[0:0]
Feb  1 19:06:35 joe acpid: 1 client rule loaded
Feb  1 19:06:35 joe acpid: client 8630[0:0] has disconnected
Feb  1 19:06:35 joe acpid: client connected from 8622[0:0]
Feb  1 19:06:35 joe acpid: 1 client rule loaded
Feb  1 19:06:35 joe acpid: client 8622[0:0] has disconnected
Feb  1 19:06:35 joe acpid: client connected from 8621[0:0]
Feb  1 19:06:35 joe acpid: 1 client rule loaded
Feb  1 19:06:35 joe acpid: client 8621[0:0] has disconnected
Feb  1 19:06:35 joe acpid: client connected from 8618[0:0]
Feb  1 19:06:35 joe acpid: 1 client rule loaded
Feb  1 19:06:35 joe acpid: client 8618[0:0] has disconnected
Feb  1 19:06:35 joe acpid: client connected from 8627[0:0]
Feb  1 19:06:35 joe acpid: 1 client rule loaded
Feb  1 19:06:35 joe acpid: client 8627[0:0] has disconnected
Feb  1 19:06:35 joe acpid: client connected from 8624[0:0]
Feb  1 19:06:35 joe acpid: 1 client rule loaded
Feb  1 19:06:35 joe acpid: client 8624[0:0] has disconnected
Feb  1 19:06:35 joe acpid: client connected from 8626[0:0]
Feb  1 19:06:35 joe acpid: 1 client rule loaded
Feb  1 19:06:40 joe acpid: client 8626[0:0] has disconnected
Feb  1 19:06:40 joe acpid: client connected from 8875[0:0]
Feb  1 19:06:40 joe acpid: 1 client rule loaded
Feb  1 19:06:40 joe acpid: client connected from 8873[0:0]
Feb  1 19:06:40 joe acpid: 1 client rule loaded
Feb  1 19:06:40 joe acpid: client connected from 8879[0:0]
Feb  1 19:06:40 joe acpid: 1 client rule loaded
Feb  1 19:06:40 joe acpid: client 8875[0:0] has disconnected
Feb  1 19:06:40 joe acpid: client 8873[0:0] has disconnected
Feb  1 19:06:40 joe acpid: client 8879[0:0] has disconnected
Feb  1 19:06:40 joe acpid: client connected from 8876[0:0]
Feb  1 19:06:40 joe acpid: 1 client rule loaded
Feb  1 19:06:40 joe acpid: client 8876[0:0] has disconnected
Feb  1 19:06:40 joe acpid: client connected from 8874[0:0]
Feb  1 19:06:40 joe acpid: 1 client rule loaded
Feb  1 19:06:40 joe acpid: client 8874[0:0] has disconnected
Feb  1 19:06:40 joe acpid: client connected from 8884[0:0]
Feb  1 19:06:40 joe acpid: 1 client rule loaded
Feb  1 19:06:40 joe acpid: client 8884[0:0] has disconnected
Feb  1 19:06:40 joe acpid: client connected from 8885[0:0]
Feb  1 19:06:40 joe acpid: 1 client rule loaded
Feb  1 19:06:40 joe acpid: client 8885[0:0] has disconnected
Feb  1 19:06:40 joe acpid: client connected from 8886[0:0]
Feb  1 19:06:40 joe acpid: 1 client rule loaded
Feb  1 19:06:40 joe acpid: client 8886[0:0] has disconnected
Feb  1 19:06:40 joe acpid: client connected from 8878[0:0]
Feb  1 19:06:40 joe acpid: 1 client rule loaded
Feb  1 19:06:40 joe acpid: client 8878[0:0] has disconnected
Feb  1 19:06:40 joe acpid: client connected from 8889[0:0]
Feb  1 19:06:40 joe acpid: 1 client rule loaded
Feb  1 19:06:46 joe acpid: client 8889[0:0] has disconnected
Feb  1 19:06:46 joe acpid: client connected from 9126[0:0]
Feb  1 19:06:46 joe acpid: 1 client rule loaded
Feb  1 19:06:46 joe acpid: client connected from 9127[0:0]
Feb  1 19:06:46 joe acpid: 1 client rule loaded
Feb  1 19:06:46 joe acpid: client connected from 9130[0:0]
Feb  1 19:06:46 joe acpid: 1 client rule loaded
Feb  1 19:06:46 joe acpid: client connected from 9131[0:0]
Feb  1 19:06:46 joe acpid: 1 client rule loaded
Feb  1 19:06:46 joe acpid: client 9126[0:0] has disconnected
Feb  1 19:06:46 joe acpid: client 9127[0:0] has disconnected
Feb  1 19:06:46 joe acpid: client 9130[0:0] has disconnected
Feb  1 19:06:46 joe acpid: client 9131[0:0] has disconnected
Feb  1 19:06:46 joe acpid: client connected from 9129[0:0]
Feb  1 19:06:46 joe acpid: 1 client rule loaded
Feb  1 19:06:46 joe acpid: client 9129[0:0] has disconnected
Feb  1 19:06:46 joe acpid: client connected from 9133[0:0]
Feb  1 19:06:46 joe acpid: 1 client rule loaded
Feb  1 19:06:46 joe acpid: client 9133[0:0] has disconnected
Feb  1 19:06:46 joe acpid: client connected from 9134[0:0]
Feb  1 19:06:46 joe acpid: 1 client rule loaded
Feb  1 19:06:46 joe acpid: client 9134[0:0] has disconnected
Feb  1 19:06:47 joe acpid: client connected from 9135[0:0]
Feb  1 19:06:47 joe acpid: 1 client rule loaded
Feb  1 19:06:47 joe acpid: client 9135[0:0] has disconnected
Feb  1 19:06:47 joe acpid: client connected from 9136[0:0]
Feb  1 19:06:47 joe acpid: 1 client rule loaded
Feb  1 19:06:47 joe acpid: client 9136[0:0] has disconnected
Feb  1 19:06:47 joe acpid: client connected from 9128[0:0]
Feb  1 19:06:47 joe acpid: 1 client rule loaded
Feb  1 19:06:47 joe acpid: client 9128[0:0] has disconnected
Feb  1 19:06:47 joe acpid: client connected from 9137[0:0]
Feb  1 19:06:47 joe acpid: 1 client rule loaded
Feb  1 19:06:47 joe acpid: client 9137[0:0] has disconnected
Feb  1 19:06:47 joe acpid: client connected from 9149[0:0]
Feb  1 19:06:47 joe acpid: 1 client rule loaded
Feb  1 19:06:47 joe acpid: client 9149[0:0] has disconnected
Feb  1 19:06:47 joe acpid: client connected from 9151[0:0]
Feb  1 19:06:47 joe acpid: 1 client rule loaded
Feb  1 19:06:47 joe acpid: client 9151[0:0] has disconnected
Feb  1 19:06:47 joe acpid: client connected from 9140[0:0]
Feb  1 19:06:47 joe acpid: 1 client rule loaded
Feb  1 19:06:47 joe acpid: client 9140[0:0] has disconnected
Feb  1 19:06:47 joe acpid: client connected from 9165[0:0]
Feb  1 19:06:48 joe acpid: 1 client rule loaded
Feb  1 19:06:48 joe acpid: client 9165[0:0] has disconnected
Feb  1 19:06:48 joe acpid: client connected from 9152[0:0]
Feb  1 19:06:48 joe acpid: 1 client rule loaded
Feb  1 19:06:48 joe acpid: client 9152[0:0] has disconnected
Feb  1 19:06:48 joe acpid: client connected from 9150[0:0]
Feb  1 19:06:48 joe acpid: 1 client rule loaded
Feb  1 19:06:49 joe acpid: client 9150[0:0] has disconnected
Feb  1 19:06:49 joe acpid: client connected from 9164[0:0]
Feb  1 19:06:49 joe acpid: 1 client rule loaded
Feb  1 19:06:49 joe acpid: client 9164[0:0] has disconnected
Feb  1 19:06:49 joe acpid: client connected from 9178[0:0]
Feb  1 19:06:49 joe acpid: 1 client rule loaded
Feb  1 19:06:51 joe acpid: client 9178[0:0] has disconnected
Feb  1 19:06:51 joe acpid: client connected from 9179[0:0]
Feb  1 19:06:51 joe acpid: 1 client rule loaded
Feb  1 19:06:51 joe acpid: client 9179[0:0] has disconnected
Feb  1 19:06:51 joe acpid: client connected from 9169[0:0]
Feb  1 19:06:51 joe acpid: 1 client rule loaded
Feb  1 19:06:51 joe acpid: client 9169[0:0] has disconnected
Feb  1 19:06:51 joe acpid: client connected from 9171[0:0]
Feb  1 19:06:51 joe acpid: 1 client rule loaded
Feb  1 19:06:51 joe acpid: client 9171[0:0] has disconnected
Feb  1 19:06:52 joe acpid: client connected from 9172[0:0]
Feb  1 19:06:52 joe acpid: 1 client rule loaded
Feb  1 19:06:52 joe acpid: client 9172[0:0] has disconnected
Feb  1 19:06:52 joe acpid: client connected from 9170[0:0]
Feb  1 19:06:52 joe acpid: 1 client rule loaded
Feb  1 19:06:52 joe acpid: client 9170[0:0] has disconnected
Feb  1 19:06:52 joe acpid: client connected from 9162[0:0]
Feb  1 19:06:52 joe acpid: 1 client rule loaded
Feb  1 19:06:52 joe acpid: client 9162[0:0] has disconnected
Feb  1 19:06:52 joe acpid: client connected from 9159[0:0]
Feb  1 19:06:52 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client 9159[0:0] has disconnected
Feb  1 19:06:53 joe acpid: client connected from 9163[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client 9163[0:0] has disconnected
Feb  1 19:06:53 joe acpid: client connected from 9173[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client 9173[0:0] has disconnected
Feb  1 19:06:53 joe acpid: client connected from 9177[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client 9177[0:0] has disconnected
Feb  1 19:06:53 joe acpid: client connected from 9175[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client 9175[0:0] has disconnected
Feb  1 19:06:53 joe acpid: client connected from 9160[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client 9160[0:0] has disconnected
Feb  1 19:06:53 joe acpid: client connected from 9176[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client 9176[0:0] has disconnected
Feb  1 19:06:53 joe acpid: client connected from 9174[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client 9174[0:0] has disconnected
Feb  1 19:06:53 joe acpid: client connected from 9166[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client 9166[0:0] has disconnected
Feb  1 19:06:53 joe acpid: client connected from 9168[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client 9168[0:0] has disconnected
Feb  1 19:06:53 joe acpid: client connected from 9204[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client 9204[0:0] has disconnected
Feb  1 19:06:53 joe acpid: client connected from 9161[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client 9161[0:0] has disconnected
Feb  1 19:06:53 joe acpid: client connected from 9211[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client 9211[0:0] has disconnected
Feb  1 19:06:53 joe acpid: client connected from 9205[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client 9205[0:0] has disconnected
Feb  1 19:06:53 joe acpid: client connected from 9202[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client 9202[0:0] has disconnected
Feb  1 19:06:53 joe acpid: client connected from 9206[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client 9206[0:0] has disconnected
Feb  1 19:06:53 joe acpid: client connected from 9210[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client connected from 9201[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client connected from 9207[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client connected from 9167[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client connected from 9203[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client connected from 9466[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client connected from 9208[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client connected from 9465[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client connected from 9462[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client connected from 9464[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client connected from 9468[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client connected from 9463[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client connected from 9467[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client connected from 9460[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:53 joe acpid: client connected from 9461[0:0]
Feb  1 19:06:53 joe acpid: 1 client rule loaded
Feb  1 19:06:54 joe acpid: client 9210[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9201[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9207[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9167[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9203[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9466[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9208[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9465[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9462[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9464[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9468[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9463[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9467[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9460[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9461[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client connected from 9710[0:0]
Feb  1 19:06:54 joe acpid: 1 client rule loaded
Feb  1 19:06:54 joe acpid: client connected from 9713[0:0]
Feb  1 19:06:54 joe acpid: 1 client rule loaded
Feb  1 19:06:54 joe acpid: client connected from 9715[0:0]
Feb  1 19:06:54 joe acpid: 1 client rule loaded
Feb  1 19:06:54 joe acpid: client connected from 9712[0:0]
Feb  1 19:06:54 joe acpid: 1 client rule loaded
Feb  1 19:06:54 joe acpid: client connected from 9714[0:0]
Feb  1 19:06:54 joe acpid: 1 client rule loaded
Feb  1 19:06:54 joe acpid: client connected from 9718[0:0]
Feb  1 19:06:54 joe acpid: 1 client rule loaded
Feb  1 19:06:54 joe acpid: client 9710[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9713[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9715[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9712[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client 9714[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client connected from 9723[0:0]
Feb  1 19:06:54 joe acpid: 1 client rule loaded
Feb  1 19:06:54 joe acpid: client 9718[0:0] has disconnected
Feb  1 19:06:54 joe acpid: client connected from 9722[0:0]
Feb  1 19:06:54 joe acpid: 1 client rule loaded
Feb  1 19:07:02 joe acpid: client 9723[0:0] has disconnected
Feb  1 19:07:02 joe acpid: client 9722[0:0] has disconnected
Feb  1 19:07:02 joe acpid: client connected from 9959[0:0]
Feb  1 19:07:02 joe acpid: 1 client rule loaded
Feb  1 19:07:02 joe acpid: client connected from 9977[0:0]
Feb  1 19:07:02 joe acpid: 1 client rule loaded
Feb  1 19:07:02 joe acpid: client connected from 9958[0:0]
Feb  1 19:07:02 joe acpid: 1 client rule loaded
Feb  1 19:07:02 joe acpid: client connected from 9976[0:0]
Feb  1 19:07:02 joe acpid: 1 client rule loaded
Feb  1 19:07:02 joe acpid: client connected from 9965[0:0]
Feb  1 19:07:02 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9959[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client 9977[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client 9958[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client 9976[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client 9965[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9963[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9963[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9962[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9962[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9956[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9956[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9967[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9967[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9972[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9972[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9964[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9964[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9957[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9957[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9970[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9970[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9974[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9974[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9961[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9961[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9978[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9978[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9979[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9979[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 10003[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 10003[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9968[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9968[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9960[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9960[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9980[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9980[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9981[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client 9981[0:0] has disconnected
Feb  1 19:07:03 joe acpid: client connected from 9973[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:03 joe acpid: client connected from 9971[0:0]
Feb  1 19:07:03 joe acpid: 1 client rule loaded
Feb  1 19:07:04 joe acpid: client connected from 10004[0:0]
Feb  1 19:07:04 joe acpid: 1 client rule loaded
Feb  1 19:07:05 joe acpid: client connected from 9982[0:0]
Feb  1 19:07:05 joe acpid: 1 client rule loaded
Feb  1 19:07:05 joe acpid: client connected from 10013[0:0]
Feb  1 19:07:05 joe acpid: 1 client rule loaded
Feb  1 19:07:05 joe acpid: client connected from 10005[0:0]
Feb  1 19:07:05 joe acpid: 1 client rule loaded
Feb  1 19:07:05 joe acpid: client connected from 10002[0:0]
Feb  1 19:07:05 joe acpid: 1 client rule loaded
Feb  1 19:07:05 joe acpid: client connected from 10017[0:0]
Feb  1 19:07:05 joe acpid: 1 client rule loaded
Feb  1 19:07:05 joe acpid: client 9973[0:0] has disconnected
Feb  1 19:07:05 joe acpid: client 9971[0:0] has disconnected
Feb  1 19:07:05 joe acpid: client 10004[0:0] has disconnected
Feb  1 19:07:05 joe acpid: client 9982[0:0] has disconnected
Feb  1 19:07:05 joe acpid: client 10013[0:0] has disconnected
Feb  1 19:07:05 joe acpid: client 10005[0:0] has disconnected
Feb  1 19:07:05 joe acpid: client 10002[0:0] has disconnected
Feb  1 19:07:05 joe acpid: client 10017[0:0] has disconnected
Feb  1 19:07:05 joe acpid: client connected from 10014[0:0]
Feb  1 19:07:05 joe acpid: 1 client rule loaded
Feb  1 19:07:05 joe acpid: client 10014[0:0] has disconnected
Feb  1 19:07:05 joe acpid: client connected from 10019[0:0]
Feb  1 19:07:05 joe acpid: 1 client rule loaded
Feb  1 19:07:05 joe acpid: client 10019[0:0] has disconnected
Feb  1 19:07:05 joe acpid: client connected from 10015[0:0]
Feb  1 19:07:05 joe acpid: 1 client rule loaded
Feb  1 19:07:05 joe acpid: client 10015[0:0] has disconnected
Feb  1 19:07:05 joe acpid: client connected from 10027[0:0]
Feb  1 19:07:05 joe acpid: 1 client rule loaded
Feb  1 19:07:05 joe acpid: client 10027[0:0] has disconnected
Feb  1 19:07:05 joe acpid: client connected from 10020[0:0]
Feb  1 19:07:05 joe acpid: 1 client rule loaded
Feb  1 19:07:05 joe acpid: client 10020[0:0] has disconnected
Feb  1 19:07:05 joe acpid: client connected from 10018[0:0]
Feb  1 19:07:05 joe acpid: 1 client rule loaded
Feb  1 19:07:05 joe acpid: client 10018[0:0] has disconnected
Feb  1 19:07:05 joe acpid: client connected from 10016[0:0]
Feb  1 19:07:05 joe acpid: 1 client rule loaded
Feb  1 19:07:05 joe acpid: client 10016[0:0] has disconnected
Feb  1 19:07:05 joe acpid: client connected from 10025[0:0]
Feb  1 19:07:05 joe acpid: 1 client rule loaded
Feb  1 19:07:05 joe acpid: client 10025[0:0] has disconnected
Feb  1 19:07:05 joe acpid: client connected from 10188[0:0]
Feb  1 19:07:05 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client 10188[0:0] has disconnected
Feb  1 19:07:08 joe acpid: client connected from 10420[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client connected from 10418[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client connected from 10425[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client connected from 10417[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client connected from 10416[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client connected from 10423[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client connected from 10426[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client connected from 10415[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client connected from 10424[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client connected from 10427[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client 10420[0:0] has disconnected
Feb  1 19:07:08 joe acpid: client 10418[0:0] has disconnected
Feb  1 19:07:08 joe acpid: client 10425[0:0] has disconnected
Feb  1 19:07:08 joe acpid: client 10417[0:0] has disconnected
Feb  1 19:07:08 joe acpid: client 10416[0:0] has disconnected
Feb  1 19:07:08 joe acpid: client 10423[0:0] has disconnected
Feb  1 19:07:08 joe acpid: client 10426[0:0] has disconnected
Feb  1 19:07:08 joe acpid: client 10415[0:0] has disconnected
Feb  1 19:07:08 joe acpid: client 10424[0:0] has disconnected
Feb  1 19:07:08 joe acpid: client 10427[0:0] has disconnected
Feb  1 19:07:08 joe acpid: client connected from 10440[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client connected from 10437[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client connected from 10436[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client connected from 10439[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client connected from 10442[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client connected from 10441[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:08 joe acpid: client connected from 10438[0:0]
Feb  1 19:07:08 joe acpid: 1 client rule loaded
Feb  1 19:07:19 joe acpid: client 10440[0:0] has disconnected
Feb  1 19:07:19 joe acpid: client 10437[0:0] has disconnected
Feb  1 19:07:19 joe acpid: client 10436[0:0] has disconnected
Feb  1 19:07:19 joe acpid: client 10439[0:0] has disconnected
Feb  1 19:07:19 joe acpid: client 10442[0:0] has disconnected
Feb  1 19:07:19 joe acpid: client 10441[0:0] has disconnected
Feb  1 19:07:19 joe acpid: client 10438[0:0] has disconnected
Feb  1 19:07:19 joe acpid: client connected from 10707[0:0]
Feb  1 19:07:19 joe acpid: 1 client rule loaded
Feb  1 19:07:19 joe acpid: client 10707[0:0] has disconnected
Feb  1 19:07:19 joe acpid: client connected from 10714[0:0]
Feb  1 19:07:19 joe acpid: 1 client rule loaded
Feb  1 19:07:19 joe acpid: client 10714[0:0] has disconnected
Feb  1 19:07:19 joe acpid: client connected from 10711[0:0]
Feb  1 19:07:19 joe acpid: 1 client rule loaded
Feb  1 19:07:19 joe acpid: client 10711[0:0] has disconnected
Feb  1 19:07:19 joe acpid: client connected from 10709[0:0]
Feb  1 19:07:19 joe acpid: 1 client rule loaded
Feb  1 19:07:19 joe acpid: client 10709[0:0] has disconnected
Feb  1 19:07:19 joe acpid: client connected from 10713[0:0]
Feb  1 19:07:19 joe acpid: 1 client rule loaded
Feb  1 19:07:19 joe acpid: client 10713[0:0] has disconnected
Feb  1 19:07:19 joe acpid: client connected from 10715[0:0]
Feb  1 19:07:19 joe acpid: 1 client rule loaded
Feb  1 19:07:19 joe acpid: client 10715[0:0] has disconnected
Feb  1 19:07:19 joe acpid: client connected from 10716[0:0]
Feb  1 19:07:19 joe acpid: 1 client rule loaded
Feb  1 19:07:19 joe acpid: client 10716[0:0] has disconnected
Feb  1 19:07:19 joe acpid: client connected from 10712[0:0]
Feb  1 19:07:19 joe acpid: 1 client rule loaded
Feb  1 19:07:19 joe acpid: client 10712[0:0] has disconnected
Feb  1 19:07:19 joe acpid: client connected from 10708[0:0]
Feb  1 19:07:19 joe acpid: 1 client rule loaded
Feb  1 19:07:24 joe acpid: client 10708[0:0] has disconnected
Feb  1 19:07:24 joe acpid: client connected from 10973[0:0]
Feb  1 19:07:24 joe acpid: 1 client rule loaded
Feb  1 19:07:24 joe acpid: client connected from 10970[0:0]
Feb  1 19:07:24 joe acpid: 1 client rule loaded
Feb  1 19:07:24 joe acpid: client connected from 10967[0:0]
Feb  1 19:07:24 joe acpid: 1 client rule loaded
Feb  1 19:07:24 joe acpid: client connected from 10976[0:0]
Feb  1 19:07:24 joe acpid: 1 client rule loaded
Feb  1 19:07:24 joe acpid: client 10970[0:0] has disconnected
Feb  1 19:07:24 joe acpid: client 10967[0:0] has disconnected
Feb  1 19:07:24 joe acpid: client 10976[0:0] has disconnected
Feb  1 19:07:24 joe acpid: client connected from 10968[0:0]
Feb  1 19:07:24 joe acpid: 1 client rule loaded
Feb  1 19:07:24 joe acpid: client 10973[0:0] has disconnected
Feb  1 19:07:24 joe acpid: client 10968[0:0] has disconnected
Feb  1 19:07:24 joe acpid: client connected from 10972[0:0]
Feb  1 19:07:24 joe acpid: 1 client rule loaded
Feb  1 19:07:24 joe acpid: client 10972[0:0] has disconnected
Feb  1 19:07:24 joe acpid: client connected from 10974[0:0]
Feb  1 19:07:24 joe acpid: 1 client rule loaded
Feb  1 19:07:24 joe acpid: client 10974[0:0] has disconnected
Feb  1 19:07:24 joe acpid: client connected from 10982[0:0]
Feb  1 19:07:24 joe acpid: 1 client rule loaded
Feb  1 19:07:24 joe acpid: client 10982[0:0] has disconnected
Feb  1 19:07:24 joe acpid: client connected from 10984[0:0]
Feb  1 19:07:24 joe acpid: 1 client rule loaded
Feb  1 19:07:24 joe acpid: client 10984[0:0] has disconnected
Feb  1 19:07:24 joe acpid: client connected from 10983[0:0]
Feb  1 19:07:24 joe acpid: 1 client rule loaded
Feb  1 19:07:24 joe acpid: client 10983[0:0] has disconnected
Feb  1 19:07:24 joe acpid: client connected from 10985[0:0]
Feb  1 19:07:24 joe acpid: 1 client rule loaded
Feb  1 19:07:24 joe acpid: client 10985[0:0] has disconnected
Feb  1 19:07:24 joe acpid: client connected from 10990[0:0]
Feb  1 19:07:24 joe acpid: 1 client rule loaded
Feb  1 19:07:29 joe acpid: client 10990[0:0] has disconnected
Feb  1 19:07:29 joe acpid: client connected from 11243[0:0]
Feb  1 19:07:29 joe acpid: 1 client rule loaded
Feb  1 19:07:29 joe acpid: client connected from 11245[0:0]
Feb  1 19:07:29 joe acpid: 1 client rule loaded
Feb  1 19:07:29 joe acpid: client connected from 11242[0:0]
Feb  1 19:07:29 joe acpid: 1 client rule loaded
Feb  1 19:07:29 joe acpid: client connected from 11244[0:0]
Feb  1 19:07:29 joe acpid: 1 client rule loaded
Feb  1 19:07:29 joe acpid: client 11242[0:0] has disconnected
Feb  1 19:07:29 joe acpid: client 11244[0:0] has disconnected
Feb  1 19:07:29 joe acpid: client connected from 11241[0:0]
Feb  1 19:07:29 joe acpid: 1 client rule loaded
Feb  1 19:07:29 joe acpid: client 11243[0:0] has disconnected
Feb  1 19:07:29 joe acpid: client 11245[0:0] has disconnected
Feb  1 19:07:29 joe acpid: client 11241[0:0] has disconnected
Feb  1 19:07:29 joe acpid: client connected from 11246[0:0]
Feb  1 19:07:29 joe acpid: 1 client rule loaded
Feb  1 19:07:29 joe acpid: client 11246[0:0] has disconnected
Feb  1 19:07:29 joe acpid: client connected from 11239[0:0]
Feb  1 19:07:29 joe acpid: 1 client rule loaded
Feb  1 19:07:29 joe acpid: client 11239[0:0] has disconnected
Feb  1 19:07:29 joe acpid: client connected from 11240[0:0]
Feb  1 19:07:29 joe acpid: 1 client rule loaded
Feb  1 19:07:29 joe acpid: client 11240[0:0] has disconnected
Feb  1 19:07:29 joe acpid: client connected from 11238[0:0]
Feb  1 19:07:29 joe acpid: 1 client rule loaded
Feb  1 19:07:29 joe acpid: client 11238[0:0] has disconnected
Feb  1 19:07:29 joe acpid: client connected from 11237[0:0]
Feb  1 19:07:29 joe acpid: 1 client rule loaded
Feb  1 19:07:35 joe acpid: client 11237[0:0] has disconnected
Feb  1 19:07:35 joe acpid: client connected from 11476[0:0]
Feb  1 19:07:35 joe acpid: 1 client rule loaded
Feb  1 19:07:35 joe acpid: client connected from 11481[0:0]
Feb  1 19:07:35 joe acpid: 1 client rule loaded
Feb  1 19:07:35 joe acpid: client connected from 11486[0:0]
Feb  1 19:07:35 joe acpid: 1 client rule loaded
Feb  1 19:07:35 joe acpid: client connected from 11483[0:0]
Feb  1 19:07:35 joe acpid: 1 client rule loaded
Feb  1 19:07:35 joe acpid: client 11476[0:0] has disconnected
Feb  1 19:07:35 joe acpid: client 11481[0:0] has disconnected
Feb  1 19:07:35 joe acpid: client 11486[0:0] has disconnected
Feb  1 19:07:35 joe acpid: client 11483[0:0] has disconnected
Feb  1 19:07:35 joe acpid: client connected from 11480[0:0]
Feb  1 19:07:35 joe acpid: 1 client rule loaded
Feb  1 19:07:35 joe acpid: client 11480[0:0] has disconnected
Feb  1 19:07:35 joe acpid: client connected from 11479[0:0]
Feb  1 19:07:35 joe acpid: 1 client rule loaded
Feb  1 19:07:35 joe acpid: client 11479[0:0] has disconnected
Feb  1 19:07:35 joe acpid: client connected from 11488[0:0]
Feb  1 19:07:35 joe acpid: 1 client rule loaded
Feb  1 19:07:35 joe acpid: client 11488[0:0] has disconnected
Feb  1 19:07:35 joe acpid: client connected from 11482[0:0]
Feb  1 19:07:35 joe acpid: 1 client rule loaded
Feb  1 19:07:35 joe acpid: client 11482[0:0] has disconnected
Feb  1 19:07:35 joe acpid: client connected from 11485[0:0]
Feb  1 19:07:35 joe acpid: 1 client rule loaded
Feb  1 19:07:35 joe acpid: client 11485[0:0] has disconnected
Feb  1 19:07:35 joe acpid: client connected from 11487[0:0]
Feb  1 19:07:35 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client 11487[0:0] has disconnected
Feb  1 19:07:41 joe acpid: client connected from 11731[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11730[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11729[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client 11731[0:0] has disconnected
Feb  1 19:07:41 joe acpid: client 11730[0:0] has disconnected
Feb  1 19:07:41 joe acpid: client 11729[0:0] has disconnected
Feb  1 19:07:41 joe acpid: client connected from 11738[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client 11738[0:0] has disconnected
Feb  1 19:07:41 joe acpid: client connected from 11737[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client 11737[0:0] has disconnected
Feb  1 19:07:41 joe acpid: client connected from 11735[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client 11735[0:0] has disconnected
Feb  1 19:07:41 joe acpid: client connected from 11736[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client 11736[0:0] has disconnected
Feb  1 19:07:41 joe acpid: client connected from 11742[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client 11742[0:0] has disconnected
Feb  1 19:07:41 joe acpid: client connected from 11739[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client 11739[0:0] has disconnected
Feb  1 19:07:41 joe acpid: client connected from 11732[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client 11732[0:0] has disconnected
Feb  1 19:07:41 joe acpid: client connected from 11740[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client 11740[0:0] has disconnected
Feb  1 19:07:41 joe acpid: client connected from 11733[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client 11733[0:0] has disconnected
Feb  1 19:07:41 joe acpid: client connected from 11761[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client 11761[0:0] has disconnected
Feb  1 19:07:41 joe acpid: client connected from 11766[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client 11766[0:0] has disconnected
Feb  1 19:07:41 joe acpid: client connected from 11772[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client 11772[0:0] has disconnected
Feb  1 19:07:41 joe acpid: client connected from 11765[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11773[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11762[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11763[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11769[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11778[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11770[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11780[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11775[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11800[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11774[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11782[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11798[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11796[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11797[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11783[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11781[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11776[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11799[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11802[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:41 joe acpid: client connected from 11767[0:0]
Feb  1 19:07:41 joe acpid: 1 client rule loaded
Feb  1 19:07:48 joe acpid: client 11765[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11773[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11762[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11763[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11769[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11778[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11770[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11780[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11775[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11800[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11774[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11782[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11798[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11796[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11797[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11783[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11781[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11776[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11799[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11802[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client 11767[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client connected from 12083[0:0]
Feb  1 19:07:48 joe acpid: 1 client rule loaded
Feb  1 19:07:48 joe acpid: client 12083[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client connected from 12078[0:0]
Feb  1 19:07:48 joe acpid: 1 client rule loaded
Feb  1 19:07:48 joe acpid: client 12078[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client connected from 12084[0:0]
Feb  1 19:07:48 joe acpid: 1 client rule loaded
Feb  1 19:07:48 joe acpid: client 12084[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client connected from 12081[0:0]
Feb  1 19:07:48 joe acpid: 1 client rule loaded
Feb  1 19:07:48 joe acpid: client 12081[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client connected from 12080[0:0]
Feb  1 19:07:48 joe acpid: 1 client rule loaded
Feb  1 19:07:48 joe acpid: client 12080[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client connected from 12079[0:0]
Feb  1 19:07:48 joe acpid: 1 client rule loaded
Feb  1 19:07:48 joe acpid: client 12079[0:0] has disconnected
Feb  1 19:07:48 joe acpid: client connected from 12082[0:0]
Feb  1 19:07:48 joe acpid: 1 client rule loaded
Feb  1 19:07:48 joe acpid: client 12082[0:0] has disconnected
Feb  1 19:07:49 joe acpid: client connected from 12077[0:0]
Feb  1 19:07:49 joe acpid: 1 client rule loaded
Feb  1 19:07:49 joe acpid: client 12077[0:0] has disconnected
Feb  1 19:07:49 joe acpid: client connected from 12075[0:0]
Feb  1 19:07:49 joe acpid: 1 client rule loaded
Feb  1 19:07:49 joe acpid: client 12075[0:0] has disconnected
Feb  1 19:07:49 joe acpid: client connected from 12085[0:0]
Feb  1 19:07:49 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client 12085[0:0] has disconnected
Feb  1 19:07:51 joe acpid: client connected from 12312[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12313[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12317[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12314[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12316[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12315[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12318[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12319[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client 12312[0:0] has disconnected
Feb  1 19:07:51 joe acpid: client 12313[0:0] has disconnected
Feb  1 19:07:51 joe acpid: client 12317[0:0] has disconnected
Feb  1 19:07:51 joe acpid: client 12314[0:0] has disconnected
Feb  1 19:07:51 joe acpid: client 12316[0:0] has disconnected
Feb  1 19:07:51 joe acpid: client 12315[0:0] has disconnected
Feb  1 19:07:51 joe acpid: client 12318[0:0] has disconnected
Feb  1 19:07:51 joe acpid: client 12319[0:0] has disconnected
Feb  1 19:07:51 joe acpid: client connected from 12332[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12333[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12338[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12339[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12340[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12342[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12343[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12347[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12336[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12348[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12334[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12358[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12335[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12346[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12344[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12361[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:07:51 joe acpid: client connected from 12362[0:0]
Feb  1 19:07:51 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client 12332[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client 12333[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client 12338[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client 12339[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client 12340[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client 12342[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client 12343[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client 12347[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client 12336[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client 12348[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client 12334[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client 12358[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client 12335[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client 12346[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client 12344[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client 12361[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client 12362[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client connected from 12596[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client 12596[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client connected from 12599[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client 12599[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client connected from 12609[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client 12609[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client connected from 12605[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client 12605[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client connected from 12612[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client 12612[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client connected from 12606[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client 12606[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client connected from 12604[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client 12604[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client connected from 12611[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client 12611[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client connected from 12603[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client 12603[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client connected from 12607[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client 12607[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client connected from 12613[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client 12613[0:0] has disconnected
Feb  1 19:08:00 joe acpid: client connected from 12621[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client connected from 12610[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client connected from 12608[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client connected from 12622[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client connected from 12616[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client connected from 12614[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client connected from 12618[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client connected from 12602[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client connected from 12623[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client connected from 12619[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:00 joe acpid: client connected from 12615[0:0]
Feb  1 19:08:00 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client 12621[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client 12610[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client 12608[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client 12622[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client 12616[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client 12614[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client 12618[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client 12602[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client 12623[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client 12619[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client 12615[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client connected from 12882[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client 12882[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client connected from 12883[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client 12883[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client connected from 12881[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client 12881[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client connected from 12891[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client 12891[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client connected from 12893[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client 12893[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client connected from 12894[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client 12894[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client connected from 12890[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client 12890[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client connected from 12888[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client 12888[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client connected from 12895[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client 12895[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client connected from 12897[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client 12897[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client connected from 12901[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client 12901[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client connected from 12902[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client 12902[0:0] has disconnected
Feb  1 19:08:06 joe acpid: client connected from 12899[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client connected from 12896[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client connected from 12892[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client connected from 12889[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:06 joe acpid: client connected from 12898[0:0]
Feb  1 19:08:06 joe acpid: 1 client rule loaded
Feb  1 19:08:10 joe acpid: client 12899[0:0] has disconnected
Feb  1 19:08:10 joe acpid: client 12896[0:0] has disconnected
Feb  1 19:08:10 joe acpid: client 12892[0:0] has disconnected
Feb  1 19:08:10 joe acpid: client 12889[0:0] has disconnected
Feb  1 19:08:10 joe acpid: client 12898[0:0] has disconnected
Feb  1 19:08:10 joe acpid: client connected from 13159[0:0]
Feb  1 19:08:10 joe acpid: 1 client rule loaded
Feb  1 19:08:10 joe acpid: client connected from 13150[0:0]
Feb  1 19:08:10 joe acpid: 1 client rule loaded
Feb  1 19:08:10 joe acpid: client 13159[0:0] has disconnected
Feb  1 19:08:10 joe acpid: client 13150[0:0] has disconnected
Feb  1 19:08:10 joe acpid: client connected from 13158[0:0]
Feb  1 19:08:10 joe acpid: 1 client rule loaded
Feb  1 19:08:10 joe acpid: client 13158[0:0] has disconnected
Feb  1 19:08:10 joe acpid: client connected from 13154[0:0]
Feb  1 19:08:10 joe acpid: 1 client rule loaded
Feb  1 19:08:10 joe acpid: client 13154[0:0] has disconnected
Feb  1 19:08:10 joe acpid: client connected from 13151[0:0]
Feb  1 19:08:10 joe acpid: 1 client rule loaded
Feb  1 19:08:10 joe acpid: client 13151[0:0] has disconnected
Feb  1 19:08:10 joe acpid: client connected from 13157[0:0]
Feb  1 19:08:10 joe acpid: 1 client rule loaded
Feb  1 19:08:10 joe acpid: client 13157[0:0] has disconnected
Feb  1 19:08:10 joe acpid: client connected from 13160[0:0]
Feb  1 19:08:10 joe acpid: 1 client rule loaded
Feb  1 19:08:10 joe acpid: client 13160[0:0] has disconnected
Feb  1 19:08:10 joe acpid: client connected from 13152[0:0]
Feb  1 19:08:10 joe acpid: 1 client rule loaded
Feb  1 19:08:10 joe acpid: client 13152[0:0] has disconnected
Feb  1 19:08:10 joe acpid: client connected from 13156[0:0]
Feb  1 19:08:10 joe acpid: 1 client rule loaded
Feb  1 19:08:19 joe acpid: client 13156[0:0] has disconnected
Feb  1 19:08:19 joe acpid: client connected from 13433[0:0]
Feb  1 19:08:19 joe acpid: 1 client rule loaded
Feb  1 19:08:19 joe acpid: client connected from 13432[0:0]
Feb  1 19:08:19 joe acpid: 1 client rule loaded
Feb  1 19:08:19 joe acpid: client connected from 13437[0:0]
Feb  1 19:08:19 joe acpid: 1 client rule loaded
Feb  1 19:08:19 joe acpid: client connected from 13439[0:0]
Feb  1 19:08:19 joe acpid: 1 client rule loaded
Feb  1 19:08:19 joe acpid: client connected from 13445[0:0]
Feb  1 19:08:19 joe acpid: 1 client rule loaded
Feb  1 19:08:19 joe acpid: client 13433[0:0] has disconnected
Feb  1 19:08:20 joe acpid: client 13432[0:0] has disconnected
Feb  1 19:08:20 joe acpid: client 13437[0:0] has disconnected
Feb  1 19:08:20 joe acpid: client 13439[0:0] has disconnected
Feb  1 19:08:20 joe acpid: client 13445[0:0] has disconnected
Feb  1 19:08:20 joe acpid: client connected from 13435[0:0]
Feb  1 19:08:20 joe acpid: 1 client rule loaded
Feb  1 19:08:20 joe acpid: client 13435[0:0] has disconnected
Feb  1 19:08:20 joe acpid: client connected from 13441[0:0]
Feb  1 19:08:20 joe acpid: 1 client rule loaded
Feb  1 19:08:20 joe acpid: client 13441[0:0] has disconnected
Feb  1 19:08:21 joe acpid: client connected from 13438[0:0]
Feb  1 19:08:21 joe acpid: 1 client rule loaded
Feb  1 19:08:21 joe acpid: client 13438[0:0] has disconnected
Feb  1 19:08:21 joe acpid: client connected from 13444[0:0]
Feb  1 19:08:21 joe acpid: 1 client rule loaded
Feb  1 19:08:21 joe acpid: client 13444[0:0] has disconnected
Feb  1 19:08:21 joe acpid: client connected from 13436[0:0]
Feb  1 19:08:21 joe acpid: 1 client rule loaded
Feb  1 19:08:21 joe acpid: client 13436[0:0] has disconnected
Feb  1 19:08:21 joe acpid: client connected from 13446[0:0]
Feb  1 19:08:21 joe acpid: 1 client rule loaded
Feb  1 19:08:21 joe acpid: client 13446[0:0] has disconnected
Feb  1 19:08:21 joe acpid: client connected from 13434[0:0]
Feb  1 19:08:21 joe acpid: 1 client rule loaded
Feb  1 19:08:23 joe acpid: client 13434[0:0] has disconnected
Feb  1 19:08:23 joe acpid: client connected from 13679[0:0]
Feb  1 19:08:23 joe acpid: 1 client rule loaded
Feb  1 19:08:23 joe acpid: client connected from 13680[0:0]
Feb  1 19:08:23 joe acpid: 1 client rule loaded
Feb  1 19:08:23 joe acpid: client connected from 13681[0:0]
Feb  1 19:08:23 joe acpid: 1 client rule loaded
Feb  1 19:08:23 joe acpid: client connected from 13685[0:0]
Feb  1 19:08:23 joe acpid: 1 client rule loaded
Feb  1 19:08:23 joe acpid: client connected from 13688[0:0]
Feb  1 19:08:23 joe acpid: 1 client rule loaded
Feb  1 19:08:23 joe acpid: client connected from 13689[0:0]
Feb  1 19:08:23 joe acpid: 1 client rule loaded
Feb  1 19:08:23 joe acpid: client connected from 13686[0:0]
Feb  1 19:08:23 joe acpid: 1 client rule loaded
Feb  1 19:08:23 joe acpid: client connected from 13691[0:0]
Feb  1 19:08:23 joe acpid: 1 client rule loaded
Feb  1 19:08:23 joe acpid: client connected from 13687[0:0]
Feb  1 19:08:23 joe acpid: 1 client rule loaded
Feb  1 19:08:23 joe acpid: client connected from 13690[0:0]
Feb  1 19:08:23 joe acpid: 1 client rule loaded
Feb  1 19:08:30 joe acpid: client 13679[0:0] has disconnected
Feb  1 19:08:30 joe acpid: client 13680[0:0] has disconnected
Feb  1 19:08:30 joe acpid: client 13681[0:0] has disconnected
Feb  1 19:08:30 joe acpid: client 13685[0:0] has disconnected
Feb  1 19:08:30 joe acpid: client 13688[0:0] has disconnected
Feb  1 19:08:30 joe acpid: client 13689[0:0] has disconnected
Feb  1 19:08:30 joe acpid: client 13686[0:0] has disconnected
Feb  1 19:08:30 joe acpid: client 13691[0:0] has disconnected
Feb  1 19:08:30 joe acpid: client 13687[0:0] has disconnected
Feb  1 19:08:30 joe acpid: client 13690[0:0] has disconnected
Feb  1 19:08:30 joe acpid: client connected from 13948[0:0]
Feb  1 19:08:30 joe acpid: 1 client rule loaded
Feb  1 19:08:30 joe acpid: client connected from 13950[0:0]
Feb  1 19:08:30 joe acpid: 1 client rule loaded
Feb  1 19:08:30 joe acpid: client connected from 13952[0:0]
Feb  1 19:08:30 joe acpid: 1 client rule loaded
Feb  1 19:08:30 joe acpid: client connected from 13944[0:0]
Feb  1 19:08:30 joe acpid: 1 client rule loaded
Feb  1 19:08:30 joe acpid: client connected from 13945[0:0]
Feb  1 19:08:30 joe acpid: 1 client rule loaded
Feb  1 19:08:30 joe acpid: client connected from 13946[0:0]
Feb  1 19:08:30 joe acpid: 1 client rule loaded
Feb  1 19:08:30 joe acpid: client connected from 13949[0:0]
Feb  1 19:08:30 joe acpid: 1 client rule loaded
Feb  1 19:08:30 joe acpid: client connected from 13943[0:0]
Feb  1 19:08:30 joe acpid: 1 client rule loaded
Feb  1 19:08:30 joe acpid: client connected from 13947[0:0]
Feb  1 19:08:30 joe acpid: 1 client rule loaded
Feb  1 19:08:30 joe acpid: client connected from 13951[0:0]
Feb  1 19:08:30 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client 13948[0:0] has disconnected
Feb  1 19:08:36 joe acpid: client 13950[0:0] has disconnected
Feb  1 19:08:36 joe acpid: client 13952[0:0] has disconnected
Feb  1 19:08:36 joe acpid: client 13944[0:0] has disconnected
Feb  1 19:08:36 joe acpid: client 13945[0:0] has disconnected
Feb  1 19:08:36 joe acpid: client 13946[0:0] has disconnected
Feb  1 19:08:36 joe acpid: client 13949[0:0] has disconnected
Feb  1 19:08:36 joe acpid: client 13943[0:0] has disconnected
Feb  1 19:08:36 joe acpid: client 13947[0:0] has disconnected
Feb  1 19:08:36 joe acpid: client 13951[0:0] has disconnected
Feb  1 19:08:36 joe acpid: client connected from 14206[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14201[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14203[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14202[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14200[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14215[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14212[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14214[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14229[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14216[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14219[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14211[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14217[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14210[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14234[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14225[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14213[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14224[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14221[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14222[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14218[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14230[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14232[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14220[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14226[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14227[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14253[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client 14203[0:0] has disconnected
Feb  1 19:08:36 joe acpid: client connected from 14252[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14265[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14259[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client 14201[0:0] has disconnected
Feb  1 19:08:36 joe acpid: client connected from 14264[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14260[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14262[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14258[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client 14206[0:0] has disconnected
Feb  1 19:08:36 joe acpid: client connected from 14263[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:36 joe acpid: client connected from 14261[0:0]
Feb  1 19:08:36 joe acpid: 1 client rule loaded
Feb  1 19:08:42 joe acpid: client 14202[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14200[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14215[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14212[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14214[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14229[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14216[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14219[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14211[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14217[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14210[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14234[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14225[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14213[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14224[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14221[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14222[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14218[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14230[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14232[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14220[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14226[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14227[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14253[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14252[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14265[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14259[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14264[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14260[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14262[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14258[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14263[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client 14261[0:0] has disconnected
Feb  1 19:08:42 joe acpid: client connected from 14530[0:0]
Feb  1 19:08:42 joe acpid: 1 client rule loaded
Feb  1 19:08:42 joe acpid: client connected from 14527[0:0]
Feb  1 19:08:42 joe acpid: 1 client rule loaded
Feb  1 19:08:42 joe acpid: client connected from 14524[0:0]
Feb  1 19:08:42 joe acpid: 1 client rule loaded
Feb  1 19:08:42 joe acpid: client connected from 14522[0:0]
Feb  1 19:08:42 joe acpid: 1 client rule loaded
Feb  1 19:08:42 joe acpid: client connected from 14526[0:0]
Feb  1 19:08:42 joe acpid: 1 client rule loaded
Feb  1 19:08:42 joe acpid: client connected from 14529[0:0]
Feb  1 19:08:42 joe acpid: 1 client rule loaded
Feb  1 19:08:42 joe acpid: client connected from 14531[0:0]
Feb  1 19:08:42 joe acpid: 1 client rule loaded
Feb  1 19:08:42 joe acpid: client connected from 14528[0:0]
Feb  1 19:08:42 joe acpid: 1 client rule loaded
Feb  1 19:08:42 joe acpid: client connected from 14523[0:0]
Feb  1 19:08:42 joe acpid: 1 client rule loaded
Feb  1 19:08:42 joe acpid: client connected from 14532[0:0]
Feb  1 19:08:42 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client 14530[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client 14527[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client 14524[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client 14522[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client 14526[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client 14529[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client 14531[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client 14528[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client 14523[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client 14532[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client connected from 14781[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14784[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14783[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14788[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14798[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14787[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14794[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14793[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14797[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14791[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14790[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14795[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client 14781[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client connected from 14789[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client 14783[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client connected from 14807[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14809[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14810[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14811[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client 14784[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client connected from 14808[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14812[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14814[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14819[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14816[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14820[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client connected from 14818[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:48 joe acpid: client 14788[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client 14787[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client 14794[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client 14791[0:0] has disconnected
Feb  1 19:08:48 joe acpid: client connected from 14813[0:0]
Feb  1 19:08:48 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client 14798[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14793[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14797[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14790[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14795[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14789[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14807[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14809[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14810[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14811[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14808[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14812[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14814[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14819[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14816[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14820[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14818[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client 14813[0:0] has disconnected
Feb  1 19:08:55 joe acpid: client connected from 15083[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15084[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15090[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15087[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15085[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15100[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15108[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15095[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15093[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15106[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15109[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15104[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15096[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15099[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15105[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15103[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15097[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15091[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15098[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15086[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15088[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:08:55 joe acpid: client connected from 15101[0:0]
Feb  1 19:08:55 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe /USR/SBIN/CRON[15372]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \; -delete)
Feb  1 19:09:01 joe acpid: client 15083[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15084[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15090[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15087[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15085[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15100[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15108[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15095[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15093[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15106[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15109[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15104[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15096[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15099[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15105[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15103[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15097[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15091[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15098[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15086[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15088[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client 15101[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client connected from 15376[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe acpid: client 15376[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client connected from 15378[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe acpid: client 15378[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client connected from 15379[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe acpid: client 15379[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client connected from 15380[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe acpid: client 15380[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client connected from 15377[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe acpid: client 15377[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client connected from 15383[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe acpid: client 15383[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client connected from 15384[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe acpid: client 15384[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client connected from 15392[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe acpid: client 15392[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client connected from 15397[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe acpid: client 15397[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client connected from 15400[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe acpid: client 15400[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client connected from 15401[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe acpid: client 15401[0:0] has disconnected
Feb  1 19:09:01 joe acpid: client connected from 15395[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe acpid: client connected from 15394[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe acpid: client connected from 15393[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe acpid: client connected from 15391[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe acpid: client connected from 15396[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:01 joe acpid: client connected from 15398[0:0]
Feb  1 19:09:01 joe acpid: 1 client rule loaded
Feb  1 19:09:07 joe acpid: client 15395[0:0] has disconnected
Feb  1 19:09:07 joe acpid: client 15394[0:0] has disconnected
Feb  1 19:09:07 joe acpid: client 15393[0:0] has disconnected
Feb  1 19:09:07 joe acpid: client 15391[0:0] has disconnected
Feb  1 19:09:07 joe acpid: client 15396[0:0] has disconnected
Feb  1 19:09:07 joe acpid: client 15398[0:0] has disconnected
Feb  1 19:09:07 joe acpid: client connected from 15659[0:0]
Feb  1 19:09:07 joe acpid: 1 client rule loaded
Feb  1 19:09:07 joe acpid: client connected from 15665[0:0]
Feb  1 19:09:07 joe acpid: 1 client rule loaded
Feb  1 19:09:07 joe acpid: client connected from 15661[0:0]
Feb  1 19:09:07 joe acpid: 1 client rule loaded
Feb  1 19:09:07 joe acpid: client connected from 15657[0:0]
Feb  1 19:09:07 joe acpid: 1 client rule loaded
Feb  1 19:09:07 joe acpid: client connected from 15664[0:0]
Feb  1 19:09:07 joe acpid: 1 client rule loaded
Feb  1 19:09:07 joe acpid: client connected from 15660[0:0]
Feb  1 19:09:07 joe acpid: 1 client rule loaded
Feb  1 19:09:07 joe acpid: client connected from 15662[0:0]
Feb  1 19:09:07 joe acpid: 1 client rule loaded
Feb  1 19:09:07 joe acpid: client connected from 15667[0:0]
Feb  1 19:09:07 joe acpid: 1 client rule loaded
Feb  1 19:09:07 joe acpid: client connected from 15658[0:0]
Feb  1 19:09:07 joe acpid: 1 client rule loaded
Feb  1 19:09:16 joe acpid: client 15659[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client 15665[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client 15661[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client 15657[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client 15664[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client 15660[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client 15662[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client 15667[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client 15658[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client connected from 15926[0:0]
Feb  1 19:09:16 joe acpid: 1 client rule loaded
Feb  1 19:09:16 joe acpid: client 15926[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client connected from 15936[0:0]
Feb  1 19:09:16 joe acpid: 1 client rule loaded
Feb  1 19:09:16 joe acpid: client 15936[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client connected from 15925[0:0]
Feb  1 19:09:16 joe acpid: 1 client rule loaded
Feb  1 19:09:16 joe acpid: client 15925[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client connected from 15934[0:0]
Feb  1 19:09:16 joe acpid: 1 client rule loaded
Feb  1 19:09:16 joe acpid: client 15934[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client connected from 15931[0:0]
Feb  1 19:09:16 joe acpid: 1 client rule loaded
Feb  1 19:09:16 joe acpid: client 15931[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client connected from 15928[0:0]
Feb  1 19:09:16 joe acpid: 1 client rule loaded
Feb  1 19:09:16 joe acpid: client 15928[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client connected from 15938[0:0]
Feb  1 19:09:16 joe acpid: 1 client rule loaded
Feb  1 19:09:16 joe acpid: client 15938[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client connected from 15933[0:0]
Feb  1 19:09:16 joe acpid: 1 client rule loaded
Feb  1 19:09:16 joe acpid: client 15933[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client connected from 15932[0:0]
Feb  1 19:09:16 joe acpid: 1 client rule loaded
Feb  1 19:09:16 joe acpid: client 15932[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client connected from 15937[0:0]
Feb  1 19:09:16 joe acpid: 1 client rule loaded
Feb  1 19:09:16 joe acpid: client 15937[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client connected from 15927[0:0]
Feb  1 19:09:16 joe acpid: 1 client rule loaded
Feb  1 19:09:16 joe acpid: client 15927[0:0] has disconnected
Feb  1 19:09:16 joe acpid: client connected from 15929[0:0]
Feb  1 19:09:16 joe acpid: 1 client rule loaded
Feb  1 19:09:22 joe acpid: client 15929[0:0] has disconnected
Feb  1 19:09:22 joe acpid: client connected from 16188[0:0]
Feb  1 19:09:22 joe acpid: 1 client rule loaded
Feb  1 19:09:22 joe acpid: client connected from 16191[0:0]
Feb  1 19:09:22 joe acpid: 1 client rule loaded
Feb  1 19:09:22 joe acpid: client connected from 16189[0:0]
Feb  1 19:09:22 joe acpid: 1 client rule loaded
Feb  1 19:09:22 joe acpid: client 16188[0:0] has disconnected
Feb  1 19:09:22 joe acpid: client 16191[0:0] has disconnected
Feb  1 19:09:22 joe acpid: client 16189[0:0] has disconnected
Feb  1 19:09:22 joe acpid: client connected from 16190[0:0]
Feb  1 19:09:22 joe acpid: 1 client rule loaded
Feb  1 19:09:22 joe acpid: client 16190[0:0] has disconnected
Feb  1 19:09:22 joe acpid: client connected from 16202[0:0]
Feb  1 19:09:22 joe acpid: 1 client rule loaded
Feb  1 19:09:22 joe acpid: client 16202[0:0] has disconnected
Feb  1 19:09:22 joe acpid: client connected from 16197[0:0]
Feb  1 19:09:22 joe acpid: 1 client rule loaded
Feb  1 19:09:22 joe acpid: client 16197[0:0] has disconnected
Feb  1 19:09:22 joe acpid: client connected from 16199[0:0]
Feb  1 19:09:22 joe acpid: 1 client rule loaded
Feb  1 19:09:22 joe acpid: client 16199[0:0] has disconnected
Feb  1 19:09:22 joe acpid: client connected from 16201[0:0]
Feb  1 19:09:22 joe acpid: 1 client rule loaded
Feb  1 19:09:22 joe acpid: client 16201[0:0] has disconnected
Feb  1 19:09:22 joe acpid: client connected from 16198[0:0]
Feb  1 19:09:22 joe acpid: 1 client rule loaded
Feb  1 19:09:22 joe acpid: client 16198[0:0] has disconnected
Feb  1 19:09:22 joe acpid: client connected from 16200[0:0]
Feb  1 19:09:22 joe acpid: 1 client rule loaded
Feb  1 19:09:28 joe acpid: client 16200[0:0] has disconnected
Feb  1 19:09:28 joe acpid: client connected from 16453[0:0]
Feb  1 19:09:28 joe acpid: 1 client rule loaded
Feb  1 19:09:28 joe acpid: client connected from 16456[0:0]
Feb  1 19:09:28 joe acpid: 1 client rule loaded
Feb  1 19:09:28 joe acpid: client connected from 16459[0:0]
Feb  1 19:09:28 joe acpid: 1 client rule loaded
Feb  1 19:09:28 joe acpid: client connected from 16458[0:0]
Feb  1 19:09:28 joe acpid: 1 client rule loaded
Feb  1 19:09:28 joe acpid: client connected from 16457[0:0]
Feb  1 19:09:28 joe acpid: 1 client rule loaded
Feb  1 19:09:28 joe acpid: client 16453[0:0] has disconnected
Feb  1 19:09:28 joe acpid: client 16456[0:0] has disconnected
Feb  1 19:09:28 joe acpid: client 16459[0:0] has disconnected
Feb  1 19:09:28 joe acpid: client 16458[0:0] has disconnected
Feb  1 19:09:28 joe acpid: client 16457[0:0] has disconnected
Feb  1 19:09:28 joe acpid: client connected from 16460[0:0]
Feb  1 19:09:28 joe acpid: 1 client rule loaded
Feb  1 19:09:28 joe acpid: client 16460[0:0] has disconnected
Feb  1 19:09:28 joe acpid: client connected from 16466[0:0]
Feb  1 19:09:28 joe acpid: 1 client rule loaded
Feb  1 19:09:28 joe acpid: client 16466[0:0] has disconnected
Feb  1 19:09:28 joe acpid: client connected from 16470[0:0]
Feb  1 19:09:28 joe acpid: 1 client rule loaded
Feb  1 19:09:28 joe acpid: client 16470[0:0] has disconnected
Feb  1 19:09:28 joe acpid: client connected from 16469[0:0]
Feb  1 19:09:28 joe acpid: 1 client rule loaded
Feb  1 19:09:28 joe acpid: client 16469[0:0] has disconnected
Feb  1 19:09:28 joe acpid: client connected from 16468[0:0]
Feb  1 19:09:28 joe acpid: 1 client rule loaded
Feb  1 19:09:35 joe acpid: client 16468[0:0] has disconnected
Feb  1 19:09:35 joe acpid: client connected from 16733[0:0]
Feb  1 19:09:35 joe acpid: 1 client rule loaded
Feb  1 19:09:35 joe acpid: client connected from 16737[0:0]
Feb  1 19:09:35 joe acpid: 1 client rule loaded
Feb  1 19:09:35 joe acpid: client connected from 16739[0:0]
Feb  1 19:09:35 joe acpid: 1 client rule loaded
Feb  1 19:09:35 joe acpid: client connected from 16735[0:0]
Feb  1 19:09:35 joe acpid: 1 client rule loaded
Feb  1 19:09:35 joe acpid: client connected from 16740[0:0]
Feb  1 19:09:35 joe acpid: 1 client rule loaded
Feb  1 19:09:35 joe acpid: client connected from 16750[0:0]
Feb  1 19:09:35 joe acpid: 1 client rule loaded
Feb  1 19:09:35 joe acpid: client connected from 16746[0:0]
Feb  1 19:09:35 joe acpid: 1 client rule loaded
Feb  1 19:09:35 joe acpid: client connected from 16754[0:0]
Feb  1 19:09:35 joe acpid: 1 client rule loaded
Feb  1 19:09:35 joe acpid: client connected from 16753[0:0]
Feb  1 19:09:35 joe acpid: 1 client rule loaded
Feb  1 19:09:35 joe acpid: client connected from 16744[0:0]
Feb  1 19:09:35 joe acpid: 1 client rule loaded
Feb  1 19:09:35 joe acpid: client connected from 16745[0:0]
Feb  1 19:09:35 joe acpid: 1 client rule loaded
Feb  1 19:09:35 joe acpid: client connected from 16755[0:0]
Feb  1 19:09:35 joe acpid: 1 client rule loaded
Feb  1 19:09:35 joe acpid: client connected from 16751[0:0]
Feb  1 19:09:35 joe acpid: 1 client rule loaded
Feb  1 19:09:35 joe acpid: client connected from 16748[0:0]
Feb  1 19:09:35 joe acpid: 1 client rule loaded
Feb  1 19:09:35 joe acpid: client connected from 16749[0:0]
Feb  1 19:09:35 joe acpid: 1 client rule loaded
Feb  1 19:09:35 joe acpid: client connected from 16761[0:0]
Feb  1 19:09:35 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client 16733[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client 16737[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client 16739[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client 16735[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client 16740[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client 16750[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client 16746[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client 16754[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client 16753[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client 16744[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client 16745[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client 16755[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client 16751[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client 16748[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client 16749[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client 16761[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client connected from 17012[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client 17012[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client connected from 17021[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client 17021[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client connected from 17017[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client 17017[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client connected from 17018[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client 17018[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client connected from 17016[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client 17016[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client connected from 17022[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client 17022[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client connected from 17028[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client 17028[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client connected from 17036[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client 17036[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client connected from 17031[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client 17031[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client connected from 17037[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client 17037[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client connected from 17039[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client 17039[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client connected from 17034[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client 17034[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client connected from 17015[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client 17015[0:0] has disconnected
Feb  1 19:09:44 joe acpid: client connected from 17023[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client connected from 17035[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client connected from 17033[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client connected from 17032[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client connected from 17040[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client connected from 17041[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client connected from 17038[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client connected from 17060[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client connected from 17061[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client connected from 17058[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client connected from 17059[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client connected from 17064[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client connected from 17056[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client connected from 17057[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client connected from 17063[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client connected from 17062[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:44 joe acpid: client connected from 17065[0:0]
Feb  1 19:09:44 joe acpid: 1 client rule loaded
Feb  1 19:09:53 joe acpid: client 17023[0:0] has disconnected
Feb  1 19:09:53 joe acpid: client 17035[0:0] has disconnected
Feb  1 19:09:53 joe acpid: client 17033[0:0] has disconnected
Feb  1 19:09:53 joe acpid: client 17032[0:0] has disconnected
Feb  1 19:09:53 joe acpid: client 17040[0:0] has disconnected
Feb  1 19:09:53 joe acpid: client 17041[0:0] has disconnected
Feb  1 19:09:53 joe acpid: client 17038[0:0] has disconnected
Feb  1 19:09:53 joe acpid: client 17060[0:0] has disconnected
Feb  1 19:09:53 joe acpid: client 17061[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client 17058[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client 17059[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client 17064[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client 17056[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client 17057[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client 17063[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client 17062[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client 17065[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client connected from 17325[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client 17325[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client connected from 17328[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client 17328[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client connected from 17326[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client 17326[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client connected from 17333[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client 17333[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client connected from 17335[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client 17335[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client connected from 17339[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client 17339[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client connected from 17336[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client 17336[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client connected from 17340[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client 17340[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client connected from 17329[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client 17329[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client connected from 17337[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client 17337[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client connected from 17327[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client 17327[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client connected from 17331[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client 17331[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client connected from 17334[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client 17334[0:0] has disconnected
Feb  1 19:09:54 joe acpid: client connected from 17332[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client connected from 17342[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client connected from 17355[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client connected from 17356[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client connected from 17365[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client connected from 17364[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client connected from 17361[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client connected from 17362[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client connected from 17360[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client connected from 17363[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client connected from 17366[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:54 joe acpid: client connected from 17367[0:0]
Feb  1 19:09:54 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client 17332[0:0] has disconnected
Feb  1 19:09:56 joe acpid: client 17342[0:0] has disconnected
Feb  1 19:09:56 joe acpid: client 17355[0:0] has disconnected
Feb  1 19:09:56 joe acpid: client 17356[0:0] has disconnected
Feb  1 19:09:56 joe acpid: client 17365[0:0] has disconnected
Feb  1 19:09:56 joe acpid: client 17364[0:0] has disconnected
Feb  1 19:09:56 joe acpid: client 17361[0:0] has disconnected
Feb  1 19:09:56 joe acpid: client 17362[0:0] has disconnected
Feb  1 19:09:56 joe acpid: client 17360[0:0] has disconnected
Feb  1 19:09:56 joe acpid: client 17363[0:0] has disconnected
Feb  1 19:09:56 joe acpid: client 17366[0:0] has disconnected
Feb  1 19:09:56 joe acpid: client 17367[0:0] has disconnected
Feb  1 19:09:56 joe acpid: client connected from 17599[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17603[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17606[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17600[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17604[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17602[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17612[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17619[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17616[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17614[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17613[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17620[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17615[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17618[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17621[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17631[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client 17599[0:0] has disconnected
Feb  1 19:09:56 joe acpid: client connected from 17630[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17636[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17638[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17637[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client 17603[0:0] has disconnected
Feb  1 19:09:56 joe acpid: client connected from 17632[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:09:56 joe acpid: client connected from 17639[0:0]
Feb  1 19:09:56 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client 17606[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17600[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17604[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17602[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17612[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17619[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17616[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17614[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17613[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17620[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17615[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17618[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17621[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17631[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17630[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17636[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17638[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17637[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17632[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client 17639[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client connected from 17911[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client 17911[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client connected from 17915[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client 17915[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client connected from 17914[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client 17914[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client connected from 17926[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client 17926[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client connected from 17918[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client 17918[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client connected from 17921[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client 17921[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client connected from 17925[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client 17925[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client connected from 17923[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client 17923[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client connected from 17917[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client 17917[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client connected from 17919[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client 17919[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client connected from 17916[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client 17916[0:0] has disconnected
Feb  1 19:10:08 joe acpid: client connected from 17924[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client connected from 17936[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client connected from 17940[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client connected from 17939[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client connected from 17937[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:08 joe acpid: client connected from 17938[0:0]
Feb  1 19:10:08 joe acpid: 1 client rule loaded
Feb  1 19:10:14 joe acpid: client 17924[0:0] has disconnected
Feb  1 19:10:14 joe acpid: client 17936[0:0] has disconnected
Feb  1 19:10:14 joe acpid: client 17940[0:0] has disconnected
Feb  1 19:10:14 joe acpid: client 17939[0:0] has disconnected
Feb  1 19:10:14 joe acpid: client 17937[0:0] has disconnected
Feb  1 19:10:14 joe acpid: client 17938[0:0] has disconnected
Feb  1 19:10:14 joe acpid: client connected from 18203[0:0]
Feb  1 19:10:14 joe acpid: 1 client rule loaded
Feb  1 19:10:14 joe acpid: client connected from 18202[0:0]
Feb  1 19:10:14 joe acpid: 1 client rule loaded
Feb  1 19:10:14 joe acpid: client connected from 18205[0:0]
Feb  1 19:10:14 joe acpid: 1 client rule loaded
Feb  1 19:10:14 joe acpid: client connected from 18210[0:0]
Feb  1 19:10:14 joe acpid: 1 client rule loaded
Feb  1 19:10:14 joe acpid: client connected from 18209[0:0]
Feb  1 19:10:14 joe acpid: 1 client rule loaded
Feb  1 19:10:14 joe acpid: client connected from 18211[0:0]
Feb  1 19:10:14 joe acpid: 1 client rule loaded
Feb  1 19:10:14 joe acpid: client connected from 18206[0:0]
Feb  1 19:10:14 joe acpid: 1 client rule loaded
Feb  1 19:10:14 joe acpid: client connected from 18207[0:0]
Feb  1 19:10:14 joe acpid: 1 client rule loaded
Feb  1 19:10:14 joe acpid: client connected from 18204[0:0]
Feb  1 19:10:14 joe acpid: 1 client rule loaded
Feb  1 19:10:25 joe acpid: client 18203[0:0] has disconnected
Feb  1 19:10:25 joe acpid: client 18202[0:0] has disconnected
Feb  1 19:10:25 joe acpid: client 18205[0:0] has disconnected
Feb  1 19:10:25 joe acpid: client 18210[0:0] has disconnected
Feb  1 19:10:25 joe acpid: client 18209[0:0] has disconnected
Feb  1 19:10:25 joe acpid: client 18211[0:0] has disconnected
Feb  1 19:10:25 joe acpid: client 18206[0:0] has disconnected
Feb  1 19:10:25 joe acpid: client 18207[0:0] has disconnected
Feb  1 19:10:25 joe acpid: client 18204[0:0] has disconnected
Feb  1 19:10:25 joe acpid: client connected from 18524[0:0]
Feb  1 19:10:25 joe acpid: 1 client rule loaded
Feb  1 19:10:25 joe acpid: client connected from 18526[0:0]
Feb  1 19:10:25 joe acpid: 1 client rule loaded
Feb  1 19:10:25 joe acpid: client connected from 18532[0:0]
Feb  1 19:10:25 joe acpid: 1 client rule loaded
Feb  1 19:10:25 joe acpid: client connected from 18527[0:0]
Feb  1 19:10:25 joe acpid: 1 client rule loaded
Feb  1 19:10:25 joe acpid: client connected from 18523[0:0]
Feb  1 19:10:25 joe acpid: 1 client rule loaded
Feb  1 19:10:25 joe acpid: client connected from 18531[0:0]
Feb  1 19:10:25 joe acpid: 1 client rule loaded
Feb  1 19:10:25 joe acpid: client connected from 18529[0:0]
Feb  1 19:10:25 joe acpid: 1 client rule loaded
Feb  1 19:10:25 joe acpid: client connected from 18525[0:0]
Feb  1 19:10:25 joe acpid: 1 client rule loaded
Feb  1 19:10:25 joe acpid: client connected from 18528[0:0]
Feb  1 19:10:25 joe acpid: 1 client rule loaded
Feb  1 19:10:25 joe acpid: client connected from 18534[0:0]
Feb  1 19:10:25 joe acpid: 1 client rule loaded
Feb  1 19:10:25 joe acpid: client connected from 18544[0:0]
Feb  1 19:10:25 joe acpid: 1 client rule loaded
Feb  1 19:10:25 joe acpid: client connected from 18543[0:0]
Feb  1 19:10:25 joe acpid: 1 client rule loaded
Feb  1 19:10:34 joe acpid: client 18524[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client 18526[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client 18532[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client 18527[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client 18523[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client 18531[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client 18529[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client 18525[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client 18528[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client 18534[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client 18544[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client 18543[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client connected from 18819[0:0]
Feb  1 19:10:34 joe acpid: 1 client rule loaded
Feb  1 19:10:34 joe acpid: client 18819[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client connected from 18820[0:0]
Feb  1 19:10:34 joe acpid: 1 client rule loaded
Feb  1 19:10:34 joe acpid: client 18820[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client connected from 18822[0:0]
Feb  1 19:10:34 joe acpid: 1 client rule loaded
Feb  1 19:10:34 joe acpid: client 18822[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client connected from 18828[0:0]
Feb  1 19:10:34 joe acpid: 1 client rule loaded
Feb  1 19:10:34 joe acpid: client 18828[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client connected from 18824[0:0]
Feb  1 19:10:34 joe acpid: 1 client rule loaded
Feb  1 19:10:34 joe acpid: client 18824[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client connected from 18829[0:0]
Feb  1 19:10:34 joe acpid: 1 client rule loaded
Feb  1 19:10:34 joe acpid: client 18829[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client connected from 18825[0:0]
Feb  1 19:10:34 joe acpid: 1 client rule loaded
Feb  1 19:10:34 joe acpid: client 18825[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client connected from 18832[0:0]
Feb  1 19:10:34 joe acpid: 1 client rule loaded
Feb  1 19:10:34 joe acpid: client 18832[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client connected from 18823[0:0]
Feb  1 19:10:34 joe acpid: 1 client rule loaded
Feb  1 19:10:34 joe acpid: client 18823[0:0] has disconnected
Feb  1 19:10:34 joe acpid: client connected from 18821[0:0]
Feb  1 19:10:34 joe acpid: 1 client rule loaded
Feb  1 19:10:40 joe acpid: client 18821[0:0] has disconnected
Feb  1 19:10:40 joe acpid: client connected from 19128[0:0]
Feb  1 19:10:40 joe acpid: 1 client rule loaded
Feb  1 19:10:40 joe acpid: client connected from 19132[0:0]
Feb  1 19:10:40 joe acpid: 1 client rule loaded
Feb  1 19:10:40 joe acpid: client connected from 19127[0:0]
Feb  1 19:10:40 joe acpid: 1 client rule loaded
Feb  1 19:10:40 joe acpid: client connected from 19134[0:0]
Feb  1 19:10:40 joe acpid: 1 client rule loaded
Feb  1 19:10:40 joe acpid: client connected from 19125[0:0]
Feb  1 19:10:40 joe acpid: 1 client rule loaded
Feb  1 19:10:40 joe acpid: client connected from 19130[0:0]
Feb  1 19:10:40 joe acpid: 1 client rule loaded
Feb  1 19:10:40 joe acpid: client connected from 19126[0:0]
Feb  1 19:10:40 joe acpid: 1 client rule loaded
Feb  1 19:10:40 joe acpid: client connected from 19135[0:0]
Feb  1 19:10:40 joe acpid: 1 client rule loaded
Feb  1 19:10:40 joe acpid: client connected from 19133[0:0]
Feb  1 19:10:40 joe acpid: 1 client rule loaded
Feb  1 19:10:40 joe acpid: client connected from 19131[0:0]
Feb  1 19:10:40 joe acpid: 1 client rule loaded
Feb  1 19:10:48 joe acpid: client 19128[0:0] has disconnected
Feb  1 19:10:48 joe acpid: client 19132[0:0] has disconnected
Feb  1 19:10:48 joe acpid: client 19127[0:0] has disconnected
Feb  1 19:10:48 joe acpid: client 19134[0:0] has disconnected
Feb  1 19:10:48 joe acpid: client 19125[0:0] has disconnected
Feb  1 19:10:48 joe acpid: client 19130[0:0] has disconnected
Feb  1 19:10:48 joe acpid: client 19126[0:0] has disconnected
Feb  1 19:10:48 joe acpid: client 19135[0:0] has disconnected
Feb  1 19:10:48 joe acpid: client 19133[0:0] has disconnected
Feb  1 19:10:48 joe acpid: client 19131[0:0] has disconnected
Feb  1 19:10:48 joe acpid: client connected from 19439[0:0]
Feb  1 19:10:48 joe acpid: 1 client rule loaded
Feb  1 19:10:48 joe acpid: client connected from 19444[0:0]
Feb  1 19:10:48 joe acpid: 1 client rule loaded
Feb  1 19:10:48 joe acpid: client connected from 19442[0:0]
Feb  1 19:10:48 joe acpid: 1 client rule loaded
Feb  1 19:10:48 joe acpid: client connected from 19445[0:0]
Feb  1 19:10:48 joe acpid: 1 client rule loaded
Feb  1 19:10:48 joe acpid: client connected from 19443[0:0]
Feb  1 19:10:48 joe acpid: 1 client rule loaded
Feb  1 19:10:48 joe acpid: client connected from 19440[0:0]
Feb  1 19:10:48 joe acpid: 1 client rule loaded
Feb  1 19:10:48 joe acpid: client connected from 19454[0:0]
Feb  1 19:10:48 joe acpid: 1 client rule loaded
Feb  1 19:10:48 joe acpid: client connected from 19441[0:0]
Feb  1 19:10:48 joe acpid: 1 client rule loaded
Feb  1 19:10:48 joe acpid: client connected from 19455[0:0]
Feb  1 19:10:48 joe acpid: 1 client rule loaded
Feb  1 19:10:48 joe acpid: client connected from 19460[0:0]
Feb  1 19:10:48 joe acpid: 1 client rule loaded
Feb  1 19:10:48 joe acpid: client connected from 19464[0:0]
Feb  1 19:10:48 joe acpid: 1 client rule loaded
Feb  1 19:10:48 joe acpid: client connected from 19456[0:0]
Feb  1 19:10:48 joe acpid: 1 client rule loaded
Feb  1 19:10:48 joe acpid: client connected from 19458[0:0]
Feb  1 19:10:48 joe acpid: 1 client rule loaded
Feb  1 19:10:48 joe acpid: client connected from 19459[0:0]
Feb  1 19:10:48 joe acpid: 1 client rule loaded
Feb  1 19:10:49 joe acpid: client connected from 19463[0:0]
Feb  1 19:10:49 joe acpid: 1 client rule loaded
Feb  1 19:10:49 joe acpid: client connected from 19461[0:0]
Feb  1 19:10:49 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client 19439[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client 19444[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client 19442[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client 19445[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client 19443[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client 19440[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client 19454[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client 19441[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client 19455[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client 19460[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client 19464[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client 19456[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client 19458[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client 19459[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client 19463[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client 19461[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client connected from 19805[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19816[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19818[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19811[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19825[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19819[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19808[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19807[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19812[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19806[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19813[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19814[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19822[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19815[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19809[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19824[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19820[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19817[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19827[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19823[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19843[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19848[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19846[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19849[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19855[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19845[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client 19808[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client connected from 19856[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client 19807[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client connected from 19857[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client 19815[0:0] has disconnected
Feb  1 19:10:58 joe acpid: client connected from 19859[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:10:58 joe acpid: client connected from 19858[0:0]
Feb  1 19:10:58 joe acpid: 1 client rule loaded
Feb  1 19:11:09 joe acpid: client 19805[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19816[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19818[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19811[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19825[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19819[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19812[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19806[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19813[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19814[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19822[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19809[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19824[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19820[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19817[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19827[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19823[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19843[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19848[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19846[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19849[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19855[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19845[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19856[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19857[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19859[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client 19858[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client connected from 20159[0:0]
Feb  1 19:11:09 joe acpid: 1 client rule loaded
Feb  1 19:11:09 joe acpid: client 20159[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client connected from 20160[0:0]
Feb  1 19:11:09 joe acpid: 1 client rule loaded
Feb  1 19:11:09 joe acpid: client 20160[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client connected from 20161[0:0]
Feb  1 19:11:09 joe acpid: 1 client rule loaded
Feb  1 19:11:09 joe acpid: client 20161[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client connected from 20162[0:0]
Feb  1 19:11:09 joe acpid: 1 client rule loaded
Feb  1 19:11:09 joe acpid: client 20162[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client connected from 20168[0:0]
Feb  1 19:11:09 joe acpid: 1 client rule loaded
Feb  1 19:11:09 joe acpid: client 20168[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client connected from 20174[0:0]
Feb  1 19:11:09 joe acpid: 1 client rule loaded
Feb  1 19:11:09 joe acpid: client 20174[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client connected from 20171[0:0]
Feb  1 19:11:09 joe acpid: 1 client rule loaded
Feb  1 19:11:09 joe acpid: client 20171[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client connected from 20170[0:0]
Feb  1 19:11:09 joe acpid: 1 client rule loaded
Feb  1 19:11:09 joe acpid: client 20170[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client connected from 20176[0:0]
Feb  1 19:11:09 joe acpid: 1 client rule loaded
Feb  1 19:11:09 joe acpid: client 20176[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client connected from 20167[0:0]
Feb  1 19:11:09 joe acpid: 1 client rule loaded
Feb  1 19:11:09 joe acpid: client 20167[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client connected from 20172[0:0]
Feb  1 19:11:09 joe acpid: 1 client rule loaded
Feb  1 19:11:09 joe acpid: client 20172[0:0] has disconnected
Feb  1 19:11:09 joe acpid: client connected from 20183[0:0]
Feb  1 19:11:09 joe acpid: 1 client rule loaded
Feb  1 19:11:09 joe acpid: client connected from 20182[0:0]
Feb  1 19:11:09 joe acpid: 1 client rule loaded
Feb  1 19:11:09 joe acpid: client connected from 20186[0:0]
Feb  1 19:11:09 joe acpid: 1 client rule loaded
Feb  1 19:11:09 joe acpid: client connected from 20184[0:0]
Feb  1 19:11:09 joe acpid: 1 client rule loaded
Feb  1 19:11:09 joe acpid: client connected from 20187[0:0]
Feb  1 19:11:09 joe acpid: 1 client rule loaded
Feb  1 19:11:16 joe acpid: client 20183[0:0] has disconnected
Feb  1 19:11:16 joe acpid: client 20182[0:0] has disconnected
Feb  1 19:11:16 joe acpid: client 20186[0:0] has disconnected
Feb  1 19:11:16 joe acpid: client 20184[0:0] has disconnected
Feb  1 19:11:16 joe acpid: client 20187[0:0] has disconnected
Feb  1 19:11:16 joe acpid: client connected from 20530[0:0]
Feb  1 19:11:16 joe acpid: 1 client rule loaded
Feb  1 19:11:16 joe acpid: client connected from 20531[0:0]
Feb  1 19:11:16 joe acpid: 1 client rule loaded
Feb  1 19:11:16 joe acpid: client connected from 20535[0:0]
Feb  1 19:11:16 joe acpid: 1 client rule loaded
Feb  1 19:11:16 joe acpid: client connected from 20539[0:0]
Feb  1 19:11:16 joe acpid: 1 client rule loaded
Feb  1 19:11:16 joe acpid: client connected from 20537[0:0]
Feb  1 19:11:16 joe acpid: 1 client rule loaded
Feb  1 19:11:16 joe acpid: client connected from 20533[0:0]
Feb  1 19:11:16 joe acpid: 1 client rule loaded
Feb  1 19:11:16 joe acpid: client connected from 20534[0:0]
Feb  1 19:11:16 joe acpid: 1 client rule loaded
Feb  1 19:11:16 joe acpid: client connected from 20545[0:0]
Feb  1 19:11:16 joe acpid: 1 client rule loaded
Feb  1 19:11:16 joe acpid: client connected from 20542[0:0]
Feb  1 19:11:16 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client 20530[0:0] has disconnected
Feb  1 19:11:25 joe acpid: client 20531[0:0] has disconnected
Feb  1 19:11:25 joe acpid: client 20535[0:0] has disconnected
Feb  1 19:11:25 joe acpid: client 20539[0:0] has disconnected
Feb  1 19:11:25 joe acpid: client 20537[0:0] has disconnected
Feb  1 19:11:25 joe acpid: client 20533[0:0] has disconnected
Feb  1 19:11:25 joe acpid: client 20534[0:0] has disconnected
Feb  1 19:11:25 joe acpid: client 20545[0:0] has disconnected
Feb  1 19:11:25 joe acpid: client 20542[0:0] has disconnected
Feb  1 19:11:25 joe acpid: client connected from 20920[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20922[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20927[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20926[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20923[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20948[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20925[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20940[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20928[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20938[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20947[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20939[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20934[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20941[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20935[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20937[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20950[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20946[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20944[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20931[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20936[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:25 joe acpid: client connected from 20943[0:0]
Feb  1 19:11:25 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client 20920[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20922[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20927[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20926[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20923[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20948[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20925[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20940[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20928[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20938[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20947[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20939[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20934[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20941[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20935[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20937[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20950[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20946[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20944[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20931[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20936[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client 20943[0:0] has disconnected
Feb  1 19:11:26 joe acpid: client connected from 20964[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client connected from 20966[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client connected from 20970[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client connected from 20969[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client connected from 20975[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client connected from 20971[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client connected from 20974[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client connected from 20978[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client connected from 20984[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client connected from 20980[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client connected from 20979[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client connected from 20977[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client connected from 20972[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client connected from 20985[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client connected from 20983[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client connected from 20982[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:26 joe acpid: client connected from 20973[0:0]
Feb  1 19:11:26 joe acpid: 1 client rule loaded
Feb  1 19:11:34 joe acpid: client 20964[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 20966[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 20970[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 20969[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 20975[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 20971[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 20974[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 20978[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 20984[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 20980[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 20979[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 20977[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 20972[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 20985[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 20983[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 20982[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 20973[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client connected from 21301[0:0]
Feb  1 19:11:34 joe acpid: 1 client rule loaded
Feb  1 19:11:34 joe acpid: client connected from 21303[0:0]
Feb  1 19:11:34 joe acpid: 1 client rule loaded
Feb  1 19:11:34 joe acpid: client connected from 21302[0:0]
Feb  1 19:11:34 joe acpid: 1 client rule loaded
Feb  1 19:11:34 joe acpid: client connected from 21299[0:0]
Feb  1 19:11:34 joe acpid: 1 client rule loaded
Feb  1 19:11:34 joe acpid: client connected from 21300[0:0]
Feb  1 19:11:34 joe acpid: 1 client rule loaded
Feb  1 19:11:34 joe acpid: client 21301[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 21303[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 21302[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 21299[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client 21300[0:0] has disconnected
Feb  1 19:11:34 joe acpid: client connected from 21313[0:0]
Feb  1 19:11:34 joe acpid: 1 client rule loaded
Feb  1 19:11:34 joe acpid: client connected from 21315[0:0]
Feb  1 19:11:34 joe acpid: 1 client rule loaded
Feb  1 19:11:34 joe acpid: client connected from 21317[0:0]
Feb  1 19:11:34 joe acpid: 1 client rule loaded
Feb  1 19:11:34 joe acpid: client connected from 21316[0:0]
Feb  1 19:11:34 joe acpid: 1 client rule loaded
Feb  1 19:11:44 joe acpid: client 21313[0:0] has disconnected
Feb  1 19:11:44 joe acpid: client 21315[0:0] has disconnected
Feb  1 19:11:44 joe acpid: client 21317[0:0] has disconnected
Feb  1 19:11:44 joe acpid: client 21316[0:0] has disconnected
Feb  1 19:11:44 joe acpid: client connected from 21723[0:0]
Feb  1 19:11:44 joe acpid: 1 client rule loaded
Feb  1 19:11:44 joe acpid: client connected from 21719[0:0]
Feb  1 19:11:44 joe acpid: 1 client rule loaded
Feb  1 19:11:44 joe acpid: client connected from 21725[0:0]
Feb  1 19:11:44 joe acpid: 1 client rule loaded
Feb  1 19:11:44 joe acpid: client connected from 21728[0:0]
Feb  1 19:11:44 joe acpid: 1 client rule loaded
Feb  1 19:11:44 joe acpid: client connected from 21726[0:0]
Feb  1 19:11:44 joe acpid: 1 client rule loaded
Feb  1 19:11:44 joe acpid: client connected from 21721[0:0]
Feb  1 19:11:44 joe acpid: 1 client rule loaded
Feb  1 19:11:44 joe acpid: client connected from 21722[0:0]
Feb  1 19:11:44 joe acpid: 1 client rule loaded
Feb  1 19:11:44 joe acpid: client connected from 21718[0:0]
Feb  1 19:11:44 joe acpid: 1 client rule loaded
Feb  1 19:11:44 joe acpid: client connected from 21720[0:0]
Feb  1 19:11:44 joe acpid: 1 client rule loaded
Feb  1 19:11:44 joe acpid: client connected from 21724[0:0]
Feb  1 19:11:44 joe acpid: 1 client rule loaded
Feb  1 19:11:44 joe acpid: client connected from 21731[0:0]
Feb  1 19:11:44 joe acpid: 1 client rule loaded
Feb  1 19:11:44 joe acpid: client connected from 21729[0:0]
Feb  1 19:11:44 joe acpid: 1 client rule loaded
Feb  1 19:11:54 joe acpid: client 21723[0:0] has disconnected
Feb  1 19:11:54 joe acpid: client 21719[0:0] has disconnected
Feb  1 19:11:54 joe acpid: client 21725[0:0] has disconnected
Feb  1 19:11:54 joe acpid: client 21728[0:0] has disconnected
Feb  1 19:11:54 joe acpid: client 21726[0:0] has disconnected
Feb  1 19:11:54 joe acpid: client 21721[0:0] has disconnected
Feb  1 19:11:54 joe acpid: client 21722[0:0] has disconnected
Feb  1 19:11:54 joe acpid: client 21718[0:0] has disconnected
Feb  1 19:11:54 joe acpid: client 21720[0:0] has disconnected
Feb  1 19:11:54 joe acpid: client 21724[0:0] has disconnected
Feb  1 19:11:54 joe acpid: client 21731[0:0] has disconnected
Feb  1 19:11:54 joe acpid: client 21729[0:0] has disconnected
Feb  1 19:11:54 joe acpid: client connected from 22138[0:0]
Feb  1 19:11:54 joe acpid: 1 client rule loaded
Feb  1 19:11:54 joe acpid: client connected from 22150[0:0]
Feb  1 19:11:54 joe acpid: 1 client rule loaded
Feb  1 19:11:54 joe acpid: client connected from 22147[0:0]
Feb  1 19:11:54 joe acpid: 1 client rule loaded
Feb  1 19:11:54 joe acpid: client connected from 22144[0:0]
Feb  1 19:11:54 joe acpid: 1 client rule loaded
Feb  1 19:11:54 joe acpid: client connected from 22146[0:0]
Feb  1 19:11:54 joe acpid: 1 client rule loaded
Feb  1 19:11:54 joe acpid: client connected from 22143[0:0]
Feb  1 19:11:54 joe acpid: 1 client rule loaded
Feb  1 19:11:54 joe acpid: client connected from 22142[0:0]
Feb  1 19:11:54 joe acpid: 1 client rule loaded
Feb  1 19:11:54 joe acpid: client connected from 22141[0:0]
Feb  1 19:11:54 joe acpid: 1 client rule loaded
Feb  1 19:11:54 joe acpid: client connected from 22139[0:0]
Feb  1 19:11:54 joe acpid: 1 client rule loaded
Feb  1 19:11:54 joe acpid: client connected from 22140[0:0]
Feb  1 19:11:54 joe acpid: 1 client rule loaded
Feb  1 19:12:04 joe acpid: client 22138[0:0] has disconnected
Feb  1 19:12:04 joe acpid: client 22150[0:0] has disconnected
Feb  1 19:12:04 joe acpid: client 22147[0:0] has disconnected
Feb  1 19:12:04 joe acpid: client 22144[0:0] has disconnected
Feb  1 19:12:04 joe acpid: client 22146[0:0] has disconnected
Feb  1 19:12:04 joe acpid: client 22143[0:0] has disconnected
Feb  1 19:12:04 joe acpid: client 22142[0:0] has disconnected
Feb  1 19:12:04 joe acpid: client 22141[0:0] has disconnected
Feb  1 19:12:04 joe acpid: client 22139[0:0] has disconnected
Feb  1 19:12:04 joe acpid: client 22140[0:0] has disconnected
Feb  1 19:12:04 joe acpid: client connected from 22586[0:0]
Feb  1 19:12:04 joe acpid: 1 client rule loaded
Feb  1 19:12:04 joe acpid: client connected from 22581[0:0]
Feb  1 19:12:04 joe acpid: 1 client rule loaded
Feb  1 19:12:04 joe acpid: client connected from 22577[0:0]
Feb  1 19:12:04 joe acpid: 1 client rule loaded
Feb  1 19:12:04 joe acpid: client connected from 22575[0:0]
Feb  1 19:12:04 joe acpid: 1 client rule loaded
Feb  1 19:12:04 joe acpid: client connected from 22583[0:0]
Feb  1 19:12:04 joe acpid: 1 client rule loaded
Feb  1 19:12:04 joe acpid: client connected from 22576[0:0]
Feb  1 19:12:04 joe acpid: 1 client rule loaded
Feb  1 19:12:04 joe acpid: client connected from 22578[0:0]
Feb  1 19:12:04 joe acpid: 1 client rule loaded
Feb  1 19:12:04 joe acpid: client connected from 22574[0:0]
Feb  1 19:12:04 joe acpid: 1 client rule loaded
Feb  1 19:12:04 joe acpid: client connected from 22579[0:0]
Feb  1 19:12:04 joe acpid: 1 client rule loaded
Feb  1 19:12:04 joe acpid: client connected from 22580[0:0]
Feb  1 19:12:04 joe acpid: 1 client rule loaded
Feb  1 19:12:16 joe acpid: client 22586[0:0] has disconnected
Feb  1 19:12:16 joe acpid: client 22581[0:0] has disconnected
Feb  1 19:12:16 joe acpid: client 22577[0:0] has disconnected
Feb  1 19:12:16 joe acpid: client 22575[0:0] has disconnected
Feb  1 19:12:16 joe acpid: client 22583[0:0] has disconnected
Feb  1 19:12:16 joe acpid: client 22576[0:0] has disconnected
Feb  1 19:12:16 joe acpid: client 22578[0:0] has disconnected
Feb  1 19:12:16 joe acpid: client 22574[0:0] has disconnected
Feb  1 19:12:16 joe acpid: client 22579[0:0] has disconnected
Feb  1 19:12:16 joe acpid: client 22580[0:0] has disconnected
Feb  1 19:12:16 joe acpid: client connected from 23056[0:0]
Feb  1 19:12:17 joe acpid: 1 client rule loaded
Feb  1 19:12:17 joe acpid: client 23056[0:0] has disconnected
Feb  1 19:12:17 joe acpid: client connected from 23058[0:0]
Feb  1 19:12:17 joe acpid: 1 client rule loaded
Feb  1 19:12:17 joe acpid: client 23058[0:0] has disconnected
Feb  1 19:12:17 joe acpid: client connected from 23069[0:0]
Feb  1 19:12:17 joe acpid: 1 client rule loaded
Feb  1 19:12:17 joe acpid: client 23069[0:0] has disconnected
Feb  1 19:12:17 joe acpid: client connected from 23055[0:0]
Feb  1 19:12:17 joe acpid: 1 client rule loaded
Feb  1 19:12:17 joe acpid: client 23055[0:0] has disconnected
Feb  1 19:12:17 joe acpid: client connected from 23065[0:0]
Feb  1 19:12:17 joe acpid: 1 client rule loaded
Feb  1 19:12:17 joe acpid: client 23065[0:0] has disconnected
Feb  1 19:12:17 joe acpid: client connected from 23057[0:0]
Feb  1 19:12:17 joe acpid: 1 client rule loaded
Feb  1 19:12:17 joe acpid: client 23057[0:0] has disconnected
Feb  1 19:12:17 joe acpid: client connected from 23073[0:0]
Feb  1 19:12:17 joe acpid: 1 client rule loaded
Feb  1 19:12:17 joe acpid: client 23073[0:0] has disconnected
Feb  1 19:12:17 joe acpid: client connected from 23063[0:0]
Feb  1 19:12:17 joe acpid: 1 client rule loaded
Feb  1 19:12:17 joe acpid: client 23063[0:0] has disconnected
Feb  1 19:12:17 joe acpid: client connected from 23060[0:0]
Feb  1 19:12:17 joe acpid: 1 client rule loaded
Feb  1 19:12:17 joe acpid: client 23060[0:0] has disconnected
Feb  1 19:12:17 joe acpid: client connected from 23127[0:0]
Feb  1 19:12:17 joe acpid: 1 client rule loaded
Feb  1 19:12:17 joe acpid: client 23127[0:0] has disconnected
Feb  1 19:12:17 joe acpid: client connected from 23133[0:0]
Feb  1 19:12:17 joe acpid: 1 client rule loaded
Feb  1 19:12:17 joe acpid: client 23133[0:0] has disconnected
Feb  1 19:12:17 joe acpid: client connected from 23134[0:0]
Feb  1 19:12:17 joe acpid: 1 client rule loaded
Feb  1 19:12:17 joe acpid: client 23134[0:0] has disconnected
Feb  1 19:12:17 joe acpid: client connected from 23111[0:0]
Feb  1 19:12:17 joe acpid: 1 client rule loaded
Feb  1 19:12:17 joe acpid: client connected from 23128[0:0]
Feb  1 19:12:17 joe acpid: 1 client rule loaded
Feb  1 19:12:17 joe acpid: client connected from 23126[0:0]
Feb  1 19:12:17 joe acpid: 1 client rule loaded
Feb  1 19:12:17 joe acpid: client connected from 23116[0:0]
Feb  1 19:12:17 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client 23111[0:0] has disconnected
Feb  1 19:12:27 joe acpid: client 23128[0:0] has disconnected
Feb  1 19:12:27 joe acpid: client 23126[0:0] has disconnected
Feb  1 19:12:27 joe acpid: client 23116[0:0] has disconnected
Feb  1 19:12:27 joe acpid: client connected from 23659[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client connected from 23663[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client connected from 23658[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client connected from 23665[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client connected from 23666[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client connected from 23661[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client connected from 23660[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client connected from 23678[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client connected from 23676[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client connected from 23680[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client connected from 23677[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client connected from 23674[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client connected from 23679[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client connected from 23675[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client connected from 23673[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client connected from 23690[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client 23659[0:0] has disconnected
Feb  1 19:12:27 joe acpid: client 23663[0:0] has disconnected
Feb  1 19:12:27 joe acpid: client 23658[0:0] has disconnected
Feb  1 19:12:27 joe acpid: client 23665[0:0] has disconnected
Feb  1 19:12:27 joe acpid: client 23666[0:0] has disconnected
Feb  1 19:12:27 joe acpid: client 23661[0:0] has disconnected
Feb  1 19:12:27 joe acpid: client 23660[0:0] has disconnected
Feb  1 19:12:27 joe acpid: client connected from 23691[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:27 joe acpid: client connected from 23692[0:0]
Feb  1 19:12:27 joe acpid: 1 client rule loaded
Feb  1 19:12:37 joe acpid: client 23678[0:0] has disconnected
Feb  1 19:12:37 joe acpid: client 23676[0:0] has disconnected
Feb  1 19:12:37 joe acpid: client 23680[0:0] has disconnected
Feb  1 19:12:37 joe acpid: client 23677[0:0] has disconnected
Feb  1 19:12:37 joe acpid: client 23674[0:0] has disconnected
Feb  1 19:12:37 joe acpid: client 23679[0:0] has disconnected
Feb  1 19:12:37 joe acpid: client 23675[0:0] has disconnected
Feb  1 19:12:37 joe acpid: client 23673[0:0] has disconnected
Feb  1 19:12:37 joe acpid: client 23690[0:0] has disconnected
Feb  1 19:12:37 joe acpid: client 23691[0:0] has disconnected
Feb  1 19:12:37 joe acpid: client 23692[0:0] has disconnected
Feb  1 19:12:37 joe acpid: client connected from 24085[0:0]
Feb  1 19:12:37 joe acpid: 1 client rule loaded
Feb  1 19:12:37 joe acpid: client connected from 24091[0:0]
Feb  1 19:12:37 joe acpid: 1 client rule loaded
Feb  1 19:12:37 joe acpid: client connected from 24092[0:0]
Feb  1 19:12:37 joe acpid: 1 client rule loaded
Feb  1 19:12:37 joe acpid: client connected from 24081[0:0]
Feb  1 19:12:37 joe acpid: 1 client rule loaded
Feb  1 19:12:37 joe acpid: client connected from 24087[0:0]
Feb  1 19:12:37 joe acpid: 1 client rule loaded
Feb  1 19:12:37 joe acpid: client connected from 24086[0:0]
Feb  1 19:12:37 joe acpid: 1 client rule loaded
Feb  1 19:12:37 joe acpid: client connected from 24084[0:0]
Feb  1 19:12:37 joe acpid: 1 client rule loaded
Feb  1 19:12:37 joe acpid: client connected from 24094[0:0]
Feb  1 19:12:37 joe acpid: 1 client rule loaded
Feb  1 19:12:37 joe acpid: client connected from 24089[0:0]
Feb  1 19:12:37 joe acpid: 1 client rule loaded
Feb  1 19:12:37 joe acpid: client connected from 24083[0:0]
Feb  1 19:12:37 joe acpid: 1 client rule loaded
Feb  1 19:12:37 joe acpid: client connected from 24088[0:0]
Feb  1 19:12:37 joe acpid: 1 client rule loaded
Feb  1 19:12:37 joe acpid: client connected from 24082[0:0]
Feb  1 19:12:37 joe acpid: 1 client rule loaded
Feb  1 19:12:49 joe acpid: client 24085[0:0] has disconnected
Feb  1 19:12:49 joe acpid: client 24091[0:0] has disconnected
Feb  1 19:12:49 joe acpid: client 24092[0:0] has disconnected
Feb  1 19:12:49 joe acpid: client 24081[0:0] has disconnected
Feb  1 19:12:49 joe acpid: client 24087[0:0] has disconnected
Feb  1 19:12:49 joe acpid: client 24086[0:0] has disconnected
Feb  1 19:12:49 joe acpid: client 24084[0:0] has disconnected
Feb  1 19:12:49 joe acpid: client 24094[0:0] has disconnected
Feb  1 19:12:49 joe acpid: client 24089[0:0] has disconnected
Feb  1 19:12:49 joe acpid: client 24083[0:0] has disconnected
Feb  1 19:12:49 joe acpid: client 24088[0:0] has disconnected
Feb  1 19:12:49 joe acpid: client 24082[0:0] has disconnected
Feb  1 19:12:49 joe acpid: client connected from 24485[0:0]
Feb  1 19:12:49 joe acpid: 1 client rule loaded
Feb  1 19:12:49 joe acpid: client connected from 24489[0:0]
Feb  1 19:12:49 joe acpid: 1 client rule loaded
Feb  1 19:12:49 joe acpid: client connected from 24492[0:0]
Feb  1 19:12:49 joe acpid: 1 client rule loaded
Feb  1 19:12:49 joe acpid: client connected from 24487[0:0]
Feb  1 19:12:49 joe acpid: 1 client rule loaded
Feb  1 19:12:49 joe acpid: client connected from 24494[0:0]
Feb  1 19:12:49 joe acpid: 1 client rule loaded
Feb  1 19:12:49 joe acpid: client connected from 24499[0:0]
Feb  1 19:12:49 joe acpid: 1 client rule loaded
Feb  1 19:12:49 joe acpid: client connected from 24506[0:0]
Feb  1 19:12:49 joe acpid: 1 client rule loaded
Feb  1 19:12:49 joe acpid: client connected from 24497[0:0]
Feb  1 19:12:49 joe acpid: 1 client rule loaded
Feb  1 19:12:49 joe acpid: client connected from 24495[0:0]
Feb  1 19:12:49 joe acpid: 1 client rule loaded
Feb  1 19:12:49 joe acpid: client connected from 24488[0:0]
Feb  1 19:12:49 joe acpid: 1 client rule loaded
Feb  1 19:12:49 joe acpid: client connected from 24505[0:0]
Feb  1 19:12:49 joe acpid: 1 client rule loaded
Feb  1 19:12:49 joe acpid: client connected from 24500[0:0]
Feb  1 19:12:49 joe acpid: 1 client rule loaded
Feb  1 19:12:49 joe acpid: client connected from 24504[0:0]
Feb  1 19:12:49 joe acpid: 1 client rule loaded
Feb  1 19:12:49 joe acpid: client connected from 24507[0:0]
Feb  1 19:12:49 joe acpid: 1 client rule loaded
Feb  1 19:12:49 joe acpid: client 24485[0:0] has disconnected
Feb  1 19:12:49 joe acpid: client connected from 24501[0:0]
Feb  1 19:12:49 joe acpid: 1 client rule loaded
Feb  1 19:12:49 joe acpid: client connected from 24503[0:0]
Feb  1 19:12:49 joe acpid: 1 client rule loaded
Feb  1 19:12:50 joe acpid: client 24489[0:0] has disconnected
Feb  1 19:12:50 joe acpid: client 24492[0:0] has disconnected
Feb  1 19:12:50 joe acpid: client 24487[0:0] has disconnected
Feb  1 19:12:50 joe acpid: client 24494[0:0] has disconnected
Feb  1 19:12:50 joe acpid: client 24499[0:0] has disconnected
Feb  1 19:12:50 joe acpid: client 24506[0:0] has disconnected
Feb  1 19:12:50 joe acpid: client 24497[0:0] has disconnected
Feb  1 19:12:50 joe acpid: client 24495[0:0] has disconnected
Feb  1 19:12:50 joe acpid: client 24488[0:0] has disconnected
Feb  1 19:12:50 joe acpid: client 24505[0:0] has disconnected
Feb  1 19:12:50 joe acpid: client 24500[0:0] has disconnected
Feb  1 19:12:50 joe acpid: client 24504[0:0] has disconnected
Feb  1 19:12:50 joe acpid: client 24507[0:0] has disconnected
Feb  1 19:12:50 joe acpid: client 24501[0:0] has disconnected
Feb  1 19:12:50 joe acpid: client 24503[0:0] has disconnected
Feb  1 19:12:50 joe acpid: client connected from 24517[0:0]
Feb  1 19:12:50 joe acpid: 1 client rule loaded
Feb  1 19:12:50 joe acpid: client connected from 24518[0:0]
Feb  1 19:12:50 joe acpid: 1 client rule loaded
Feb  1 19:12:50 joe acpid: client connected from 24521[0:0]
Feb  1 19:12:50 joe acpid: 1 client rule loaded
Feb  1 19:12:50 joe acpid: client connected from 24524[0:0]
Feb  1 19:12:50 joe acpid: 1 client rule loaded
Feb  1 19:12:50 joe acpid: client connected from 24525[0:0]
Feb  1 19:12:50 joe acpid: 1 client rule loaded
Feb  1 19:12:50 joe acpid: client connected from 24523[0:0]
Feb  1 19:12:50 joe acpid: 1 client rule loaded
Feb  1 19:12:50 joe acpid: client connected from 24527[0:0]
Feb  1 19:12:50 joe acpid: 1 client rule loaded
Feb  1 19:12:50 joe acpid: client connected from 24526[0:0]
Feb  1 19:12:50 joe acpid: 1 client rule loaded
Feb  1 19:12:50 joe acpid: client connected from 24519[0:0]
Feb  1 19:12:50 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client 24517[0:0] has disconnected
Feb  1 19:13:00 joe acpid: client 24518[0:0] has disconnected
Feb  1 19:13:00 joe acpid: client 24521[0:0] has disconnected
Feb  1 19:13:00 joe acpid: client 24524[0:0] has disconnected
Feb  1 19:13:00 joe acpid: client 24525[0:0] has disconnected
Feb  1 19:13:00 joe acpid: client 24523[0:0] has disconnected
Feb  1 19:13:00 joe acpid: client 24527[0:0] has disconnected
Feb  1 19:13:00 joe acpid: client 24526[0:0] has disconnected
Feb  1 19:13:00 joe acpid: client 24519[0:0] has disconnected
Feb  1 19:13:00 joe acpid: client connected from 24935[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24914[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24920[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24925[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24909[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24911[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24922[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24916[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24921[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24910[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24929[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24931[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24913[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24917[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24928[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24933[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24918[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24912[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24932[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24930[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24926[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:00 joe acpid: client connected from 24924[0:0]
Feb  1 19:13:00 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client 24935[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24914[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24920[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24925[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24909[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24911[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24922[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24916[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24921[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24910[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24929[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24931[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24913[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24917[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24928[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24933[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24918[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24912[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24932[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24930[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24926[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 24924[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client connected from 25338[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client 25338[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client connected from 25343[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client 25343[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client connected from 25342[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client 25342[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client connected from 25341[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client connected from 25340[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client connected from 25337[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client connected from 25349[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client connected from 25359[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client connected from 25353[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client connected from 25354[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client connected from 25350[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client connected from 25352[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client connected from 25357[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client connected from 25360[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client connected from 25355[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client connected from 25356[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client connected from 25358[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client 25341[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 25340[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 25337[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 25349[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 25359[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 25353[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client connected from 25380[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:11 joe acpid: client 25356[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client 25380[0:0] has disconnected
Feb  1 19:13:11 joe acpid: client connected from 25373[0:0]
Feb  1 19:13:11 joe acpid: 1 client rule loaded
Feb  1 19:13:12 joe acpid: client 25354[0:0] has disconnected
Feb  1 19:13:12 joe acpid: client 25350[0:0] has disconnected
Feb  1 19:13:12 joe acpid: client 25352[0:0] has disconnected
Feb  1 19:13:12 joe acpid: client 25357[0:0] has disconnected
Feb  1 19:13:12 joe acpid: client 25360[0:0] has disconnected
Feb  1 19:13:12 joe acpid: client 25355[0:0] has disconnected
Feb  1 19:13:12 joe acpid: client 25358[0:0] has disconnected
Feb  1 19:13:12 joe acpid: client 25373[0:0] has disconnected
Feb  1 19:13:12 joe acpid: client connected from 25377[0:0]
Feb  1 19:13:12 joe acpid: 1 client rule loaded
Feb  1 19:13:12 joe acpid: client connected from 25374[0:0]
Feb  1 19:13:12 joe acpid: 1 client rule loaded
Feb  1 19:13:12 joe acpid: client connected from 25379[0:0]
Feb  1 19:13:12 joe acpid: 1 client rule loaded
Feb  1 19:13:12 joe acpid: client connected from 25375[0:0]
Feb  1 19:13:12 joe acpid: 1 client rule loaded
Feb  1 19:13:12 joe acpid: client connected from 25372[0:0]
Feb  1 19:13:12 joe acpid: 1 client rule loaded
Feb  1 19:13:12 joe acpid: client connected from 25378[0:0]
Feb  1 19:13:12 joe acpid: 1 client rule loaded
Feb  1 19:13:12 joe acpid: client connected from 25376[0:0]
Feb  1 19:13:12 joe acpid: 1 client rule loaded
Feb  1 19:13:22 joe acpid: client 25377[0:0] has disconnected
Feb  1 19:13:22 joe acpid: client 25374[0:0] has disconnected
Feb  1 19:13:22 joe acpid: client 25379[0:0] has disconnected
Feb  1 19:13:22 joe acpid: client 25375[0:0] has disconnected
Feb  1 19:13:22 joe acpid: client 25372[0:0] has disconnected
Feb  1 19:13:22 joe acpid: client 25378[0:0] has disconnected
Feb  1 19:13:22 joe acpid: client 25376[0:0] has disconnected
Feb  1 19:13:22 joe acpid: client connected from 25772[0:0]
Feb  1 19:13:22 joe acpid: 1 client rule loaded
Feb  1 19:13:22 joe acpid: client connected from 25773[0:0]
Feb  1 19:13:22 joe acpid: 1 client rule loaded
Feb  1 19:13:22 joe acpid: client connected from 25775[0:0]
Feb  1 19:13:22 joe acpid: 1 client rule loaded
Feb  1 19:13:22 joe acpid: client connected from 25776[0:0]
Feb  1 19:13:22 joe acpid: 1 client rule loaded
Feb  1 19:13:22 joe acpid: client connected from 25777[0:0]
Feb  1 19:13:22 joe acpid: 1 client rule loaded
Feb  1 19:13:22 joe acpid: client 25772[0:0] has disconnected
Feb  1 19:13:22 joe acpid: client 25773[0:0] has disconnected
Feb  1 19:13:22 joe acpid: client 25775[0:0] has disconnected
Feb  1 19:13:22 joe acpid: client 25776[0:0] has disconnected
Feb  1 19:13:22 joe acpid: client 25777[0:0] has disconnected
Feb  1 19:13:22 joe acpid: client connected from 25782[0:0]
Feb  1 19:13:22 joe acpid: 1 client rule loaded
Feb  1 19:13:22 joe acpid: client connected from 25786[0:0]
Feb  1 19:13:22 joe acpid: 1 client rule loaded
Feb  1 19:13:22 joe acpid: client connected from 25788[0:0]
Feb  1 19:13:22 joe acpid: 1 client rule loaded
Feb  1 19:13:22 joe acpid: client connected from 25787[0:0]
Feb  1 19:13:22 joe acpid: 1 client rule loaded
Feb  1 19:13:22 joe acpid: client connected from 25785[0:0]
Feb  1 19:13:22 joe acpid: 1 client rule loaded
Feb  1 19:13:22 joe acpid: client connected from 25783[0:0]
Feb  1 19:13:22 joe acpid: 1 client rule loaded
Feb  1 19:13:22 joe acpid: client connected from 25784[0:0]
Feb  1 19:13:22 joe acpid: 1 client rule loaded
Feb  1 19:13:33 joe acpid: client 25782[0:0] has disconnected
Feb  1 19:13:33 joe acpid: client 25786[0:0] has disconnected
Feb  1 19:13:33 joe acpid: client 25788[0:0] has disconnected
Feb  1 19:13:33 joe acpid: client 25787[0:0] has disconnected
Feb  1 19:13:33 joe acpid: client 25785[0:0] has disconnected
Feb  1 19:13:33 joe acpid: client 25783[0:0] has disconnected
Feb  1 19:13:33 joe acpid: client 25784[0:0] has disconnected
Feb  1 19:13:33 joe acpid: client connected from 26198[0:0]
Feb  1 19:13:33 joe acpid: 1 client rule loaded
Feb  1 19:13:33 joe acpid: client connected from 26197[0:0]
Feb  1 19:13:33 joe acpid: 1 client rule loaded
Feb  1 19:13:33 joe acpid: client connected from 26194[0:0]
Feb  1 19:13:33 joe acpid: 1 client rule loaded
Feb  1 19:13:33 joe acpid: client connected from 26193[0:0]
Feb  1 19:13:33 joe acpid: 1 client rule loaded
Feb  1 19:13:33 joe acpid: client connected from 26202[0:0]
Feb  1 19:13:33 joe acpid: 1 client rule loaded
Feb  1 19:13:33 joe acpid: client connected from 26200[0:0]
Feb  1 19:13:33 joe acpid: 1 client rule loaded
Feb  1 19:13:33 joe acpid: client connected from 26201[0:0]
Feb  1 19:13:33 joe acpid: 1 client rule loaded
Feb  1 19:13:33 joe acpid: client connected from 26199[0:0]
Feb  1 19:13:33 joe acpid: 1 client rule loaded
Feb  1 19:13:33 joe acpid: client connected from 26195[0:0]
Feb  1 19:13:33 joe acpid: 1 client rule loaded
Feb  1 19:13:33 joe acpid: client connected from 26196[0:0]
Feb  1 19:13:33 joe acpid: 1 client rule loaded
Feb  1 19:13:34 joe acpid: client 26198[0:0] has disconnected
Feb  1 19:13:34 joe acpid: client 26197[0:0] has disconnected
Feb  1 19:13:34 joe acpid: client 26194[0:0] has disconnected
Feb  1 19:13:34 joe acpid: client 26202[0:0] has disconnected
Feb  1 19:13:34 joe acpid: client 26200[0:0] has disconnected
Feb  1 19:13:34 joe acpid: client 26201[0:0] has disconnected
Feb  1 19:13:34 joe acpid: client 26199[0:0] has disconnected
Feb  1 19:13:34 joe acpid: client 26196[0:0] has disconnected
Feb  1 19:13:34 joe acpid: client connected from 26216[0:0]
Feb  1 19:13:34 joe acpid: 1 client rule loaded
Feb  1 19:13:34 joe acpid: client 26193[0:0] has disconnected
Feb  1 19:13:34 joe acpid: client 26195[0:0] has disconnected
Feb  1 19:13:34 joe acpid: client connected from 26219[0:0]
Feb  1 19:13:34 joe acpid: 1 client rule loaded
Feb  1 19:13:34 joe acpid: client connected from 26215[0:0]
Feb  1 19:13:34 joe acpid: 1 client rule loaded
Feb  1 19:13:34 joe acpid: client connected from 26222[0:0]
Feb  1 19:13:34 joe acpid: 1 client rule loaded
Feb  1 19:13:34 joe acpid: client connected from 26221[0:0]
Feb  1 19:13:34 joe acpid: 1 client rule loaded
Feb  1 19:13:34 joe acpid: client connected from 26223[0:0]
Feb  1 19:13:34 joe acpid: 1 client rule loaded
Feb  1 19:13:34 joe acpid: client connected from 26230[0:0]
Feb  1 19:13:34 joe acpid: 1 client rule loaded
Feb  1 19:13:34 joe acpid: client connected from 26220[0:0]
Feb  1 19:13:34 joe acpid: 1 client rule loaded
Feb  1 19:13:34 joe acpid: client connected from 26225[0:0]
Feb  1 19:13:34 joe acpid: 1 client rule loaded
Feb  1 19:13:34 joe acpid: client connected from 26229[0:0]
Feb  1 19:13:34 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client 26216[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26219[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26215[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26222[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26221[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26223[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26230[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26220[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26225[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26229[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client connected from 26607[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26609[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26610[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26614[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26605[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26613[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26623[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26615[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26608[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26606[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26619[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26620[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26617[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26622[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26624[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26618[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client 26607[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26609[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26610[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26605[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26613[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26615[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26606[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26622[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26624[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client connected from 26638[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client 26614[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26623[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26608[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26619[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26620[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26617[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client 26618[0:0] has disconnected
Feb  1 19:13:45 joe acpid: client connected from 26637[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26643[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26642[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:45 joe acpid: client connected from 26641[0:0]
Feb  1 19:13:45 joe acpid: 1 client rule loaded
Feb  1 19:13:57 joe acpid: client 26638[0:0] has disconnected
Feb  1 19:13:57 joe acpid: client 26637[0:0] has disconnected
Feb  1 19:13:57 joe acpid: client 26643[0:0] has disconnected
Feb  1 19:13:57 joe acpid: client 26642[0:0] has disconnected
Feb  1 19:13:57 joe acpid: client 26641[0:0] has disconnected
Feb  1 19:13:57 joe acpid: client connected from 27020[0:0]
Feb  1 19:13:57 joe acpid: 1 client rule loaded
Feb  1 19:13:57 joe acpid: client connected from 27023[0:0]
Feb  1 19:13:57 joe acpid: 1 client rule loaded
Feb  1 19:13:57 joe acpid: client connected from 27022[0:0]
Feb  1 19:13:57 joe acpid: 1 client rule loaded
Feb  1 19:13:57 joe acpid: client connected from 27026[0:0]
Feb  1 19:13:57 joe acpid: 1 client rule loaded
Feb  1 19:13:57 joe acpid: client 27020[0:0] has disconnected
Feb  1 19:13:57 joe acpid: client connected from 27028[0:0]
Feb  1 19:13:57 joe acpid: 1 client rule loaded
Feb  1 19:13:57 joe acpid: client connected from 27032[0:0]
Feb  1 19:13:57 joe acpid: 1 client rule loaded
Feb  1 19:13:57 joe acpid: client connected from 27033[0:0]
Feb  1 19:13:57 joe acpid: 1 client rule loaded
Feb  1 19:13:57 joe acpid: client connected from 27038[0:0]
Feb  1 19:13:57 joe acpid: 1 client rule loaded
Feb  1 19:13:57 joe acpid: client connected from 27024[0:0]
Feb  1 19:13:57 joe acpid: 1 client rule loaded
Feb  1 19:13:57 joe acpid: client connected from 27029[0:0]
Feb  1 19:13:57 joe acpid: 1 client rule loaded
Feb  1 19:13:57 joe acpid: client connected from 27035[0:0]
Feb  1 19:13:57 joe acpid: 1 client rule loaded
Feb  1 19:13:57 joe acpid: client 27022[0:0] has disconnected
Feb  1 19:13:57 joe acpid: client connected from 27036[0:0]
Feb  1 19:13:57 joe acpid: 1 client rule loaded
Feb  1 19:13:57 joe acpid: client connected from 27037[0:0]
Feb  1 19:13:57 joe acpid: 1 client rule loaded
Feb  1 19:14:09 joe acpid: client 27023[0:0] has disconnected
Feb  1 19:14:09 joe acpid: client 27026[0:0] has disconnected
Feb  1 19:14:09 joe acpid: client 27028[0:0] has disconnected
Feb  1 19:14:09 joe acpid: client 27032[0:0] has disconnected
Feb  1 19:14:09 joe acpid: client 27033[0:0] has disconnected
Feb  1 19:14:09 joe acpid: client 27038[0:0] has disconnected
Feb  1 19:14:09 joe acpid: client 27024[0:0] has disconnected
Feb  1 19:14:09 joe acpid: client 27029[0:0] has disconnected
Feb  1 19:14:09 joe acpid: client 27035[0:0] has disconnected
Feb  1 19:14:09 joe acpid: client 27036[0:0] has disconnected
Feb  1 19:14:09 joe acpid: client 27037[0:0] has disconnected
Feb  1 19:14:09 joe acpid: client connected from 27440[0:0]
Feb  1 19:14:09 joe acpid: 1 client rule loaded
Feb  1 19:14:09 joe acpid: client connected from 27442[0:0]
Feb  1 19:14:09 joe acpid: 1 client rule loaded
Feb  1 19:14:09 joe acpid: client connected from 27441[0:0]
Feb  1 19:14:09 joe acpid: 1 client rule loaded
Feb  1 19:14:09 joe acpid: client 27440[0:0] has disconnected
Feb  1 19:14:09 joe acpid: client 27442[0:0] has disconnected
Feb  1 19:14:09 joe acpid: client 27441[0:0] has disconnected
Feb  1 19:14:09 joe acpid: client connected from 27453[0:0]
Feb  1 19:14:09 joe acpid: 1 client rule loaded
Feb  1 19:14:09 joe acpid: client connected from 27451[0:0]
Feb  1 19:14:09 joe acpid: 1 client rule loaded
Feb  1 19:14:09 joe acpid: client connected from 27449[0:0]
Feb  1 19:14:09 joe acpid: 1 client rule loaded
Feb  1 19:14:09 joe acpid: client connected from 27447[0:0]
Feb  1 19:14:09 joe acpid: 1 client rule loaded
Feb  1 19:14:09 joe acpid: client connected from 27452[0:0]
Feb  1 19:14:09 joe acpid: 1 client rule loaded
Feb  1 19:14:09 joe acpid: client connected from 27450[0:0]
Feb  1 19:14:09 joe acpid: 1 client rule loaded
Feb  1 19:14:09 joe acpid: client connected from 27448[0:0]
Feb  1 19:14:09 joe acpid: 1 client rule loaded
Feb  1 19:14:09 joe acpid: client connected from 27454[0:0]
Feb  1 19:14:09 joe acpid: 1 client rule loaded
Feb  1 19:14:09 joe acpid: client connected from 27446[0:0]
Feb  1 19:14:09 joe acpid: 1 client rule loaded
Feb  1 19:14:22 joe acpid: client 27453[0:0] has disconnected
Feb  1 19:14:22 joe acpid: client 27451[0:0] has disconnected
Feb  1 19:14:22 joe acpid: client 27449[0:0] has disconnected
Feb  1 19:14:22 joe acpid: client 27447[0:0] has disconnected
Feb  1 19:14:22 joe acpid: client 27452[0:0] has disconnected
Feb  1 19:14:22 joe acpid: client 27450[0:0] has disconnected
Feb  1 19:14:22 joe acpid: client 27448[0:0] has disconnected
Feb  1 19:14:22 joe acpid: client 27454[0:0] has disconnected
Feb  1 19:14:22 joe acpid: client 27446[0:0] has disconnected
Feb  1 19:14:22 joe acpid: client connected from 27858[0:0]
Feb  1 19:14:22 joe acpid: 1 client rule loaded
Feb  1 19:14:22 joe acpid: client connected from 27856[0:0]
Feb  1 19:14:22 joe acpid: 1 client rule loaded
Feb  1 19:14:22 joe acpid: client connected from 27855[0:0]
Feb  1 19:14:22 joe acpid: 1 client rule loaded
Feb  1 19:14:22 joe acpid: client connected from 27861[0:0]
Feb  1 19:14:22 joe acpid: 1 client rule loaded
Feb  1 19:14:22 joe acpid: client connected from 27857[0:0]
Feb  1 19:14:22 joe acpid: 1 client rule loaded
Feb  1 19:14:22 joe acpid: client connected from 27862[0:0]
Feb  1 19:14:22 joe acpid: 1 client rule loaded
Feb  1 19:14:22 joe acpid: client connected from 27860[0:0]
Feb  1 19:14:22 joe acpid: 1 client rule loaded
Feb  1 19:14:22 joe acpid: client connected from 27854[0:0]
Feb  1 19:14:22 joe acpid: 1 client rule loaded
Feb  1 19:14:22 joe acpid: client connected from 27871[0:0]
Feb  1 19:14:22 joe acpid: 1 client rule loaded
Feb  1 19:14:22 joe acpid: client connected from 27870[0:0]
Feb  1 19:14:22 joe acpid: 1 client rule loaded
Feb  1 19:14:22 joe acpid: client connected from 27873[0:0]
Feb  1 19:14:22 joe acpid: 1 client rule loaded
Feb  1 19:14:22 joe acpid: client connected from 27874[0:0]
Feb  1 19:14:22 joe acpid: 1 client rule loaded
Feb  1 19:14:22 joe acpid: client connected from 27872[0:0]
Feb  1 19:14:22 joe acpid: 1 client rule loaded
Feb  1 19:14:35 joe acpid: client 27858[0:0] has disconnected
Feb  1 19:14:35 joe acpid: client 27856[0:0] has disconnected
Feb  1 19:14:35 joe acpid: client 27855[0:0] has disconnected
Feb  1 19:14:35 joe acpid: client 27861[0:0] has disconnected
Feb  1 19:14:35 joe acpid: client 27857[0:0] has disconnected
Feb  1 19:14:35 joe acpid: client 27862[0:0] has disconnected
Feb  1 19:14:35 joe acpid: client 27860[0:0] has disconnected
Feb  1 19:14:35 joe acpid: client 27854[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client 27871[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client 27870[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client 27873[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client 27874[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client 27872[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client connected from 28288[0:0]
Feb  1 19:14:36 joe acpid: 1 client rule loaded
Feb  1 19:14:36 joe acpid: client 28288[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client connected from 28289[0:0]
Feb  1 19:14:36 joe acpid: 1 client rule loaded
Feb  1 19:14:36 joe acpid: client 28289[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client connected from 28292[0:0]
Feb  1 19:14:36 joe acpid: 1 client rule loaded
Feb  1 19:14:36 joe acpid: client 28292[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client connected from 28294[0:0]
Feb  1 19:14:36 joe acpid: 1 client rule loaded
Feb  1 19:14:36 joe acpid: client 28294[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client connected from 28300[0:0]
Feb  1 19:14:36 joe acpid: 1 client rule loaded
Feb  1 19:14:36 joe acpid: client 28300[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client connected from 28301[0:0]
Feb  1 19:14:36 joe acpid: 1 client rule loaded
Feb  1 19:14:36 joe acpid: client 28301[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client connected from 28290[0:0]
Feb  1 19:14:36 joe acpid: 1 client rule loaded
Feb  1 19:14:36 joe acpid: client 28290[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client connected from 28302[0:0]
Feb  1 19:14:36 joe acpid: 1 client rule loaded
Feb  1 19:14:36 joe acpid: client 28302[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client connected from 28291[0:0]
Feb  1 19:14:36 joe acpid: 1 client rule loaded
Feb  1 19:14:36 joe acpid: client 28291[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client connected from 28297[0:0]
Feb  1 19:14:36 joe acpid: 1 client rule loaded
Feb  1 19:14:36 joe acpid: client 28297[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client connected from 28303[0:0]
Feb  1 19:14:36 joe acpid: 1 client rule loaded
Feb  1 19:14:36 joe acpid: client 28303[0:0] has disconnected
Feb  1 19:14:36 joe acpid: client connected from 28296[0:0]
Feb  1 19:14:36 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client 28296[0:0] has disconnected
Feb  1 19:14:45 joe acpid: client connected from 28714[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28713[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client 28714[0:0] has disconnected
Feb  1 19:14:45 joe acpid: client connected from 28717[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28718[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client 28713[0:0] has disconnected
Feb  1 19:14:45 joe acpid: client connected from 28726[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28731[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28722[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28721[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28732[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28730[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28734[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28728[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28723[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28725[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28733[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28729[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28735[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28727[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28749[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28746[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client connected from 28750[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:14:45 joe acpid: client 28717[0:0] has disconnected
Feb  1 19:14:45 joe acpid: client 28718[0:0] has disconnected
Feb  1 19:14:45 joe acpid: client connected from 28755[0:0]
Feb  1 19:14:45 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client 28726[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28731[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28722[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28721[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28732[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28730[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28734[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28728[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28723[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28725[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28733[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28729[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28735[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28727[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28749[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28746[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28750[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client 28755[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client connected from 29237[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client 29237[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client connected from 29210[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client 29210[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client connected from 29203[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client 29203[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client connected from 29188[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client 29188[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client connected from 29216[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client 29216[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client connected from 29197[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client 29197[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client connected from 29215[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client 29215[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client connected from 29180[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client 29180[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client connected from 29238[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client 29238[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client connected from 29235[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client 29235[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client connected from 29193[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client 29193[0:0] has disconnected
Feb  1 19:15:01 joe acpid: client connected from 29218[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29202[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29196[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29236[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29208[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29212[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29189[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29182[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29187[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29209[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29184[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29205[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29183[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29194[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29199[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29213[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29206[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29195[0:0]
Feb  1 19:15:01 joe acpid: 1 client rule loaded
Feb  1 19:15:01 joe acpid: client connected from 29201[0:0]
Feb  1 19:15:02 joe acpid: 1 client rule loaded
Feb  1 19:15:02 joe acpid: client connected from 29219[0:0]
Feb  1 19:15:02 joe acpid: 1 client rule loaded
Feb  1 19:15:08 joe acpid: client 29218[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29202[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29196[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29236[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29208[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29212[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29189[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29182[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29187[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29209[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29184[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29205[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29183[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29194[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29199[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29213[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29206[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29195[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29201[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client 29219[0:0] has disconnected
Feb  1 19:15:08 joe acpid: client connected from 29597[0:0]
Feb  1 19:15:08 joe acpid: 1 client rule loaded
Feb  1 19:15:08 joe acpid: client connected from 29600[0:0]
Feb  1 19:15:08 joe acpid: 1 client rule loaded
Feb  1 19:15:08 joe acpid: client connected from 29596[0:0]
Feb  1 19:15:08 joe acpid: 1 client rule loaded
Feb  1 19:15:08 joe acpid: client connected from 29601[0:0]
Feb  1 19:15:08 joe acpid: 1 client rule loaded
Feb  1 19:15:08 joe acpid: client connected from 29599[0:0]
Feb  1 19:15:08 joe acpid: 1 client rule loaded
Feb  1 19:15:08 joe acpid: client connected from 29594[0:0]
Feb  1 19:15:08 joe acpid: 1 client rule loaded
Feb  1 19:15:08 joe acpid: client connected from 29598[0:0]
Feb  1 19:15:08 joe acpid: 1 client rule loaded
Feb  1 19:15:08 joe acpid: client connected from 29595[0:0]
Feb  1 19:15:08 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client 29597[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client 29600[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client 29596[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client 29601[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client 29599[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client 29594[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client 29598[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client 29595[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client connected from 30038[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client 30038[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client connected from 30042[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client 30042[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client connected from 30039[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client 30039[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client connected from 30048[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client 30048[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client connected from 30040[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client 30040[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client connected from 30046[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client 30046[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client connected from 30050[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client 30050[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client connected from 30058[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client 30058[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client connected from 30047[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client 30047[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client connected from 30054[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client 30054[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client connected from 30055[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client 30055[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client connected from 30072[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client 30072[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client connected from 30056[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client 30056[0:0] has disconnected
Feb  1 19:15:22 joe acpid: client connected from 30059[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client connected from 30061[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client connected from 30060[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client connected from 30057[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client connected from 30074[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client connected from 30073[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:22 joe acpid: client connected from 30049[0:0]
Feb  1 19:15:22 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client 30059[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client 30061[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client 30060[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client 30057[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client 30074[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client 30073[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client 30049[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client connected from 30474[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client connected from 30482[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client 30474[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client 30482[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client connected from 30478[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client 30478[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client connected from 30480[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client 30480[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client connected from 30486[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client 30486[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client connected from 30488[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client 30488[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client connected from 30492[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client 30492[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client connected from 30489[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client 30489[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client connected from 30479[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client 30479[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client connected from 30490[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client 30490[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client connected from 30481[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client 30481[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client connected from 30477[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client 30477[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client connected from 30484[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client 30484[0:0] has disconnected
Feb  1 19:15:34 joe acpid: client connected from 30483[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client connected from 30485[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client connected from 30491[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client connected from 30508[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client connected from 30509[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client connected from 30511[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client connected from 30510[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:34 joe acpid: client connected from 30512[0:0]
Feb  1 19:15:34 joe acpid: 1 client rule loaded
Feb  1 19:15:44 joe acpid: client 30483[0:0] has disconnected
Feb  1 19:15:44 joe acpid: client 30485[0:0] has disconnected
Feb  1 19:15:44 joe acpid: client 30491[0:0] has disconnected
Feb  1 19:15:44 joe acpid: client 30508[0:0] has disconnected
Feb  1 19:15:44 joe acpid: client 30509[0:0] has disconnected
Feb  1 19:15:44 joe acpid: client 30511[0:0] has disconnected
Feb  1 19:15:44 joe acpid: client 30510[0:0] has disconnected
Feb  1 19:15:44 joe acpid: client 30512[0:0] has disconnected
Feb  1 19:15:44 joe acpid: client connected from 30899[0:0]
Feb  1 19:15:44 joe acpid: 1 client rule loaded
Feb  1 19:15:44 joe acpid: client connected from 30896[0:0]
Feb  1 19:15:44 joe acpid: 1 client rule loaded
Feb  1 19:15:44 joe acpid: client connected from 30902[0:0]
Feb  1 19:15:44 joe acpid: 1 client rule loaded
Feb  1 19:15:44 joe acpid: client connected from 30900[0:0]
Feb  1 19:15:44 joe acpid: 1 client rule loaded
Feb  1 19:15:44 joe acpid: client connected from 30904[0:0]
Feb  1 19:15:44 joe acpid: 1 client rule loaded
Feb  1 19:15:44 joe acpid: client connected from 30897[0:0]
Feb  1 19:15:44 joe acpid: 1 client rule loaded
Feb  1 19:15:44 joe acpid: client connected from 30898[0:0]
Feb  1 19:15:44 joe acpid: 1 client rule loaded
Feb  1 19:15:44 joe acpid: client connected from 30903[0:0]
Feb  1 19:15:44 joe acpid: 1 client rule loaded
Feb  1 19:15:56 joe acpid: client 30899[0:0] has disconnected
Feb  1 19:15:56 joe acpid: client 30896[0:0] has disconnected
Feb  1 19:15:56 joe acpid: client 30902[0:0] has disconnected
Feb  1 19:15:56 joe acpid: client 30900[0:0] has disconnected
Feb  1 19:15:56 joe acpid: client 30904[0:0] has disconnected
Feb  1 19:15:56 joe acpid: client 30897[0:0] has disconnected
Feb  1 19:15:56 joe acpid: client 30898[0:0] has disconnected
Feb  1 19:15:56 joe acpid: client 30903[0:0] has disconnected
Feb  1 19:15:56 joe acpid: client connected from 31314[0:0]
Feb  1 19:15:56 joe acpid: 1 client rule loaded
Feb  1 19:15:56 joe acpid: client connected from 31315[0:0]
Feb  1 19:15:56 joe acpid: 1 client rule loaded
Feb  1 19:15:56 joe acpid: client connected from 31317[0:0]
Feb  1 19:15:56 joe acpid: 1 client rule loaded
Feb  1 19:15:56 joe acpid: client connected from 31316[0:0]
Feb  1 19:15:56 joe acpid: 1 client rule loaded
Feb  1 19:15:56 joe acpid: client connected from 31318[0:0]
Feb  1 19:15:56 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client 31314[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client 31315[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client 31317[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client 31316[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client 31318[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client connected from 31757[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client connected from 31758[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client 31757[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client 31758[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client connected from 31762[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client 31762[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client connected from 31761[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client 31761[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client connected from 31755[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client 31755[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client connected from 31756[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client 31756[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client connected from 31763[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client 31763[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client connected from 31768[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client 31768[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client connected from 31770[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client 31770[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client connected from 31764[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client 31764[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client connected from 31769[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client 31769[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client connected from 31771[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client 31771[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client connected from 31781[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client 31781[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client connected from 31779[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client 31779[0:0] has disconnected
Feb  1 19:16:11 joe acpid: client connected from 31780[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client connected from 31784[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client connected from 31782[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client connected from 31793[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client connected from 31785[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client connected from 31783[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client connected from 31792[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client connected from 31797[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client connected from 31796[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client connected from 31798[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:11 joe acpid: client connected from 31799[0:0]
Feb  1 19:16:11 joe acpid: 1 client rule loaded
Feb  1 19:16:22 joe acpid: client 31780[0:0] has disconnected
Feb  1 19:16:22 joe acpid: client 31784[0:0] has disconnected
Feb  1 19:16:22 joe acpid: client 31782[0:0] has disconnected
Feb  1 19:16:22 joe acpid: client 31793[0:0] has disconnected
Feb  1 19:16:22 joe acpid: client 31785[0:0] has disconnected
Feb  1 19:16:22 joe acpid: client 31783[0:0] has disconnected
Feb  1 19:16:22 joe acpid: client 31792[0:0] has disconnected
Feb  1 19:16:22 joe acpid: client 31797[0:0] has disconnected
Feb  1 19:16:22 joe acpid: client 31796[0:0] has disconnected
Feb  1 19:16:22 joe acpid: client 31798[0:0] has disconnected
Feb  1 19:16:22 joe acpid: client 31799[0:0] has disconnected
Feb  1 19:16:22 joe acpid: client connected from 32202[0:0]
Feb  1 19:16:22 joe acpid: 1 client rule loaded
Feb  1 19:16:22 joe acpid: client connected from 32205[0:0]
Feb  1 19:16:22 joe acpid: 1 client rule loaded
Feb  1 19:16:22 joe acpid: client connected from 32212[0:0]
Feb  1 19:16:22 joe acpid: 1 client rule loaded
Feb  1 19:16:22 joe acpid: client connected from 32211[0:0]
Feb  1 19:16:22 joe acpid: 1 client rule loaded
Feb  1 19:16:22 joe acpid: client connected from 32204[0:0]
Feb  1 19:16:22 joe acpid: 1 client rule loaded
Feb  1 19:16:22 joe acpid: client connected from 32203[0:0]
Feb  1 19:16:22 joe acpid: 1 client rule loaded
Feb  1 19:16:22 joe acpid: client connected from 32208[0:0]
Feb  1 19:16:22 joe acpid: 1 client rule loaded
Feb  1 19:16:22 joe acpid: client connected from 32206[0:0]
Feb  1 19:16:22 joe acpid: 1 client rule loaded
Feb  1 19:16:22 joe acpid: client connected from 32209[0:0]
Feb  1 19:16:22 joe acpid: 1 client rule loaded
Feb  1 19:16:22 joe acpid: client connected from 32222[0:0]
Feb  1 19:16:22 joe acpid: 1 client rule loaded
Feb  1 19:16:22 joe acpid: client connected from 32223[0:0]
Feb  1 19:16:22 joe acpid: 1 client rule loaded
Feb  1 19:16:22 joe acpid: client 32202[0:0] has disconnected
Feb  1 19:16:22 joe acpid: client 32203[0:0] has disconnected
Feb  1 19:16:22 joe acpid: client connected from 32221[0:0]
Feb  1 19:16:22 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client 32205[0:0] has disconnected
Feb  1 19:16:36 joe acpid: client 32212[0:0] has disconnected
Feb  1 19:16:36 joe acpid: client 32211[0:0] has disconnected
Feb  1 19:16:36 joe acpid: client 32204[0:0] has disconnected
Feb  1 19:16:36 joe acpid: client 32208[0:0] has disconnected
Feb  1 19:16:36 joe acpid: client 32206[0:0] has disconnected
Feb  1 19:16:36 joe acpid: client 32209[0:0] has disconnected
Feb  1 19:16:36 joe acpid: client 32222[0:0] has disconnected
Feb  1 19:16:36 joe acpid: client 32223[0:0] has disconnected
Feb  1 19:16:36 joe acpid: client 32221[0:0] has disconnected
Feb  1 19:16:36 joe acpid: client connected from 32648[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32652[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32653[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32649[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32650[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32656[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32657[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32654[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32659[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32669[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32658[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32671[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32673[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32678[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32675[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32674[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32679[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32677[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32680[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client 32652[0:0] has disconnected
Feb  1 19:16:36 joe acpid: client connected from 32676[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32681[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:36 joe acpid: client connected from 32691[0:0]
Feb  1 19:16:36 joe acpid: 1 client rule loaded
Feb  1 19:16:48 joe acpid: client 32648[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32653[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32649[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32650[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32656[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32657[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32654[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32659[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32669[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32658[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32671[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32673[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32678[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32675[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32674[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32679[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32677[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32680[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32676[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32681[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client 32691[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client connected from 625[0:0]
Feb  1 19:16:48 joe acpid: 1 client rule loaded
Feb  1 19:16:48 joe acpid: client connected from 630[0:0]
Feb  1 19:16:48 joe acpid: 1 client rule loaded
Feb  1 19:16:48 joe acpid: client connected from 626[0:0]
Feb  1 19:16:48 joe acpid: 1 client rule loaded
Feb  1 19:16:48 joe acpid: client connected from 628[0:0]
Feb  1 19:16:48 joe acpid: 1 client rule loaded
Feb  1 19:16:48 joe acpid: client connected from 629[0:0]
Feb  1 19:16:48 joe acpid: 1 client rule loaded
Feb  1 19:16:48 joe acpid: client connected from 636[0:0]
Feb  1 19:16:48 joe acpid: 1 client rule loaded
Feb  1 19:16:48 joe acpid: client connected from 638[0:0]
Feb  1 19:16:48 joe acpid: 1 client rule loaded
Feb  1 19:16:48 joe acpid: client 628[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client connected from 641[0:0]
Feb  1 19:16:48 joe acpid: 1 client rule loaded
Feb  1 19:16:48 joe acpid: client 629[0:0] has disconnected
Feb  1 19:16:48 joe acpid: client connected from 640[0:0]
Feb  1 19:16:48 joe acpid: 1 client rule loaded
Feb  1 19:16:48 joe acpid: client connected from 643[0:0]
Feb  1 19:16:48 joe acpid: 1 client rule loaded
Feb  1 19:16:48 joe acpid: client connected from 642[0:0]
Feb  1 19:16:48 joe acpid: 1 client rule loaded
Feb  1 19:17:01 joe /USR/SBIN/CRON[1066]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb  1 19:17:03 joe acpid: client 625[0:0] has disconnected
Feb  1 19:17:03 joe acpid: client 630[0:0] has disconnected
Feb  1 19:17:03 joe acpid: client 626[0:0] has disconnected
Feb  1 19:17:03 joe acpid: client 636[0:0] has disconnected
Feb  1 19:17:03 joe acpid: client 638[0:0] has disconnected
Feb  1 19:17:03 joe acpid: client 641[0:0] has disconnected
Feb  1 19:17:03 joe acpid: client 640[0:0] has disconnected
Feb  1 19:17:03 joe acpid: client 643[0:0] has disconnected
Feb  1 19:17:03 joe acpid: client 642[0:0] has disconnected
Feb  1 19:17:03 joe acpid: client connected from 1068[0:0]
Feb  1 19:17:03 joe acpid: 1 client rule loaded
Feb  1 19:17:03 joe acpid: client 1068[0:0] has disconnected
Feb  1 19:17:03 joe acpid: client connected from 1070[0:0]
Feb  1 19:17:03 joe acpid: 1 client rule loaded
Feb  1 19:17:03 joe acpid: client 1070[0:0] has disconnected
Feb  1 19:17:03 joe acpid: client connected from 1074[0:0]
Feb  1 19:17:03 joe acpid: 1 client rule loaded
Feb  1 19:17:03 joe acpid: client 1074[0:0] has disconnected
Feb  1 19:17:03 joe acpid: client connected from 1077[0:0]
Feb  1 19:17:03 joe acpid: 1 client rule loaded
Feb  1 19:17:03 joe acpid: client 1077[0:0] has disconnected
Feb  1 19:17:03 joe acpid: client connected from 1079[0:0]
Feb  1 19:17:03 joe acpid: 1 client rule loaded
Feb  1 19:17:03 joe acpid: client 1079[0:0] has disconnected
Feb  1 19:17:03 joe acpid: client connected from 1083[0:0]
Feb  1 19:17:03 joe acpid: 1 client rule loaded
Feb  1 19:17:03 joe acpid: client 1083[0:0] has disconnected
Feb  1 19:17:03 joe acpid: client connected from 1073[0:0]
Feb  1 19:17:03 joe acpid: 1 client rule loaded
Feb  1 19:17:03 joe acpid: client 1073[0:0] has disconnected
Feb  1 19:17:03 joe acpid: client connected from 1084[0:0]
Feb  1 19:17:03 joe acpid: 1 client rule loaded
Feb  1 19:17:04 joe acpid: client 1084[0:0] has disconnected
Feb  1 19:17:04 joe acpid: client connected from 1086[0:0]
Feb  1 19:17:04 joe acpid: 1 client rule loaded
Feb  1 19:17:04 joe acpid: client 1086[0:0] has disconnected
Feb  1 19:17:04 joe acpid: client connected from 1076[0:0]
Feb  1 19:17:04 joe acpid: 1 client rule loaded
Feb  1 19:17:04 joe acpid: client 1076[0:0] has disconnected
Feb  1 19:17:04 joe acpid: client connected from 1078[0:0]
Feb  1 19:17:04 joe acpid: 1 client rule loaded
Feb  1 19:17:04 joe acpid: client 1078[0:0] has disconnected
Feb  1 19:17:04 joe acpid: client connected from 1071[0:0]
Feb  1 19:17:04 joe acpid: 1 client rule loaded
Feb  1 19:17:04 joe acpid: client 1071[0:0] has disconnected
Feb  1 19:17:04 joe acpid: client connected from 1081[0:0]
Feb  1 19:17:04 joe acpid: 1 client rule loaded
Feb  1 19:17:04 joe acpid: client 1081[0:0] has disconnected
Feb  1 19:17:04 joe acpid: client connected from 1075[0:0]
Feb  1 19:17:04 joe acpid: 1 client rule loaded
Feb  1 19:17:04 joe acpid: client 1075[0:0] has disconnected
Feb  1 19:17:04 joe acpid: client connected from 1085[0:0]
Feb  1 19:17:04 joe acpid: 1 client rule loaded
Feb  1 19:17:04 joe acpid: client 1085[0:0] has disconnected
Feb  1 19:17:04 joe acpid: client connected from 1080[0:0]
Feb  1 19:17:04 joe acpid: 1 client rule loaded
Feb  1 19:17:04 joe acpid: client 1080[0:0] has disconnected
Feb  1 19:17:04 joe acpid: client connected from 1088[0:0]
Feb  1 19:17:04 joe acpid: 1 client rule loaded
Feb  1 19:17:04 joe acpid: client 1088[0:0] has disconnected
Feb  1 19:17:04 joe acpid: client connected from 1082[0:0]
Feb  1 19:17:04 joe acpid: 1 client rule loaded
Feb  1 19:17:04 joe acpid: client 1082[0:0] has disconnected
Feb  1 19:17:04 joe acpid: client connected from 1087[0:0]
Feb  1 19:17:04 joe acpid: 1 client rule loaded
Feb  1 19:17:04 joe acpid: client 1087[0:0] has disconnected
Feb  1 19:17:04 joe acpid: client connected from 1089[0:0]
Feb  1 19:17:04 joe acpid: 1 client rule loaded
Feb  1 19:17:14 joe acpid: client 1089[0:0] has disconnected
Feb  1 19:17:14 joe acpid: client connected from 1539[0:0]
Feb  1 19:17:14 joe acpid: 1 client rule loaded
Feb  1 19:17:14 joe acpid: client connected from 1540[0:0]
Feb  1 19:17:14 joe acpid: 1 client rule loaded
Feb  1 19:17:14 joe acpid: client connected from 1542[0:0]
Feb  1 19:17:14 joe acpid: 1 client rule loaded
Feb  1 19:17:14 joe acpid: client connected from 1544[0:0]
Feb  1 19:17:14 joe acpid: 1 client rule loaded
Feb  1 19:17:14 joe acpid: client connected from 1545[0:0]
Feb  1 19:17:14 joe acpid: 1 client rule loaded
Feb  1 19:17:14 joe acpid: client connected from 1551[0:0]
Feb  1 19:17:14 joe acpid: 1 client rule loaded
Feb  1 19:17:14 joe acpid: client connected from 1550[0:0]
Feb  1 19:17:14 joe acpid: 1 client rule loaded
Feb  1 19:17:14 joe acpid: client connected from 1552[0:0]
Feb  1 19:17:14 joe acpid: 1 client rule loaded
Feb  1 19:17:14 joe acpid: client 1539[0:0] has disconnected
Feb  1 19:17:14 joe acpid: client 1540[0:0] has disconnected
Feb  1 19:17:14 joe acpid: client 1542[0:0] has disconnected
Feb  1 19:17:14 joe acpid: client 1544[0:0] has disconnected
Feb  1 19:17:14 joe acpid: client 1545[0:0] has disconnected
Feb  1 19:17:14 joe acpid: client 1551[0:0] has disconnected
Feb  1 19:17:14 joe acpid: client 1550[0:0] has disconnected
Feb  1 19:17:14 joe acpid: client 1552[0:0] has disconnected
Feb  1 19:17:14 joe acpid: client connected from 1566[0:0]
Feb  1 19:17:14 joe acpid: 1 client rule loaded
Feb  1 19:17:14 joe acpid: client connected from 1563[0:0]
Feb  1 19:17:14 joe acpid: 1 client rule loaded
Feb  1 19:17:14 joe acpid: client connected from 1562[0:0]
Feb  1 19:17:14 joe acpid: 1 client rule loaded
Feb  1 19:17:14 joe acpid: client connected from 1565[0:0]
Feb  1 19:17:14 joe acpid: 1 client rule loaded
Feb  1 19:17:14 joe acpid: client connected from 1567[0:0]
Feb  1 19:17:14 joe acpid: 1 client rule loaded
Feb  1 19:17:14 joe acpid: client connected from 1564[0:0]
Feb  1 19:17:14 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client 1566[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 1563[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 1562[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 1565[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 1567[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 1564[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client connected from 1991[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 1994[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 1990[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 1988[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2004[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2006[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 1992[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 1989[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2002[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 1995[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 1999[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2001[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2003[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2005[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client 1991[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 1994[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 1990[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 1988[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 2004[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 2006[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 1992[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 1989[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 2002[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 1995[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 1999[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 2001[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 2003[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client 2005[0:0] has disconnected
Feb  1 19:17:29 joe acpid: client connected from 2018[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2016[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2017[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2022[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2026[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2030[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2036[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2032[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2039[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2040[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2024[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2035[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2028[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2037[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2041[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2029[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2031[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2027[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2025[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2033[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:29 joe acpid: client connected from 2034[0:0]
Feb  1 19:17:29 joe acpid: 1 client rule loaded
Feb  1 19:17:41 joe acpid: client 2018[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2016[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2017[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2022[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2026[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2030[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2036[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2032[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2039[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2040[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2024[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2035[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2028[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2037[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2041[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2029[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2031[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2027[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2025[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2033[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client 2034[0:0] has disconnected
Feb  1 19:17:41 joe acpid: client connected from 2521[0:0]
Feb  1 19:17:41 joe acpid: 1 client rule loaded
Feb  1 19:17:41 joe acpid: client connected from 2517[0:0]
Feb  1 19:17:41 joe acpid: 1 client rule loaded
Feb  1 19:17:41 joe acpid: client connected from 2520[0:0]
Feb  1 19:17:41 joe acpid: 1 client rule loaded
Feb  1 19:17:41 joe acpid: client connected from 2515[0:0]
Feb  1 19:17:41 joe acpid: 1 client rule loaded
Feb  1 19:17:41 joe acpid: client connected from 2518[0:0]
Feb  1 19:17:41 joe acpid: 1 client rule loaded
Feb  1 19:17:41 joe acpid: client connected from 2514[0:0]
Feb  1 19:17:41 joe acpid: 1 client rule loaded
Feb  1 19:17:41 joe acpid: client connected from 2513[0:0]
Feb  1 19:17:41 joe acpid: 1 client rule loaded
Feb  1 19:17:41 joe acpid: client connected from 2519[0:0]
Feb  1 19:17:41 joe acpid: 1 client rule loaded
Feb  1 19:17:55 joe acpid: client 2521[0:0] has disconnected
Feb  1 19:17:55 joe acpid: client 2517[0:0] has disconnected
Feb  1 19:17:55 joe acpid: client 2520[0:0] has disconnected
Feb  1 19:17:55 joe acpid: client 2515[0:0] has disconnected
Feb  1 19:17:55 joe acpid: client 2518[0:0] has disconnected
Feb  1 19:17:55 joe acpid: client 2514[0:0] has disconnected
Feb  1 19:17:55 joe acpid: client 2513[0:0] has disconnected
Feb  1 19:17:55 joe acpid: client 2519[0:0] has disconnected
Feb  1 19:17:55 joe acpid: client connected from 2959[0:0]
Feb  1 19:17:55 joe acpid: 1 client rule loaded
Feb  1 19:17:55 joe acpid: client connected from 2958[0:0]
Feb  1 19:17:55 joe acpid: 1 client rule loaded
Feb  1 19:17:55 joe acpid: client connected from 2960[0:0]
Feb  1 19:17:55 joe acpid: 1 client rule loaded
Feb  1 19:17:55 joe acpid: client 2959[0:0] has disconnected
Feb  1 19:17:55 joe acpid: client connected from 2966[0:0]
Feb  1 19:17:55 joe acpid: 1 client rule loaded
Feb  1 19:17:55 joe acpid: client 2960[0:0] has disconnected
Feb  1 19:17:55 joe acpid: client connected from 2965[0:0]
Feb  1 19:17:55 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client 2958[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client 2966[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client 2965[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client connected from 3417[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client connected from 3416[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client 3417[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client 3416[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client connected from 3422[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client 3422[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client connected from 3437[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client 3437[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client connected from 3420[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client 3420[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client connected from 3419[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client 3419[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client connected from 3415[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client 3415[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client connected from 3452[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client 3452[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client connected from 3445[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client 3445[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client connected from 3426[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client 3426[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client connected from 3443[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client 3443[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client connected from 3435[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client 3435[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client connected from 3446[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client 3446[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client connected from 3432[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client 3432[0:0] has disconnected
Feb  1 19:18:13 joe acpid: client connected from 3439[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client connected from 3448[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client connected from 3436[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client connected from 3449[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client connected from 3444[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client connected from 3414[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client connected from 3451[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client connected from 3418[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client connected from 3455[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client connected from 3454[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:13 joe acpid: client connected from 3413[0:0]
Feb  1 19:18:13 joe acpid: 1 client rule loaded
Feb  1 19:18:22 joe acpid: client 3439[0:0] has disconnected
Feb  1 19:18:22 joe acpid: client 3448[0:0] has disconnected
Feb  1 19:18:22 joe acpid: client 3436[0:0] has disconnected
Feb  1 19:18:22 joe acpid: client 3449[0:0] has disconnected
Feb  1 19:18:22 joe acpid: client 3444[0:0] has disconnected
Feb  1 19:18:22 joe acpid: client 3414[0:0] has disconnected
Feb  1 19:18:22 joe acpid: client 3451[0:0] has disconnected
Feb  1 19:18:22 joe acpid: client 3418[0:0] has disconnected
Feb  1 19:18:22 joe acpid: client 3455[0:0] has disconnected
Feb  1 19:18:22 joe acpid: client 3454[0:0] has disconnected
Feb  1 19:18:22 joe acpid: client 3413[0:0] has disconnected
Feb  1 19:18:22 joe acpid: client connected from 3924[0:0]
Feb  1 19:18:22 joe acpid: 1 client rule loaded
Feb  1 19:18:22 joe acpid: client connected from 3933[0:0]
Feb  1 19:18:22 joe acpid: 1 client rule loaded
Feb  1 19:18:22 joe acpid: client connected from 3927[0:0]
Feb  1 19:18:22 joe acpid: 1 client rule loaded
Feb  1 19:18:22 joe acpid: client connected from 3936[0:0]
Feb  1 19:18:22 joe acpid: 1 client rule loaded
Feb  1 19:18:22 joe acpid: client connected from 3929[0:0]
Feb  1 19:18:22 joe acpid: 1 client rule loaded
Feb  1 19:18:22 joe acpid: client connected from 3930[0:0]
Feb  1 19:18:22 joe acpid: 1 client rule loaded
Feb  1 19:18:22 joe acpid: client connected from 3926[0:0]
Feb  1 19:18:22 joe acpid: 1 client rule loaded
Feb  1 19:18:22 joe acpid: client connected from 3937[0:0]
Feb  1 19:18:22 joe acpid: 1 client rule loaded
Feb  1 19:18:22 joe acpid: client connected from 3932[0:0]
Feb  1 19:18:22 joe acpid: 1 client rule loaded
Feb  1 19:18:22 joe acpid: client connected from 3931[0:0]
Feb  1 19:18:22 joe acpid: 1 client rule loaded
Feb  1 19:18:22 joe acpid: client connected from 3934[0:0]
Feb  1 19:18:22 joe acpid: 1 client rule loaded
Feb  1 19:18:22 joe acpid: client connected from 3925[0:0]
Feb  1 19:18:22 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client 3924[0:0] has disconnected
Feb  1 19:18:35 joe acpid: client 3933[0:0] has disconnected
Feb  1 19:18:35 joe acpid: client 3927[0:0] has disconnected
Feb  1 19:18:35 joe acpid: client 3936[0:0] has disconnected
Feb  1 19:18:35 joe acpid: client 3929[0:0] has disconnected
Feb  1 19:18:35 joe acpid: client 3930[0:0] has disconnected
Feb  1 19:18:35 joe acpid: client 3926[0:0] has disconnected
Feb  1 19:18:35 joe acpid: client 3937[0:0] has disconnected
Feb  1 19:18:35 joe acpid: client 3932[0:0] has disconnected
Feb  1 19:18:35 joe acpid: client 3931[0:0] has disconnected
Feb  1 19:18:35 joe acpid: client 3934[0:0] has disconnected
Feb  1 19:18:35 joe acpid: client 3925[0:0] has disconnected
Feb  1 19:18:35 joe acpid: client connected from 4380[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4383[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4381[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4379[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4389[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4385[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4388[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4391[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4378[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4400[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4402[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4397[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4408[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4409[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4396[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4401[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4403[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:35 joe acpid: client connected from 4398[0:0]
Feb  1 19:18:35 joe acpid: 1 client rule loaded
Feb  1 19:18:36 joe acpid: client connected from 4406[0:0]
Feb  1 19:18:36 joe acpid: 1 client rule loaded
Feb  1 19:18:36 joe acpid: client connected from 4410[0:0]
Feb  1 19:18:36 joe acpid: 1 client rule loaded
Feb  1 19:18:36 joe acpid: client connected from 4399[0:0]
Feb  1 19:18:36 joe acpid: 1 client rule loaded
Feb  1 19:18:36 joe acpid: client 4380[0:0] has disconnected
Feb  1 19:18:36 joe acpid: client connected from 4405[0:0]
Feb  1 19:18:36 joe acpid: 1 client rule loaded
Feb  1 19:18:50 joe acpid: client 4383[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4381[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4379[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4389[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4385[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4388[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4391[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4378[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4400[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4402[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4397[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4408[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4409[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4396[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4401[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4403[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4398[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4406[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4410[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4399[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client 4405[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client connected from 4832[0:0]
Feb  1 19:18:50 joe acpid: 1 client rule loaded
Feb  1 19:18:50 joe acpid: client 4832[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client connected from 4830[0:0]
Feb  1 19:18:50 joe acpid: 1 client rule loaded
Feb  1 19:18:50 joe acpid: client 4830[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client connected from 4834[0:0]
Feb  1 19:18:50 joe acpid: 1 client rule loaded
Feb  1 19:18:50 joe acpid: client 4834[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client connected from 4837[0:0]
Feb  1 19:18:50 joe acpid: 1 client rule loaded
Feb  1 19:18:50 joe acpid: client 4837[0:0] has disconnected
Feb  1 19:18:50 joe acpid: client connected from 4840[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client 4840[0:0] has disconnected
Feb  1 19:18:51 joe acpid: client connected from 4831[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client 4831[0:0] has disconnected
Feb  1 19:18:51 joe acpid: client connected from 4841[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client 4841[0:0] has disconnected
Feb  1 19:18:51 joe acpid: client connected from 4842[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client 4842[0:0] has disconnected
Feb  1 19:18:51 joe acpid: client connected from 4845[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client 4845[0:0] has disconnected
Feb  1 19:18:51 joe acpid: client connected from 4843[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client 4843[0:0] has disconnected
Feb  1 19:18:51 joe acpid: client connected from 4835[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client 4835[0:0] has disconnected
Feb  1 19:18:51 joe acpid: client connected from 4855[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4853[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4857[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4854[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4867[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4872[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4865[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4869[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4859[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4873[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4875[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4868[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4866[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4856[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4879[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4870[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4874[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4877[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4876[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:18:51 joe acpid: client connected from 4871[0:0]
Feb  1 19:18:51 joe acpid: 1 client rule loaded
Feb  1 19:19:01 joe acpid: client 4855[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4853[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4857[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4854[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4867[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4872[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4865[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4869[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4859[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4873[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4875[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4868[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4866[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4856[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4879[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4870[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4874[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4877[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4876[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 4871[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client connected from 5262[0:0]
Feb  1 19:19:01 joe acpid: 1 client rule loaded
Feb  1 19:19:01 joe acpid: client connected from 5265[0:0]
Feb  1 19:19:01 joe acpid: 1 client rule loaded
Feb  1 19:19:01 joe acpid: client connected from 5263[0:0]
Feb  1 19:19:01 joe acpid: 1 client rule loaded
Feb  1 19:19:01 joe acpid: client connected from 5270[0:0]
Feb  1 19:19:01 joe acpid: 1 client rule loaded
Feb  1 19:19:01 joe acpid: client connected from 5268[0:0]
Feb  1 19:19:01 joe acpid: 1 client rule loaded
Feb  1 19:19:01 joe acpid: client connected from 5273[0:0]
Feb  1 19:19:01 joe acpid: 1 client rule loaded
Feb  1 19:19:01 joe acpid: client connected from 5267[0:0]
Feb  1 19:19:01 joe acpid: 1 client rule loaded
Feb  1 19:19:01 joe acpid: client connected from 5266[0:0]
Feb  1 19:19:01 joe acpid: 1 client rule loaded
Feb  1 19:19:01 joe acpid: client connected from 5264[0:0]
Feb  1 19:19:01 joe acpid: 1 client rule loaded
Feb  1 19:19:01 joe acpid: client connected from 5275[0:0]
Feb  1 19:19:01 joe acpid: 1 client rule loaded
Feb  1 19:19:01 joe acpid: client connected from 5271[0:0]
Feb  1 19:19:01 joe acpid: 1 client rule loaded
Feb  1 19:19:01 joe acpid: client 5262[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 5265[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 5263[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client 5264[0:0] has disconnected
Feb  1 19:19:01 joe acpid: client connected from 5285[0:0]
Feb  1 19:19:01 joe acpid: 1 client rule loaded
Feb  1 19:19:01 joe acpid: client connected from 5286[0:0]
Feb  1 19:19:01 joe acpid: 1 client rule loaded
Feb  1 19:19:01 joe acpid: client connected from 5287[0:0]
Feb  1 19:19:01 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client 5270[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client 5268[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client 5273[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client 5267[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client 5266[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client 5275[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client 5271[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client 5285[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client 5286[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client 5287[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client connected from 5696[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client 5696[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client connected from 5702[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client 5702[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client connected from 5698[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client 5698[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client connected from 5707[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client 5707[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client connected from 5700[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client 5700[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client connected from 5708[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client 5708[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client connected from 5704[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client 5704[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client connected from 5706[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client 5706[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client connected from 5697[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client 5697[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client connected from 5705[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client 5705[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client connected from 5699[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client 5699[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client connected from 5703[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client 5703[0:0] has disconnected
Feb  1 19:19:18 joe acpid: client connected from 5721[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client connected from 5727[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client connected from 5728[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client connected from 5722[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client connected from 5726[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client connected from 5729[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client connected from 5723[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:18 joe acpid: client connected from 5724[0:0]
Feb  1 19:19:18 joe acpid: 1 client rule loaded
Feb  1 19:19:29 joe acpid: client 5721[0:0] has disconnected
Feb  1 19:19:29 joe acpid: client 5727[0:0] has disconnected
Feb  1 19:19:29 joe acpid: client 5728[0:0] has disconnected
Feb  1 19:19:29 joe acpid: client 5722[0:0] has disconnected
Feb  1 19:19:29 joe acpid: client 5726[0:0] has disconnected
Feb  1 19:19:29 joe acpid: client 5729[0:0] has disconnected
Feb  1 19:19:29 joe acpid: client 5723[0:0] has disconnected
Feb  1 19:19:29 joe acpid: client 5724[0:0] has disconnected
Feb  1 19:19:29 joe acpid: client connected from 6152[0:0]
Feb  1 19:19:29 joe acpid: 1 client rule loaded
Feb  1 19:19:29 joe acpid: client connected from 6148[0:0]
Feb  1 19:19:29 joe acpid: 1 client rule loaded
Feb  1 19:19:29 joe acpid: client connected from 6156[0:0]
Feb  1 19:19:29 joe acpid: 1 client rule loaded
Feb  1 19:19:29 joe acpid: client connected from 6139[0:0]
Feb  1 19:19:29 joe acpid: 1 client rule loaded
Feb  1 19:19:29 joe acpid: client connected from 6143[0:0]
Feb  1 19:19:29 joe acpid: 1 client rule loaded
Feb  1 19:19:29 joe acpid: client connected from 6140[0:0]
Feb  1 19:19:29 joe acpid: 1 client rule loaded
Feb  1 19:19:29 joe acpid: client connected from 6138[0:0]
Feb  1 19:19:29 joe acpid: 1 client rule loaded
Feb  1 19:19:29 joe acpid: client connected from 6137[0:0]
Feb  1 19:19:29 joe acpid: 1 client rule loaded
Feb  1 19:19:29 joe acpid: client connected from 6146[0:0]
Feb  1 19:19:29 joe acpid: 1 client rule loaded
Feb  1 19:19:29 joe acpid: client connected from 6159[0:0]
Feb  1 19:19:29 joe acpid: 1 client rule loaded
Feb  1 19:19:29 joe acpid: client connected from 6150[0:0]
Feb  1 19:19:29 joe acpid: 1 client rule loaded
Feb  1 19:19:29 joe acpid: client connected from 6162[0:0]
Feb  1 19:19:29 joe acpid: 1 client rule loaded
Feb  1 19:19:29 joe acpid: client connected from 6158[0:0]
Feb  1 19:19:29 joe acpid: 1 client rule loaded
Feb  1 19:19:29 joe acpid: client connected from 6153[0:0]
Feb  1 19:19:29 joe acpid: 1 client rule loaded
Feb  1 19:19:29 joe acpid: client connected from 6157[0:0]
Feb  1 19:19:29 joe acpid: 1 client rule loaded
Feb  1 19:19:44 joe acpid: client 6152[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client 6148[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client 6156[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client 6139[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client 6143[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client 6140[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client 6138[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client 6137[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client 6146[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client 6159[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client 6150[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client 6162[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client 6158[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client 6153[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client 6157[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client connected from 6584[0:0]
Feb  1 19:19:44 joe acpid: 1 client rule loaded
Feb  1 19:19:44 joe acpid: client 6584[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client connected from 6586[0:0]
Feb  1 19:19:44 joe acpid: 1 client rule loaded
Feb  1 19:19:44 joe acpid: client 6586[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client connected from 6591[0:0]
Feb  1 19:19:44 joe acpid: 1 client rule loaded
Feb  1 19:19:44 joe acpid: client 6591[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client connected from 6594[0:0]
Feb  1 19:19:44 joe acpid: 1 client rule loaded
Feb  1 19:19:44 joe acpid: client 6594[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client connected from 6587[0:0]
Feb  1 19:19:44 joe acpid: 1 client rule loaded
Feb  1 19:19:44 joe acpid: client 6587[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client connected from 6589[0:0]
Feb  1 19:19:44 joe acpid: 1 client rule loaded
Feb  1 19:19:44 joe acpid: client 6589[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client connected from 6592[0:0]
Feb  1 19:19:44 joe acpid: 1 client rule loaded
Feb  1 19:19:44 joe acpid: client 6592[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client connected from 6590[0:0]
Feb  1 19:19:44 joe acpid: 1 client rule loaded
Feb  1 19:19:44 joe acpid: client 6590[0:0] has disconnected
Feb  1 19:19:44 joe acpid: client connected from 6600[0:0]
Feb  1 19:19:44 joe acpid: 1 client rule loaded
Feb  1 19:19:57 joe acpid: client 6600[0:0] has disconnected
Feb  1 19:19:57 joe acpid: client connected from 7028[0:0]
Feb  1 19:19:57 joe acpid: 1 client rule loaded
Feb  1 19:19:57 joe acpid: client connected from 7029[0:0]
Feb  1 19:19:57 joe acpid: 1 client rule loaded
Feb  1 19:19:57 joe acpid: client connected from 7032[0:0]
Feb  1 19:19:57 joe acpid: 1 client rule loaded
Feb  1 19:19:57 joe acpid: client connected from 7031[0:0]
Feb  1 19:19:57 joe acpid: 1 client rule loaded
Feb  1 19:19:57 joe acpid: client 7028[0:0] has disconnected
Feb  1 19:19:57 joe acpid: client 7029[0:0] has disconnected
Feb  1 19:19:57 joe acpid: client 7032[0:0] has disconnected
Feb  1 19:19:57 joe acpid: client 7031[0:0] has disconnected
Feb  1 19:19:57 joe acpid: client connected from 7037[0:0]
Feb  1 19:19:57 joe acpid: 1 client rule loaded
Feb  1 19:19:57 joe acpid: client connected from 7036[0:0]
Feb  1 19:19:57 joe acpid: 1 client rule loaded
Feb  1 19:19:57 joe acpid: client connected from 7038[0:0]
Feb  1 19:19:57 joe acpid: 1 client rule loaded
Feb  1 19:20:12 joe acpid: client 7037[0:0] has disconnected
Feb  1 19:20:12 joe acpid: client 7036[0:0] has disconnected
Feb  1 19:20:12 joe acpid: client 7038[0:0] has disconnected
Feb  1 19:20:12 joe acpid: client connected from 7479[0:0]
Feb  1 19:20:12 joe acpid: 1 client rule loaded
Feb  1 19:20:12 joe acpid: client connected from 7480[0:0]
Feb  1 19:20:12 joe acpid: 1 client rule loaded
Feb  1 19:20:12 joe acpid: client connected from 7481[0:0]
Feb  1 19:20:12 joe acpid: 1 client rule loaded
Feb  1 19:20:12 joe acpid: client connected from 7483[0:0]
Feb  1 19:20:12 joe acpid: 1 client rule loaded
Feb  1 19:20:12 joe acpid: client 7480[0:0] has disconnected
Feb  1 19:20:12 joe acpid: client 7481[0:0] has disconnected
Feb  1 19:20:12 joe acpid: client 7483[0:0] has disconnected
Feb  1 19:20:12 joe acpid: client connected from 7482[0:0]
Feb  1 19:20:12 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7479[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client 7482[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7930[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client connected from 7931[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client connected from 7938[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7930[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client 7931[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client 7938[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7946[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7946[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7939[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7939[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7935[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7935[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7941[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7941[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7948[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7948[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7929[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7929[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7942[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7942[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7945[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7945[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7928[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7928[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7936[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7936[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7947[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7947[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7937[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7937[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7943[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7943[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7932[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7932[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7966[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client 7966[0:0] has disconnected
Feb  1 19:20:29 joe acpid: client connected from 7968[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client connected from 7976[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client connected from 7965[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client connected from 7978[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client connected from 7969[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client connected from 7970[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client connected from 7981[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client connected from 7971[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client connected from 7980[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client connected from 7977[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:29 joe acpid: client connected from 7979[0:0]
Feb  1 19:20:29 joe acpid: 1 client rule loaded
Feb  1 19:20:41 joe acpid: client 7968[0:0] has disconnected
Feb  1 19:20:41 joe acpid: client 7976[0:0] has disconnected
Feb  1 19:20:41 joe acpid: client 7965[0:0] has disconnected
Feb  1 19:20:41 joe acpid: client 7978[0:0] has disconnected
Feb  1 19:20:41 joe acpid: client 7969[0:0] has disconnected
Feb  1 19:20:41 joe acpid: client 7970[0:0] has disconnected
Feb  1 19:20:41 joe acpid: client 7981[0:0] has disconnected
Feb  1 19:20:41 joe acpid: client 7971[0:0] has disconnected
Feb  1 19:20:41 joe acpid: client 7980[0:0] has disconnected
Feb  1 19:20:41 joe acpid: client 7977[0:0] has disconnected
Feb  1 19:20:41 joe acpid: client 7979[0:0] has disconnected
Feb  1 19:20:41 joe acpid: client connected from 8394[0:0]
Feb  1 19:20:41 joe acpid: 1 client rule loaded
Feb  1 19:20:41 joe acpid: client connected from 8396[0:0]
Feb  1 19:20:41 joe acpid: 1 client rule loaded
Feb  1 19:20:41 joe acpid: client connected from 8395[0:0]
Feb  1 19:20:41 joe acpid: 1 client rule loaded
Feb  1 19:20:41 joe acpid: client connected from 8406[0:0]
Feb  1 19:20:41 joe acpid: 1 client rule loaded
Feb  1 19:20:41 joe acpid: client connected from 8402[0:0]
Feb  1 19:20:41 joe acpid: 1 client rule loaded
Feb  1 19:20:41 joe acpid: client connected from 8400[0:0]
Feb  1 19:20:41 joe acpid: 1 client rule loaded
Feb  1 19:20:41 joe acpid: client connected from 8408[0:0]
Feb  1 19:20:41 joe acpid: 1 client rule loaded
Feb  1 19:20:41 joe acpid: client connected from 8404[0:0]
Feb  1 19:20:41 joe acpid: 1 client rule loaded
Feb  1 19:20:41 joe acpid: client connected from 8401[0:0]
Feb  1 19:20:41 joe acpid: 1 client rule loaded
Feb  1 19:20:41 joe acpid: client connected from 8409[0:0]
Feb  1 19:20:41 joe acpid: 1 client rule loaded
Feb  1 19:20:41 joe acpid: client connected from 8403[0:0]
Feb  1 19:20:41 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client 8394[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8396[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8395[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8406[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8402[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8400[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8408[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8404[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8401[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8409[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8403[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client connected from 8835[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8834[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8830[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8839[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8833[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8838[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8843[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8831[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8832[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8840[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8841[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client 8835[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8834[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8830[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8839[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8833[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8838[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8843[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8831[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8832[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8840[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client 8841[0:0] has disconnected
Feb  1 19:20:54 joe acpid: client connected from 8857[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8859[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8855[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8854[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8862[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8860[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8858[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8861[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8853[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8856[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:20:54 joe acpid: client connected from 8863[0:0]
Feb  1 19:20:54 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client 8857[0:0] has disconnected
Feb  1 19:21:08 joe acpid: client 8859[0:0] has disconnected
Feb  1 19:21:08 joe acpid: client 8855[0:0] has disconnected
Feb  1 19:21:08 joe acpid: client 8854[0:0] has disconnected
Feb  1 19:21:08 joe acpid: client 8862[0:0] has disconnected
Feb  1 19:21:08 joe acpid: client 8860[0:0] has disconnected
Feb  1 19:21:08 joe acpid: client 8858[0:0] has disconnected
Feb  1 19:21:08 joe acpid: client 8861[0:0] has disconnected
Feb  1 19:21:08 joe acpid: client 8853[0:0] has disconnected
Feb  1 19:21:08 joe acpid: client 8856[0:0] has disconnected
Feb  1 19:21:08 joe acpid: client 8863[0:0] has disconnected
Feb  1 19:21:08 joe acpid: client connected from 9309[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9298[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9302[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9291[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9308[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9304[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9300[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9290[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9299[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9307[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9296[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9301[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9294[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9305[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9292[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9293[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9303[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9297[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9295[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:08 joe acpid: client connected from 9310[0:0]
Feb  1 19:21:08 joe acpid: 1 client rule loaded
Feb  1 19:21:09 joe acpid: client 9309[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9298[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9302[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9291[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9308[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9304[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9300[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9290[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9299[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9307[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9296[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9301[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9294[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9305[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9292[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9293[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9303[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9297[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9295[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client 9310[0:0] has disconnected
Feb  1 19:21:09 joe acpid: client connected from 9332[0:0]
Feb  1 19:21:09 joe acpid: 1 client rule loaded
Feb  1 19:21:09 joe acpid: client connected from 9331[0:0]
Feb  1 19:21:09 joe acpid: 1 client rule loaded
Feb  1 19:21:09 joe acpid: client connected from 9336[0:0]
Feb  1 19:21:09 joe acpid: 1 client rule loaded
Feb  1 19:21:09 joe acpid: client connected from 9333[0:0]
Feb  1 19:21:09 joe acpid: 1 client rule loaded
Feb  1 19:21:09 joe acpid: client connected from 9346[0:0]
Feb  1 19:21:09 joe acpid: 1 client rule loaded
Feb  1 19:21:09 joe acpid: client connected from 9341[0:0]
Feb  1 19:21:09 joe acpid: 1 client rule loaded
Feb  1 19:21:09 joe acpid: client connected from 9337[0:0]
Feb  1 19:21:09 joe acpid: 1 client rule loaded
Feb  1 19:21:09 joe acpid: client connected from 9344[0:0]
Feb  1 19:21:09 joe acpid: 1 client rule loaded
Feb  1 19:21:09 joe acpid: client connected from 9343[0:0]
Feb  1 19:21:09 joe acpid: 1 client rule loaded
Feb  1 19:21:09 joe acpid: client connected from 9345[0:0]
Feb  1 19:21:09 joe acpid: 1 client rule loaded
Feb  1 19:21:09 joe acpid: client connected from 9338[0:0]
Feb  1 19:21:09 joe acpid: 1 client rule loaded
Feb  1 19:21:09 joe acpid: client connected from 9347[0:0]
Feb  1 19:21:09 joe acpid: 1 client rule loaded
Feb  1 19:21:09 joe acpid: client connected from 9339[0:0]
Feb  1 19:21:09 joe acpid: 1 client rule loaded
Feb  1 19:21:09 joe acpid: client connected from 9340[0:0]
Feb  1 19:21:09 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client 9332[0:0] has disconnected
Feb  1 19:21:22 joe acpid: client 9331[0:0] has disconnected
Feb  1 19:21:22 joe acpid: client 9336[0:0] has disconnected
Feb  1 19:21:22 joe acpid: client 9333[0:0] has disconnected
Feb  1 19:21:22 joe acpid: client 9346[0:0] has disconnected
Feb  1 19:21:22 joe acpid: client 9341[0:0] has disconnected
Feb  1 19:21:22 joe acpid: client 9337[0:0] has disconnected
Feb  1 19:21:22 joe acpid: client 9344[0:0] has disconnected
Feb  1 19:21:22 joe acpid: client 9343[0:0] has disconnected
Feb  1 19:21:22 joe acpid: client 9345[0:0] has disconnected
Feb  1 19:21:22 joe acpid: client 9338[0:0] has disconnected
Feb  1 19:21:22 joe acpid: client 9347[0:0] has disconnected
Feb  1 19:21:22 joe acpid: client 9339[0:0] has disconnected
Feb  1 19:21:22 joe acpid: client 9340[0:0] has disconnected
Feb  1 19:21:22 joe acpid: client connected from 9726[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client connected from 9730[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client connected from 9725[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client connected from 9724[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client connected from 9729[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client connected from 9727[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client connected from 9738[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client connected from 9741[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client connected from 9739[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client connected from 9737[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client connected from 9743[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client connected from 9742[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client connected from 9745[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client connected from 9740[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client connected from 9746[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client connected from 9747[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:22 joe acpid: client connected from 9744[0:0]
Feb  1 19:21:22 joe acpid: 1 client rule loaded
Feb  1 19:21:37 joe acpid: client 9726[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 9730[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 9725[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 9724[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 9729[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 9727[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 9738[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 9741[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 9739[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 9737[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 9743[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 9742[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 9745[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 9740[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 9746[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 9747[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 9744[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client connected from 10180[0:0]
Feb  1 19:21:37 joe acpid: 1 client rule loaded
Feb  1 19:21:37 joe acpid: client connected from 10178[0:0]
Feb  1 19:21:37 joe acpid: 1 client rule loaded
Feb  1 19:21:37 joe acpid: client connected from 10179[0:0]
Feb  1 19:21:37 joe acpid: 1 client rule loaded
Feb  1 19:21:37 joe acpid: client 10180[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 10178[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client 10179[0:0] has disconnected
Feb  1 19:21:37 joe acpid: client connected from 10187[0:0]
Feb  1 19:21:37 joe acpid: 1 client rule loaded
Feb  1 19:21:37 joe acpid: client connected from 10188[0:0]
Feb  1 19:21:37 joe acpid: 1 client rule loaded
Feb  1 19:21:37 joe acpid: client connected from 10189[0:0]
Feb  1 19:21:37 joe acpid: 1 client rule loaded
Feb  1 19:21:37 joe acpid: client connected from 10186[0:0]
Feb  1 19:21:37 joe acpid: 1 client rule loaded
Feb  1 19:21:38 joe acpid: client connected from 10192[0:0]
Feb  1 19:21:38 joe acpid: 1 client rule loaded
Feb  1 19:21:38 joe acpid: client connected from 10197[0:0]
Feb  1 19:21:38 joe acpid: 1 client rule loaded
Feb  1 19:21:38 joe acpid: client connected from 10195[0:0]
Feb  1 19:21:38 joe acpid: 1 client rule loaded
Feb  1 19:21:38 joe acpid: client connected from 10184[0:0]
Feb  1 19:21:38 joe acpid: 1 client rule loaded
Feb  1 19:21:38 joe acpid: client connected from 10203[0:0]
Feb  1 19:21:38 joe acpid: 1 client rule loaded
Feb  1 19:21:38 joe acpid: client connected from 10202[0:0]
Feb  1 19:21:38 joe acpid: 1 client rule loaded
Feb  1 19:21:38 joe acpid: client connected from 10198[0:0]
Feb  1 19:21:38 joe acpid: 1 client rule loaded
Feb  1 19:21:38 joe acpid: client connected from 10185[0:0]
Feb  1 19:21:38 joe acpid: 1 client rule loaded
Feb  1 19:21:38 joe acpid: client connected from 10194[0:0]
Feb  1 19:21:38 joe acpid: 1 client rule loaded
Feb  1 19:21:38 joe acpid: client connected from 10200[0:0]
Feb  1 19:21:38 joe acpid: 1 client rule loaded
Feb  1 19:21:38 joe acpid: client connected from 10199[0:0]
Feb  1 19:21:38 joe acpid: 1 client rule loaded
Feb  1 19:21:52 joe acpid: client 10187[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client 10188[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client 10189[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client 10186[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client 10192[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client 10197[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client 10195[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client 10184[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client 10203[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client 10202[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client 10198[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client 10185[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client 10194[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client 10200[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client 10199[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client connected from 10624[0:0]
Feb  1 19:21:52 joe acpid: 1 client rule loaded
Feb  1 19:21:52 joe acpid: client 10624[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client connected from 10633[0:0]
Feb  1 19:21:52 joe acpid: 1 client rule loaded
Feb  1 19:21:52 joe acpid: client 10633[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client connected from 10634[0:0]
Feb  1 19:21:52 joe acpid: 1 client rule loaded
Feb  1 19:21:52 joe acpid: client 10634[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client connected from 10627[0:0]
Feb  1 19:21:52 joe acpid: 1 client rule loaded
Feb  1 19:21:52 joe acpid: client 10627[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client connected from 10630[0:0]
Feb  1 19:21:52 joe acpid: 1 client rule loaded
Feb  1 19:21:52 joe acpid: client 10630[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client connected from 10629[0:0]
Feb  1 19:21:52 joe acpid: 1 client rule loaded
Feb  1 19:21:52 joe acpid: client 10629[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client connected from 10626[0:0]
Feb  1 19:21:52 joe acpid: 1 client rule loaded
Feb  1 19:21:52 joe acpid: client 10626[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client connected from 10636[0:0]
Feb  1 19:21:52 joe acpid: 1 client rule loaded
Feb  1 19:21:52 joe acpid: client 10636[0:0] has disconnected
Feb  1 19:21:52 joe acpid: client connected from 10631[0:0]
Feb  1 19:21:52 joe acpid: 1 client rule loaded
Feb  1 19:22:08 joe acpid: client 10631[0:0] has disconnected
Feb  1 19:22:08 joe acpid: client connected from 11079[0:0]
Feb  1 19:22:08 joe acpid: 1 client rule loaded
Feb  1 19:22:08 joe acpid: client connected from 11082[0:0]
Feb  1 19:22:08 joe acpid: 1 client rule loaded
Feb  1 19:22:08 joe acpid: client connected from 11081[0:0]
Feb  1 19:22:08 joe acpid: 1 client rule loaded
Feb  1 19:22:08 joe acpid: client 11079[0:0] has disconnected
Feb  1 19:22:08 joe acpid: client 11082[0:0] has disconnected
Feb  1 19:22:08 joe acpid: client 11081[0:0] has disconnected
Feb  1 19:22:08 joe acpid: client connected from 11085[0:0]
Feb  1 19:22:08 joe acpid: 1 client rule loaded
Feb  1 19:22:08 joe acpid: client 11085[0:0] has disconnected
Feb  1 19:22:08 joe acpid: client connected from 11080[0:0]
Feb  1 19:22:08 joe acpid: 1 client rule loaded
Feb  1 19:22:08 joe acpid: client 11080[0:0] has disconnected
Feb  1 19:22:08 joe acpid: client connected from 11083[0:0]
Feb  1 19:22:08 joe acpid: 1 client rule loaded
Feb  1 19:22:08 joe acpid: client 11083[0:0] has disconnected
Feb  1 19:22:08 joe acpid: client connected from 11084[0:0]
Feb  1 19:22:08 joe acpid: 1 client rule loaded
Feb  1 19:22:23 joe acpid: client 11084[0:0] has disconnected
Feb  1 19:22:23 joe acpid: client connected from 11529[0:0]
Feb  1 19:22:23 joe acpid: 1 client rule loaded
Feb  1 19:22:23 joe acpid: client connected from 11528[0:0]
Feb  1 19:22:23 joe acpid: 1 client rule loaded
Feb  1 19:22:23 joe acpid: client connected from 11526[0:0]
Feb  1 19:22:23 joe acpid: 1 client rule loaded
Feb  1 19:22:23 joe acpid: client 11529[0:0] has disconnected
Feb  1 19:22:23 joe acpid: client 11528[0:0] has disconnected
Feb  1 19:22:23 joe acpid: client 11526[0:0] has disconnected
Feb  1 19:22:23 joe acpid: client connected from 11524[0:0]
Feb  1 19:22:23 joe acpid: 1 client rule loaded
Feb  1 19:22:23 joe acpid: client 11524[0:0] has disconnected
Feb  1 19:22:23 joe acpid: client connected from 11527[0:0]
Feb  1 19:22:23 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client 11527[0:0] has disconnected
Feb  1 19:22:36 joe acpid: client connected from 11975[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 11977[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 11976[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 11978[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 11980[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 11983[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 11988[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 11989[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 11999[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 11991[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 11993[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 11994[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 11995[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client 11976[0:0] has disconnected
Feb  1 19:22:36 joe acpid: client connected from 11996[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 11992[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 11998[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client 11975[0:0] has disconnected
Feb  1 19:22:36 joe acpid: client connected from 11997[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 11990[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 11987[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client 11977[0:0] has disconnected
Feb  1 19:22:36 joe acpid: client 11978[0:0] has disconnected
Feb  1 19:22:36 joe acpid: client 11980[0:0] has disconnected
Feb  1 19:22:36 joe acpid: client 11983[0:0] has disconnected
Feb  1 19:22:36 joe acpid: client connected from 12014[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 12017[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 12015[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:36 joe acpid: client connected from 12018[0:0]
Feb  1 19:22:36 joe acpid: 1 client rule loaded
Feb  1 19:22:37 joe acpid: client connected from 12021[0:0]
Feb  1 19:22:37 joe acpid: 1 client rule loaded
Feb  1 19:22:37 joe acpid: client connected from 12016[0:0]
Feb  1 19:22:37 joe acpid: 1 client rule loaded
Feb  1 19:22:51 joe acpid: client 11988[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 11989[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 11999[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 11991[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 11993[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 11994[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 11995[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 11996[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 11992[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 11998[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 11997[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 11990[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 11987[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 12014[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 12017[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 12015[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 12018[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 12021[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 12016[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client connected from 12441[0:0]
Feb  1 19:22:51 joe acpid: 1 client rule loaded
Feb  1 19:22:51 joe acpid: client connected from 12443[0:0]
Feb  1 19:22:51 joe acpid: 1 client rule loaded
Feb  1 19:22:51 joe acpid: client connected from 12442[0:0]
Feb  1 19:22:51 joe acpid: 1 client rule loaded
Feb  1 19:22:51 joe acpid: client connected from 12444[0:0]
Feb  1 19:22:51 joe acpid: 1 client rule loaded
Feb  1 19:22:51 joe acpid: client 12441[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 12443[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 12442[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client 12444[0:0] has disconnected
Feb  1 19:22:51 joe acpid: client connected from 12451[0:0]
Feb  1 19:22:51 joe acpid: 1 client rule loaded
Feb  1 19:22:51 joe acpid: client connected from 12454[0:0]
Feb  1 19:22:51 joe acpid: 1 client rule loaded
Feb  1 19:22:51 joe acpid: client connected from 12449[0:0]
Feb  1 19:22:51 joe acpid: 1 client rule loaded
Feb  1 19:22:51 joe acpid: client connected from 12450[0:0]
Feb  1 19:22:51 joe acpid: 1 client rule loaded
Feb  1 19:22:51 joe acpid: client connected from 12453[0:0]
Feb  1 19:22:51 joe acpid: 1 client rule loaded
Feb  1 19:22:51 joe acpid: client connected from 12455[0:0]
Feb  1 19:22:51 joe acpid: 1 client rule loaded
Feb  1 19:22:51 joe acpid: client connected from 12459[0:0]
Feb  1 19:22:51 joe acpid: 1 client rule loaded
Feb  1 19:22:51 joe acpid: client connected from 12458[0:0]
Feb  1 19:22:51 joe acpid: 1 client rule loaded
Feb  1 19:22:51 joe acpid: client connected from 12452[0:0]
Feb  1 19:22:51 joe acpid: 1 client rule loaded
Feb  1 19:22:51 joe acpid: client connected from 12461[0:0]
Feb  1 19:22:51 joe acpid: 1 client rule loaded
Feb  1 19:22:51 joe acpid: client connected from 12456[0:0]
Feb  1 19:22:51 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client 12451[0:0] has disconnected
Feb  1 19:23:06 joe acpid: client 12454[0:0] has disconnected
Feb  1 19:23:06 joe acpid: client 12449[0:0] has disconnected
Feb  1 19:23:06 joe acpid: client 12450[0:0] has disconnected
Feb  1 19:23:06 joe acpid: client 12453[0:0] has disconnected
Feb  1 19:23:06 joe acpid: client 12455[0:0] has disconnected
Feb  1 19:23:06 joe acpid: client 12459[0:0] has disconnected
Feb  1 19:23:06 joe acpid: client 12458[0:0] has disconnected
Feb  1 19:23:06 joe acpid: client 12452[0:0] has disconnected
Feb  1 19:23:06 joe acpid: client 12461[0:0] has disconnected
Feb  1 19:23:06 joe acpid: client 12456[0:0] has disconnected
Feb  1 19:23:06 joe acpid: client connected from 12896[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12899[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12897[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12906[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12900[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12913[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12907[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12898[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12914[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12911[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12910[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12905[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12912[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12903[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12909[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12929[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12928[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12927[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12935[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12934[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:06 joe acpid: client connected from 12936[0:0]
Feb  1 19:23:06 joe acpid: 1 client rule loaded
Feb  1 19:23:07 joe acpid: client connected from 12933[0:0]
Feb  1 19:23:07 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client 12896[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12899[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12897[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12906[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12900[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12913[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12907[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12898[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12914[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12911[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12910[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12905[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12912[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12903[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12909[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12929[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12928[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12927[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12935[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12934[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12936[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client 12933[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client connected from 13351[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client 13351[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client connected from 13353[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client 13353[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client connected from 13360[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client 13360[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client connected from 13354[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client 13354[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client connected from 13359[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client 13359[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client connected from 13356[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client 13356[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client connected from 13352[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client 13352[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client connected from 13358[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client 13358[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client connected from 13357[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client 13357[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client connected from 13370[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client 13370[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client connected from 13368[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client 13368[0:0] has disconnected
Feb  1 19:23:23 joe acpid: client connected from 13369[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client connected from 13379[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client connected from 13377[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client connected from 13376[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client connected from 13375[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client connected from 13378[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client connected from 13380[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:23 joe acpid: client connected from 13381[0:0]
Feb  1 19:23:23 joe acpid: 1 client rule loaded
Feb  1 19:23:39 joe acpid: client 13369[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client 13379[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client 13377[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client 13376[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client 13375[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client 13378[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client 13380[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client 13381[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client connected from 13850[0:0]
Feb  1 19:23:39 joe acpid: 1 client rule loaded
Feb  1 19:23:39 joe acpid: client 13850[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client connected from 13852[0:0]
Feb  1 19:23:39 joe acpid: 1 client rule loaded
Feb  1 19:23:39 joe acpid: client 13852[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client connected from 13831[0:0]
Feb  1 19:23:39 joe acpid: 1 client rule loaded
Feb  1 19:23:39 joe acpid: client 13831[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client connected from 13853[0:0]
Feb  1 19:23:39 joe acpid: 1 client rule loaded
Feb  1 19:23:39 joe acpid: client 13853[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client connected from 13840[0:0]
Feb  1 19:23:39 joe acpid: 1 client rule loaded
Feb  1 19:23:39 joe acpid: client 13840[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client connected from 13847[0:0]
Feb  1 19:23:39 joe acpid: 1 client rule loaded
Feb  1 19:23:39 joe acpid: client 13847[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client connected from 13833[0:0]
Feb  1 19:23:39 joe acpid: 1 client rule loaded
Feb  1 19:23:39 joe acpid: client 13833[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client connected from 13851[0:0]
Feb  1 19:23:39 joe acpid: 1 client rule loaded
Feb  1 19:23:39 joe acpid: client 13851[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client connected from 13849[0:0]
Feb  1 19:23:39 joe acpid: 1 client rule loaded
Feb  1 19:23:39 joe acpid: client 13849[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client connected from 13834[0:0]
Feb  1 19:23:39 joe acpid: 1 client rule loaded
Feb  1 19:23:39 joe acpid: client 13834[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client connected from 13832[0:0]
Feb  1 19:23:39 joe acpid: 1 client rule loaded
Feb  1 19:23:39 joe acpid: client 13832[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client connected from 13835[0:0]
Feb  1 19:23:39 joe acpid: 1 client rule loaded
Feb  1 19:23:39 joe acpid: client 13835[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client connected from 13845[0:0]
Feb  1 19:23:39 joe acpid: 1 client rule loaded
Feb  1 19:23:39 joe acpid: client 13845[0:0] has disconnected
Feb  1 19:23:39 joe acpid: client connected from 13848[0:0]
Feb  1 19:23:39 joe acpid: 1 client rule loaded
Feb  1 19:23:39 joe acpid: client connected from 13843[0:0]
Feb  1 19:23:39 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client 13848[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client 13843[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client connected from 14296[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14301[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14300[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14306[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14298[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client 14296[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client 14301[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client 14300[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client 14306[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client 14298[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client connected from 14309[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client 14309[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client connected from 14299[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client 14299[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client connected from 14311[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client 14311[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client connected from 14308[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client 14308[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client connected from 14310[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client 14310[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client connected from 14313[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client 14313[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client connected from 14319[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client 14319[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client connected from 14318[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client 14318[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client connected from 14316[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client 14316[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client connected from 14320[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client 14320[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client connected from 14317[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client 14317[0:0] has disconnected
Feb  1 19:23:56 joe acpid: client connected from 14315[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14331[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14341[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14332[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14334[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14340[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14342[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14338[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14346[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14337[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14344[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14333[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14339[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14343[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14357[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14360[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14359[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14358[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:23:56 joe acpid: client connected from 14361[0:0]
Feb  1 19:23:56 joe acpid: 1 client rule loaded
Feb  1 19:24:07 joe acpid: client 14315[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14331[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14341[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14332[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14334[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14340[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14342[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14338[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14346[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14337[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14344[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14333[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14339[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14343[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14357[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14360[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14359[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14358[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client 14361[0:0] has disconnected
Feb  1 19:24:07 joe acpid: client connected from 14758[0:0]
Feb  1 19:24:07 joe acpid: 1 client rule loaded
Feb  1 19:24:07 joe acpid: client connected from 14757[0:0]
Feb  1 19:24:07 joe acpid: 1 client rule loaded
Feb  1 19:24:07 joe acpid: client connected from 14760[0:0]
Feb  1 19:24:07 joe acpid: 1 client rule loaded
Feb  1 19:24:07 joe acpid: client connected from 14763[0:0]
Feb  1 19:24:07 joe acpid: 1 client rule loaded
Feb  1 19:24:07 joe acpid: client connected from 14764[0:0]
Feb  1 19:24:07 joe acpid: 1 client rule loaded
Feb  1 19:24:07 joe acpid: client connected from 14761[0:0]
Feb  1 19:24:07 joe acpid: 1 client rule loaded
Feb  1 19:24:07 joe acpid: client connected from 14767[0:0]
Feb  1 19:24:07 joe acpid: 1 client rule loaded
Feb  1 19:24:07 joe acpid: client connected from 14765[0:0]
Feb  1 19:24:07 joe acpid: 1 client rule loaded
Feb  1 19:24:07 joe acpid: client connected from 14759[0:0]
Feb  1 19:24:07 joe acpid: 1 client rule loaded
Feb  1 19:24:24 joe acpid: client 14758[0:0] has disconnected
Feb  1 19:24:24 joe acpid: client 14757[0:0] has disconnected
Feb  1 19:24:24 joe acpid: client 14760[0:0] has disconnected
Feb  1 19:24:24 joe acpid: client 14763[0:0] has disconnected
Feb  1 19:24:24 joe acpid: client 14764[0:0] has disconnected
Feb  1 19:24:24 joe acpid: client 14761[0:0] has disconnected
Feb  1 19:24:24 joe acpid: client 14767[0:0] has disconnected
Feb  1 19:24:24 joe acpid: client 14765[0:0] has disconnected
Feb  1 19:24:24 joe acpid: client 14759[0:0] has disconnected
Feb  1 19:24:24 joe acpid: client connected from 15226[0:0]
Feb  1 19:24:24 joe acpid: 1 client rule loaded
Feb  1 19:24:24 joe acpid: client connected from 15225[0:0]
Feb  1 19:24:24 joe acpid: 1 client rule loaded
Feb  1 19:24:24 joe acpid: client connected from 15224[0:0]
Feb  1 19:24:24 joe acpid: 1 client rule loaded
Feb  1 19:24:24 joe acpid: client 15226[0:0] has disconnected
Feb  1 19:24:24 joe acpid: client connected from 15231[0:0]
Feb  1 19:24:24 joe acpid: 1 client rule loaded
Feb  1 19:24:24 joe acpid: client connected from 15234[0:0]
Feb  1 19:24:24 joe acpid: 1 client rule loaded
Feb  1 19:24:24 joe acpid: client connected from 15233[0:0]
Feb  1 19:24:24 joe acpid: 1 client rule loaded
Feb  1 19:24:24 joe acpid: client connected from 15232[0:0]
Feb  1 19:24:24 joe acpid: 1 client rule loaded
Feb  1 19:24:39 joe acpid: client 15225[0:0] has disconnected
Feb  1 19:24:39 joe acpid: client 15224[0:0] has disconnected
Feb  1 19:24:39 joe acpid: client 15231[0:0] has disconnected
Feb  1 19:24:39 joe acpid: client 15234[0:0] has disconnected
Feb  1 19:24:39 joe acpid: client 15233[0:0] has disconnected
Feb  1 19:24:39 joe acpid: client 15232[0:0] has disconnected
Feb  1 19:24:39 joe acpid: client connected from 15681[0:0]
Feb  1 19:24:39 joe acpid: 1 client rule loaded
Feb  1 19:24:39 joe acpid: client connected from 15683[0:0]
Feb  1 19:24:39 joe acpid: 1 client rule loaded
Feb  1 19:24:39 joe acpid: client connected from 15680[0:0]
Feb  1 19:24:39 joe acpid: 1 client rule loaded
Feb  1 19:24:39 joe acpid: client connected from 15684[0:0]
Feb  1 19:24:39 joe acpid: 1 client rule loaded
Feb  1 19:24:39 joe acpid: client connected from 15682[0:0]
Feb  1 19:24:39 joe acpid: 1 client rule loaded
Feb  1 19:24:43 joe dbus[1463]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Feb  1 19:24:43 joe acpid: client 15681[0:0] has disconnected
Feb  1 19:24:43 joe acpid: client 15683[0:0] has disconnected
Feb  1 19:24:43 joe acpid: client 15680[0:0] has disconnected
Feb  1 19:24:43 joe acpid: client 15684[0:0] has disconnected
Feb  1 19:24:43 joe acpid: client 15682[0:0] has disconnected
Feb  1 19:24:49 joe dbus[1463]: [system] Activated service 'org.freedesktop.PackageKit' failed: Process /usr/lib/dbus-1.0/dbus-daemon-launch-helper received signal 11
Feb  1 19:24:49 joe kernel: [18517.614833] packagekitd[15743]: segfault at 8 ip 0000000008057124 sp 00000000ffe577a0 error 4 in packagekitd[8048000+49000]
Feb  1 19:24:53 joe gdm-session-worker[15964]: CRITICAL: error getting system bus: The maximum number of active connections for UID 0 has been reached 
Feb  1 19:25:00 joe acpid: client 21690[0:0] has disconnected
Feb  1 19:25:00 joe acpid: client connected from 16160[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16165[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16162[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16164[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16157[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16158[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16172[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16169[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16175[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16167[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16173[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16178[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16170[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16159[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16174[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16177[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16192[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16191[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16194[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16190[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16193[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16201[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16202[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16203[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:00 joe acpid: client connected from 16200[0:0]
Feb  1 19:25:00 joe acpid: 1 client rule loaded
Feb  1 19:25:08 joe acpid: client 16160[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16165[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16162[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16164[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16157[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16158[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16172[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16169[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16175[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16167[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16173[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16178[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16159[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16174[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16177[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16192[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16191[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16194[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16190[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16193[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16201[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16202[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16203[0:0] has disconnected
Feb  1 19:25:08 joe acpid: client 16200[0:0] has disconnected
Feb  1 19:25:16 joe gdm-simple-slave[12041]: WARNING: Unable to open session: The maximum number of active connections for UID 0 has been reached  
Feb  1 19:25:16 joe acpid: client connected from 16615[0:0]
Feb  1 19:25:16 joe acpid: 1 client rule loaded
Feb  1 19:25:16 joe acpid: client connected from 16613[0:0]
Feb  1 19:25:16 joe acpid: 1 client rule loaded
Feb  1 19:25:16 joe acpid: client connected from 16614[0:0]
Feb  1 19:25:16 joe acpid: 1 client rule loaded
Feb  1 19:25:16 joe acpid: client connected from 16616[0:0]
Feb  1 19:25:16 joe acpid: 1 client rule loaded
Feb  1 19:25:16 joe acpid: client connected from 16612[0:0]
Feb  1 19:25:16 joe acpid: 1 client rule loaded
Feb  1 19:25:24 joe gnome-session[16660]: WARNING: Failed to start app: Unable to start application: Kindprozess »gnome-power-manager« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) 
Feb  1 19:25:32 joe acpid: client 16615[0:0] has disconnected
Feb  1 19:25:32 joe acpid: client 16613[0:0] has disconnected
Feb  1 19:25:32 joe acpid: client 16614[0:0] has disconnected
Feb  1 19:25:32 joe acpid: client 16616[0:0] has disconnected
Feb  1 19:25:32 joe acpid: client 16612[0:0] has disconnected
Feb  1 19:25:33 joe acpid: client connected from 17070[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17081[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17069[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17080[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17072[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17073[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17075[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17066[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17086[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17087[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17077[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17089[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17088[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17068[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17094[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17097[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17096[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:33 joe acpid: client connected from 17098[0:0]
Feb  1 19:25:33 joe acpid: 1 client rule loaded
Feb  1 19:25:34 joe acpid: client 17070[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17081[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17069[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17080[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17072[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17073[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17075[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17066[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17086[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17087[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17077[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17089[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17088[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17068[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17094[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17097[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17096[0:0] has disconnected
Feb  1 19:25:34 joe acpid: client 17098[0:0] has disconnected
Feb  1 19:25:40 joe gnome-session[16660]: WARNING: Unable to determine session: Unable to lookup session information for process '16660' 
Feb  1 19:25:51 joe last message repeated 9 times
Feb  1 19:25:51 joe acpid: client connected from 17514[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17516[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17521[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17519[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17524[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe gnome-session[16660]: WARNING: Unable to determine session: Unable to lookup session information for process '16660' 
Feb  1 19:25:51 joe acpid: client 17514[0:0] has disconnected
Feb  1 19:25:51 joe acpid: client 17516[0:0] has disconnected
Feb  1 19:25:51 joe acpid: client 17521[0:0] has disconnected
Feb  1 19:25:51 joe acpid: client 17519[0:0] has disconnected
Feb  1 19:25:51 joe acpid: client 17524[0:0] has disconnected
Feb  1 19:25:51 joe acpid: client connected from 17517[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client 17517[0:0] has disconnected
Feb  1 19:25:51 joe acpid: client connected from 17518[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client 17518[0:0] has disconnected
Feb  1 19:25:51 joe acpid: client connected from 17533[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client 17533[0:0] has disconnected
Feb  1 19:25:51 joe acpid: client connected from 17522[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client 17522[0:0] has disconnected
Feb  1 19:25:51 joe acpid: client connected from 17528[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client 17528[0:0] has disconnected
Feb  1 19:25:51 joe acpid: client connected from 17531[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client 17531[0:0] has disconnected
Feb  1 19:25:51 joe acpid: client connected from 17532[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client 17532[0:0] has disconnected
Feb  1 19:25:51 joe acpid: client connected from 17534[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client 17534[0:0] has disconnected
Feb  1 19:25:51 joe acpid: client connected from 17529[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client 17529[0:0] has disconnected
Feb  1 19:25:51 joe acpid: client connected from 17543[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client 17543[0:0] has disconnected
Feb  1 19:25:51 joe acpid: client connected from 17555[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client 17555[0:0] has disconnected
Feb  1 19:25:51 joe acpid: client connected from 17557[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17542[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17559[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17553[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17545[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17546[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17552[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17549[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17544[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17551[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17548[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17569[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17554[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17570[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17573[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17571[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe acpid: client connected from 17572[0:0]
Feb  1 19:25:51 joe acpid: 1 client rule loaded
Feb  1 19:25:51 joe gnome-session[16660]: WARNING: Unable to determine session: Unable to lookup session information for process '16660' 
Feb  1 19:25:51 joe gdm-simple-greeter[16873]: Gtk-WARNING: Overriding tab label for notebook 
Feb  1 19:25:51 joe last message repeated 4 times
Feb  1 19:25:52 joe gnome-session[16660]: WARNING: Unable to determine session: Unable to lookup session information for process '16660' 
Feb  1 19:25:52 joe gdm-simple-greeter[16873]: Gtk-WARNING: /build/buildd-gtk+3.0_3.2.3-1-i386-GA85Ik/gtk+3.0-3.2.3/./gtk/gtkwidget.c:6857: widget not within a GtkWindow 
Feb  1 19:25:53 joe gnome-session[16660]: WARNING: Unable to determine session: Unable to lookup session information for process '16660' 
Feb  1 19:26:00 joe last message repeated 7 times
Feb  1 19:26:01 joe gdm-simple-greeter[16873]: Gtk-CRITICAL: gtk_widget_get_preferred_height_for_width: assertion `width >= 0' failed 
Feb  1 19:26:01 joe gdm-simple-greeter[16873]: Gtk-WARNING: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height -3 
Feb  1 19:26:01 joe gdm-simple-greeter[16873]: Gtk-CRITICAL: gtk_widget_get_preferred_height_for_width: assertion `width >= 0' failed 
Feb  1 19:26:01 joe gdm-simple-greeter[16873]: Gtk-CRITICAL: gtk_widget_get_preferred_height_for_width: assertion `width >= 0' failed 
Feb  1 19:26:01 joe gdm-simple-greeter[16873]: Gtk-WARNING: gtk_widget_size_allocate(): attempt to allocate widget with width -47 and height -47 
Feb  1 19:26:01 joe gnome-session[16660]: WARNING: Unable to determine session: Unable to lookup session information for process '16660' 
Feb  1 19:26:07 joe last message repeated 6 times
Feb  1 19:26:08 joe acpid: client 17557[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client 17542[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client 17559[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client 17553[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client 17545[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client 17546[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client 17552[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client 17549[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client 17544[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client 17551[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client 17548[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client 17569[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client 17554[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client 17570[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client 17573[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client 17571[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client 17572[0:0] has disconnected
Feb  1 19:26:08 joe acpid: client connected from 17994[0:0]
Feb  1 19:26:08 joe acpid: 1 client rule loaded
Feb  1 19:26:08 joe acpid: client connected from 18008[0:0]
Feb  1 19:26:08 joe acpid: 1 client rule loaded
Feb  1 19:26:08 joe acpid: client connected from 18022[0:0]
Feb  1 19:26:08 joe acpid: 1 client rule loaded
Feb  1 19:26:08 joe acpid: client connected from 18000[0:0]
Feb  1 19:26:08 joe acpid: 1 client rule loaded
Feb  1 19:26:08 joe acpid: client connected from 17999[0:0]
Feb  1 19:26:08 joe acpid: 1 client rule loaded
Feb  1 19:26:08 joe acpid: client connected from 18012[0:0]
Feb  1 19:26:08 joe acpid: 1 client rule loaded
Feb  1 19:26:08 joe acpid: client connected from 18003[0:0]
Feb  1 19:26:08 joe acpid: 1 client rule loaded
Feb  1 19:26:08 joe acpid: client connected from 18001[0:0]
Feb  1 19:26:08 joe acpid: 1 client rule loaded
Feb  1 19:26:08 joe acpid: client connected from 17998[0:0]
Feb  1 19:26:08 joe acpid: 1 client rule loaded
Feb  1 19:26:08 joe acpid: client connected from 18005[0:0]
Feb  1 19:26:08 joe acpid: 1 client rule loaded
Feb  1 19:26:08 joe acpid: client connected from 17997[0:0]
Feb  1 19:26:08 joe acpid: 1 client rule loaded
Feb  1 19:26:08 joe acpid: client connected from 18007[0:0]
Feb  1 19:26:08 joe acpid: 1 client rule loaded
Feb  1 19:26:08 joe acpid: client connected from 18004[0:0]
Feb  1 19:26:08 joe acpid: 1 client rule loaded
Feb  1 19:26:08 joe acpid: client connected from 18006[0:0]
Feb  1 19:26:08 joe acpid: 1 client rule loaded
Feb  1 19:26:08 joe acpid: client connected from 18021[0:0]
Feb  1 19:26:08 joe acpid: 1 client rule loaded
Feb  1 19:26:08 joe gnome-session[16660]: WARNING: Unable to determine session: Unable to lookup session information for process '16660' 
Feb  1 19:26:24 joe last message repeated 16 times
Feb  1 19:26:24 joe acpid: client 17994[0:0] has disconnected
Feb  1 19:26:24 joe acpid: client 18008[0:0] has disconnected
Feb  1 19:26:24 joe acpid: client 18022[0:0] has disconnected
Feb  1 19:26:24 joe acpid: client 18000[0:0] has disconnected
Feb  1 19:26:24 joe acpid: client 17999[0:0] has disconnected
Feb  1 19:26:24 joe acpid: client 18012[0:0] has disconnected
Feb  1 19:26:24 joe acpid: client 18003[0:0] has disconnected
Feb  1 19:26:24 joe acpid: client 18001[0:0] has disconnected
Feb  1 19:26:24 joe acpid: client 17998[0:0] has disconnected
Feb  1 19:26:24 joe acpid: client 18005[0:0] has disconnected
Feb  1 19:26:24 joe acpid: client 17997[0:0] has disconnected
Feb  1 19:26:24 joe acpid: client 18007[0:0] has disconnected
Feb  1 19:26:24 joe acpid: client 18004[0:0] has disconnected
Feb  1 19:26:24 joe acpid: client 18006[0:0] has disconnected
Feb  1 19:26:24 joe acpid: client 18021[0:0] has disconnected
Feb  1 19:26:24 joe acpid: client connected from 18465[0:0]
Feb  1 19:26:24 joe acpid: 1 client rule loaded
Feb  1 19:26:24 joe acpid: client connected from 18466[0:0]
Feb  1 19:26:24 joe acpid: 1 client rule loaded
Feb  1 19:26:24 joe acpid: client connected from 18459[0:0]
Feb  1 19:26:24 joe acpid: 1 client rule loaded
Feb  1 19:26:24 joe acpid: client connected from 18460[0:0]
Feb  1 19:26:24 joe acpid: 1 client rule loaded
Feb  1 19:26:24 joe acpid: client connected from 18457[0:0]
Feb  1 19:26:24 joe acpid: 1 client rule loaded
Feb  1 19:26:24 joe acpid: client connected from 18464[0:0]
Feb  1 19:26:24 joe acpid: 1 client rule loaded
Feb  1 19:26:24 joe acpid: client connected from 18461[0:0]
Feb  1 19:26:24 joe acpid: 1 client rule loaded
Feb  1 19:26:27 joe gnome-session[16660]: WARNING: Unable to determine session: Unable to lookup session information for process '16660' 
Feb  1 19:26:40 joe last message repeated 15 times
Feb  1 19:26:41 joe gdm-simple-slave[12041]: WARNING: Unable to close session: no session open  
Feb  1 19:26:45 joe acpid: client 18465[0:0] has disconnected
Feb  1 19:26:45 joe acpid: client 18466[0:0] has disconnected
Feb  1 19:26:45 joe acpid: client 18459[0:0] has disconnected
Feb  1 19:26:45 joe acpid: client 18460[0:0] has disconnected
Feb  1 19:26:45 joe acpid: client 18457[0:0] has disconnected
Feb  1 19:26:45 joe acpid: client 18464[0:0] has disconnected
Feb  1 19:26:45 joe acpid: client 18461[0:0] has disconnected
Feb  1 19:26:45 joe acpid: client connected from 18924[0:0]
Feb  1 19:26:45 joe acpid: 1 client rule loaded
Feb  1 19:26:45 joe acpid: client 16170[0:0] has disconnected
Feb  1 19:26:46 joe acpid: client connected from 18925[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18922[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client 18922[0:0] has disconnected
Feb  1 19:26:46 joe acpid: client connected from 18932[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client 18932[0:0] has disconnected
Feb  1 19:26:46 joe acpid: client connected from 18935[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client 18935[0:0] has disconnected
Feb  1 19:26:46 joe acpid: client connected from 18941[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client 18941[0:0] has disconnected
Feb  1 19:26:46 joe acpid: client connected from 18936[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client 18936[0:0] has disconnected
Feb  1 19:26:46 joe acpid: client connected from 18928[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client 18928[0:0] has disconnected
Feb  1 19:26:46 joe acpid: client connected from 18947[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client 18947[0:0] has disconnected
Feb  1 19:26:46 joe acpid: client connected from 18945[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client 18945[0:0] has disconnected
Feb  1 19:26:46 joe acpid: client connected from 18944[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client 18944[0:0] has disconnected
Feb  1 19:26:46 joe acpid: client connected from 18929[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client 18929[0:0] has disconnected
Feb  1 19:26:46 joe acpid: client connected from 18948[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client 18948[0:0] has disconnected
Feb  1 19:26:46 joe acpid: client connected from 18952[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client 18952[0:0] has disconnected
Feb  1 19:26:46 joe acpid: client connected from 18946[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client 18946[0:0] has disconnected
Feb  1 19:26:46 joe acpid: client connected from 18957[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client 18957[0:0] has disconnected
Feb  1 19:26:46 joe acpid: client connected from 18962[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client 18962[0:0] has disconnected
Feb  1 19:26:46 joe acpid: client connected from 18956[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18930[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18961[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18950[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18959[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18954[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18960[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18951[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18949[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18955[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18923[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18982[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18981[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18983[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18980[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18984[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18986[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18985[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18988[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:46 joe acpid: client connected from 18987[0:0]
Feb  1 19:26:46 joe acpid: 1 client rule loaded
Feb  1 19:26:57 joe acpid: client 18956[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18930[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18961[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18950[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18959[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18954[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18960[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18951[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18949[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18955[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18923[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18982[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18981[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18983[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18980[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18984[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18986[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18985[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18988[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 18987[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client connected from 19388[0:0]
Feb  1 19:26:57 joe acpid: 1 client rule loaded
Feb  1 19:26:57 joe acpid: client connected from 19389[0:0]
Feb  1 19:26:57 joe acpid: 1 client rule loaded
Feb  1 19:26:57 joe acpid: client connected from 19392[0:0]
Feb  1 19:26:57 joe acpid: 1 client rule loaded
Feb  1 19:26:57 joe acpid: client connected from 19393[0:0]
Feb  1 19:26:57 joe acpid: 1 client rule loaded
Feb  1 19:26:57 joe acpid: client connected from 19390[0:0]
Feb  1 19:26:57 joe acpid: 1 client rule loaded
Feb  1 19:26:57 joe acpid: client connected from 19391[0:0]
Feb  1 19:26:57 joe acpid: 1 client rule loaded
Feb  1 19:26:57 joe acpid: client connected from 19394[0:0]
Feb  1 19:26:57 joe acpid: 1 client rule loaded
Feb  1 19:26:57 joe acpid: client 19388[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 19389[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 19392[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 19393[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 19390[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 19391[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client 19394[0:0] has disconnected
Feb  1 19:26:57 joe acpid: client connected from 19403[0:0]
Feb  1 19:26:57 joe acpid: 1 client rule loaded
Feb  1 19:27:08 joe gnome-session[19459]: WARNING: Failed to start app: Unable to start application: Kindprozess »gnome-power-manager« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) 
Feb  1 19:27:15 joe acpid: client 19403[0:0] has disconnected
Feb  1 19:27:15 joe acpid: client connected from 19890[0:0]
Feb  1 19:27:15 joe acpid: 1 client rule loaded
Feb  1 19:27:15 joe acpid: client connected from 19889[0:0]
Feb  1 19:27:15 joe acpid: 1 client rule loaded
Feb  1 19:27:15 joe acpid: client connected from 19888[0:0]
Feb  1 19:27:15 joe acpid: 1 client rule loaded
Feb  1 19:27:15 joe acpid: client connected from 19893[0:0]
Feb  1 19:27:15 joe acpid: 1 client rule loaded
Feb  1 19:27:15 joe acpid: client connected from 19891[0:0]
Feb  1 19:27:15 joe acpid: 1 client rule loaded
Feb  1 19:27:15 joe acpid: client connected from 19894[0:0]
Feb  1 19:27:15 joe acpid: 1 client rule loaded
Feb  1 19:27:15 joe acpid: client connected from 19898[0:0]
Feb  1 19:27:15 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client 19890[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client 19889[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client 19888[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client 19893[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client 19891[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client 19894[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client 19898[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client connected from 20366[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client connected from 20365[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe gdm-simple-greeter[19694]: Gtk-WARNING: Overriding tab label for notebook 
Feb  1 19:27:34 joe acpid: client 20366[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client 20365[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client connected from 20368[0:0]
Feb  1 19:27:34 joe gdm-simple-greeter[19694]: Gtk-WARNING: Overriding tab label for notebook 
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe gdm-simple-greeter[19694]: Gtk-WARNING: Overriding tab label for notebook 
Feb  1 19:27:34 joe acpid: client 20368[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client connected from 20372[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client 20372[0:0] has disconnected
Feb  1 19:27:34 joe gdm-simple-greeter[19694]: Gtk-WARNING: Overriding tab label for notebook 
Feb  1 19:27:34 joe acpid: client connected from 20374[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client 20374[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client connected from 20371[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client 20371[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client connected from 20391[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client 20391[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client connected from 20386[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe gdm-simple-greeter[19694]: Gtk-WARNING: Overriding tab label for notebook 
Feb  1 19:27:34 joe acpid: client 20386[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client connected from 20388[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client 20388[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client connected from 20389[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client 20389[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client connected from 20395[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client 20395[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client connected from 20385[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client 20385[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client connected from 20378[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client 20378[0:0] has disconnected
Feb  1 19:27:34 joe acpid: client connected from 20384[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client connected from 20392[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client connected from 20382[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client connected from 20380[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client connected from 20379[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client connected from 20383[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client connected from 20396[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client connected from 20413[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client connected from 20415[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client connected from 20414[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client connected from 20417[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client connected from 20381[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client connected from 20416[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client connected from 20373[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client connected from 20394[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe acpid: client connected from 20393[0:0]
Feb  1 19:27:34 joe acpid: 1 client rule loaded
Feb  1 19:27:34 joe gdm-simple-greeter[19694]: Gtk-WARNING: /build/buildd-gtk+3.0_3.2.3-1-i386-GA85Ik/gtk+3.0-3.2.3/./gtk/gtkwidget.c:6857: widget not within a GtkWindow 
Feb  1 19:27:41 joe gdm-simple-greeter[19694]: Gtk-CRITICAL: gtk_widget_get_preferred_height_for_width: assertion `width >= 0' failed 
Feb  1 19:27:41 joe gdm-simple-greeter[19694]: Gtk-WARNING: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height -3 
Feb  1 19:27:41 joe gdm-simple-greeter[19694]: Gtk-CRITICAL: gtk_widget_get_preferred_height_for_width: assertion `width >= 0' failed 
Feb  1 19:27:41 joe gdm-simple-greeter[19694]: Gtk-CRITICAL: gtk_widget_get_preferred_height_for_width: assertion `width >= 0' failed 
Feb  1 19:27:41 joe gdm-simple-greeter[19694]: Gtk-WARNING: gtk_widget_size_allocate(): attempt to allocate widget with width -47 and height -47 
Feb  1 19:27:51 joe acpid: client 20384[0:0] has disconnected
Feb  1 19:27:51 joe acpid: client 20392[0:0] has disconnected
Feb  1 19:27:51 joe acpid: client 20382[0:0] has disconnected
Feb  1 19:27:51 joe acpid: client 20380[0:0] has disconnected
Feb  1 19:27:51 joe acpid: client 20379[0:0] has disconnected
Feb  1 19:27:51 joe acpid: client 20383[0:0] has disconnected
Feb  1 19:27:51 joe acpid: client 20396[0:0] has disconnected
Feb  1 19:27:51 joe acpid: client 20413[0:0] has disconnected
Feb  1 19:27:51 joe acpid: client 20415[0:0] has disconnected
Feb  1 19:27:51 joe acpid: client 20414[0:0] has disconnected
Feb  1 19:27:51 joe acpid: client 20417[0:0] has disconnected
Feb  1 19:27:51 joe acpid: client 20381[0:0] has disconnected
Feb  1 19:27:51 joe acpid: client 20416[0:0] has disconnected
Feb  1 19:27:51 joe acpid: client 20373[0:0] has disconnected
Feb  1 19:27:51 joe acpid: client 20394[0:0] has disconnected
Feb  1 19:27:51 joe acpid: client 20393[0:0] has disconnected
Feb  1 19:27:51 joe acpid: client connected from 20847[0:0]
Feb  1 19:27:51 joe acpid: 1 client rule loaded
Feb  1 19:27:51 joe acpid: client connected from 20853[0:0]
Feb  1 19:27:51 joe acpid: 1 client rule loaded
Feb  1 19:27:51 joe acpid: client connected from 20856[0:0]
Feb  1 19:27:51 joe acpid: 1 client rule loaded
Feb  1 19:27:51 joe acpid: client connected from 20858[0:0]
Feb  1 19:27:51 joe acpid: 1 client rule loaded
Feb  1 19:27:51 joe acpid: client connected from 20857[0:0]
Feb  1 19:27:51 joe acpid: 1 client rule loaded
Feb  1 19:27:51 joe acpid: client connected from 20850[0:0]
Feb  1 19:27:51 joe acpid: 1 client rule loaded
Feb  1 19:27:51 joe acpid: client connected from 20849[0:0]
Feb  1 19:27:51 joe acpid: 1 client rule loaded
Feb  1 19:27:51 joe acpid: client connected from 20855[0:0]
Feb  1 19:27:51 joe acpid: 1 client rule loaded
Feb  1 19:27:51 joe acpid: client connected from 20848[0:0]
Feb  1 19:27:51 joe acpid: 1 client rule loaded
Feb  1 19:27:51 joe acpid: client connected from 20859[0:0]
Feb  1 19:27:51 joe acpid: 1 client rule loaded
Feb  1 19:27:51 joe acpid: client connected from 20852[0:0]
Feb  1 19:27:51 joe acpid: 1 client rule loaded
Feb  1 19:28:07 joe acpid: client 20847[0:0] has disconnected
Feb  1 19:28:07 joe acpid: client 20853[0:0] has disconnected
Feb  1 19:28:07 joe acpid: client 20856[0:0] has disconnected
Feb  1 19:28:07 joe acpid: client 20858[0:0] has disconnected
Feb  1 19:28:07 joe acpid: client 20857[0:0] has disconnected
Feb  1 19:28:07 joe acpid: client 20850[0:0] has disconnected
Feb  1 19:28:07 joe acpid: client 20849[0:0] has disconnected
Feb  1 19:28:07 joe acpid: client 20855[0:0] has disconnected
Feb  1 19:28:07 joe acpid: client 20848[0:0] has disconnected
Feb  1 19:28:07 joe acpid: client 20859[0:0] has disconnected
Feb  1 19:28:07 joe acpid: client 20852[0:0] has disconnected
Feb  1 19:28:07 joe acpid: client connected from 21320[0:0]
Feb  1 19:28:07 joe acpid: 1 client rule loaded
Feb  1 19:28:07 joe acpid: client connected from 21322[0:0]
Feb  1 19:28:07 joe acpid: 1 client rule loaded
Feb  1 19:28:07 joe acpid: client connected from 21321[0:0]
Feb  1 19:28:07 joe acpid: 1 client rule loaded
Feb  1 19:28:08 joe acpid: client 21320[0:0] has disconnected
Feb  1 19:28:08 joe acpid: client 21322[0:0] has disconnected
Feb  1 19:28:08 joe acpid: client 21321[0:0] has disconnected
Feb  1 19:28:08 joe acpid: client connected from 21326[0:0]
Feb  1 19:28:08 joe acpid: 1 client rule loaded
Feb  1 19:28:08 joe acpid: client connected from 21327[0:0]
Feb  1 19:28:08 joe acpid: 1 client rule loaded
Feb  1 19:28:08 joe acpid: client connected from 21328[0:0]
Feb  1 19:28:08 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client 21326[0:0] has disconnected
Feb  1 19:28:27 joe acpid: client 21327[0:0] has disconnected
Feb  1 19:28:27 joe acpid: client 21328[0:0] has disconnected
Feb  1 19:28:27 joe acpid: client connected from 21807[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21808[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21806[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21809[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21801[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21802[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21804[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21812[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21814[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21815[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21803[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21843[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21811[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21824[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21829[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21828[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21827[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21823[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client 21801[0:0] has disconnected
Feb  1 19:28:27 joe acpid: client connected from 21842[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client 21807[0:0] has disconnected
Feb  1 19:28:27 joe acpid: client 21808[0:0] has disconnected
Feb  1 19:28:27 joe acpid: client 21809[0:0] has disconnected
Feb  1 19:28:27 joe acpid: client connected from 21831[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21835[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21832[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21844[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21834[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21838[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client 21812[0:0] has disconnected
Feb  1 19:28:27 joe acpid: client 21814[0:0] has disconnected
Feb  1 19:28:27 joe acpid: client connected from 21839[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21837[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client 21815[0:0] has disconnected
Feb  1 19:28:27 joe acpid: client connected from 21845[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21840[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21836[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21833[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21813[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:27 joe acpid: client connected from 21868[0:0]
Feb  1 19:28:27 joe acpid: 1 client rule loaded
Feb  1 19:28:44 joe acpid: client 21806[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21802[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21804[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21803[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21843[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21811[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21824[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21829[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21828[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21827[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21823[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21842[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21831[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21835[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21832[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21844[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21834[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21838[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21839[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21837[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21845[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21840[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21836[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21833[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21813[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client 21868[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client connected from 22288[0:0]
Feb  1 19:28:44 joe acpid: 1 client rule loaded
Feb  1 19:28:44 joe acpid: client 22288[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client connected from 22291[0:0]
Feb  1 19:28:44 joe acpid: 1 client rule loaded
Feb  1 19:28:44 joe acpid: client 22291[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client connected from 22300[0:0]
Feb  1 19:28:44 joe acpid: 1 client rule loaded
Feb  1 19:28:44 joe acpid: client 22300[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client connected from 22298[0:0]
Feb  1 19:28:44 joe acpid: 1 client rule loaded
Feb  1 19:28:44 joe acpid: client 22298[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client connected from 22297[0:0]
Feb  1 19:28:44 joe acpid: 1 client rule loaded
Feb  1 19:28:44 joe acpid: client 22297[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client connected from 22296[0:0]
Feb  1 19:28:44 joe acpid: 1 client rule loaded
Feb  1 19:28:44 joe acpid: client 22296[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client connected from 22299[0:0]
Feb  1 19:28:44 joe acpid: 1 client rule loaded
Feb  1 19:28:44 joe acpid: client 22299[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client connected from 22293[0:0]
Feb  1 19:28:44 joe acpid: 1 client rule loaded
Feb  1 19:28:44 joe acpid: client 22293[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client connected from 22294[0:0]
Feb  1 19:28:44 joe acpid: 1 client rule loaded
Feb  1 19:28:44 joe acpid: client 22294[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client connected from 22304[0:0]
Feb  1 19:28:44 joe acpid: 1 client rule loaded
Feb  1 19:28:44 joe acpid: client 22304[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client connected from 22303[0:0]
Feb  1 19:28:44 joe acpid: 1 client rule loaded
Feb  1 19:28:44 joe acpid: client 22303[0:0] has disconnected
Feb  1 19:28:44 joe acpid: client connected from 22302[0:0]
Feb  1 19:28:44 joe acpid: 1 client rule loaded
Feb  1 19:28:44 joe acpid: client connected from 22305[0:0]
Feb  1 19:28:44 joe acpid: 1 client rule loaded
Feb  1 19:28:44 joe acpid: client connected from 22295[0:0]
Feb  1 19:28:44 joe acpid: 1 client rule loaded
Feb  1 19:28:44 joe acpid: client connected from 22306[0:0]
Feb  1 19:28:44 joe acpid: 1 client rule loaded
Feb  1 19:29:01 joe acpid: client 22302[0:0] has disconnected
Feb  1 19:29:01 joe acpid: client 22305[0:0] has disconnected
Feb  1 19:29:01 joe acpid: client 22295[0:0] has disconnected
Feb  1 19:29:01 joe acpid: client 22306[0:0] has disconnected
Feb  1 19:29:01 joe acpid: client connected from 22771[0:0]
Feb  1 19:29:01 joe acpid: 1 client rule loaded
Feb  1 19:29:01 joe acpid: client connected from 22775[0:0]
Feb  1 19:29:01 joe acpid: 1 client rule loaded
Feb  1 19:29:01 joe acpid: client connected from 22776[0:0]
Feb  1 19:29:01 joe acpid: 1 client rule loaded
Feb  1 19:29:01 joe acpid: client connected from 22777[0:0]
Feb  1 19:29:01 joe acpid: 1 client rule loaded
Feb  1 19:29:01 joe acpid: client connected from 22773[0:0]
Feb  1 19:29:01 joe acpid: 1 client rule loaded
Feb  1 19:29:01 joe acpid: client connected from 22772[0:0]
Feb  1 19:29:01 joe acpid: 1 client rule loaded
Feb  1 19:29:01 joe acpid: client connected from 22784[0:0]
Feb  1 19:29:01 joe acpid: 1 client rule loaded
Feb  1 19:29:19 joe acpid: client 22771[0:0] has disconnected
Feb  1 19:29:19 joe acpid: client 22775[0:0] has disconnected
Feb  1 19:29:19 joe acpid: client 22776[0:0] has disconnected
Feb  1 19:29:19 joe acpid: client 22777[0:0] has disconnected
Feb  1 19:29:19 joe acpid: client 22773[0:0] has disconnected
Feb  1 19:29:19 joe acpid: client 22772[0:0] has disconnected
Feb  1 19:29:19 joe acpid: client 22784[0:0] has disconnected
Feb  1 19:29:19 joe acpid: client connected from 23467[0:0]
Feb  1 19:29:19 joe acpid: 1 client rule loaded
Feb  1 19:29:19 joe acpid: client connected from 23468[0:0]
Feb  1 19:29:19 joe acpid: 1 client rule loaded
Feb  1 19:29:19 joe acpid: client connected from 23470[0:0]
Feb  1 19:29:19 joe acpid: 1 client rule loaded
Feb  1 19:29:19 joe acpid: client connected from 23474[0:0]
Feb  1 19:29:19 joe acpid: 1 client rule loaded
Feb  1 19:29:19 joe acpid: client connected from 23472[0:0]
Feb  1 19:29:19 joe acpid: 1 client rule loaded
Feb  1 19:29:19 joe acpid: client connected from 23495[0:0]
Feb  1 19:29:19 joe acpid: 1 client rule loaded
Feb  1 19:29:19 joe acpid: client connected from 23480[0:0]
Feb  1 19:29:19 joe acpid: 1 client rule loaded
Feb  1 19:29:19 joe acpid: client connected from 23483[0:0]
Feb  1 19:29:19 joe acpid: 1 client rule loaded
Feb  1 19:29:19 joe acpid: client connected from 23481[0:0]
Feb  1 19:29:19 joe acpid: 1 client rule loaded
Feb  1 19:29:19 joe acpid: client connected from 23478[0:0]
Feb  1 19:29:19 joe acpid: 1 client rule loaded
Feb  1 19:29:19 joe acpid: client connected from 23477[0:0]
Feb  1 19:29:19 joe acpid: 1 client rule loaded
Feb  1 19:29:19 joe acpid: client connected from 23482[0:0]
Feb  1 19:29:19 joe acpid: 1 client rule loaded
Feb  1 19:29:19 joe acpid: client connected from 23471[0:0]
Feb  1 19:29:19 joe acpid: 1 client rule loaded
Feb  1 19:29:19 joe acpid: client connected from 23469[0:0]
Feb  1 19:29:19 joe acpid: 1 client rule loaded
Feb  1 19:29:19 joe acpid: client connected from 23484[0:0]
Feb  1 19:29:19 joe acpid: 1 client rule loaded
Feb  1 19:29:20 joe acpid: client connected from 23497[0:0]
Feb  1 19:29:20 joe acpid: 1 client rule loaded
Feb  1 19:29:20 joe acpid: client connected from 23501[0:0]
Feb  1 19:29:20 joe acpid: 1 client rule loaded
Feb  1 19:29:20 joe acpid: client connected from 23504[0:0]
Feb  1 19:29:20 joe acpid: 1 client rule loaded
Feb  1 19:29:20 joe acpid: client connected from 23508[0:0]
Feb  1 19:29:20 joe acpid: 1 client rule loaded
Feb  1 19:29:20 joe acpid: client connected from 23499[0:0]
Feb  1 19:29:20 joe acpid: 1 client rule loaded
Feb  1 19:29:20 joe acpid: client 23468[0:0] has disconnected
Feb  1 19:29:20 joe acpid: client connected from 23500[0:0]
Feb  1 19:29:20 joe acpid: 1 client rule loaded
Feb  1 19:29:20 joe acpid: client 23467[0:0] has disconnected
Feb  1 19:29:20 joe acpid: client 23470[0:0] has disconnected
Feb  1 19:29:20 joe acpid: client 23471[0:0] has disconnected
Feb  1 19:29:20 joe acpid: client connected from 23498[0:0]
Feb  1 19:29:20 joe acpid: 1 client rule loaded
Feb  1 19:29:20 joe acpid: client 23480[0:0] has disconnected
Feb  1 19:29:20 joe acpid: client connected from 23496[0:0]
Feb  1 19:29:20 joe acpid: 1 client rule loaded
Feb  1 19:29:20 joe acpid: client 23481[0:0] has disconnected
Feb  1 19:29:20 joe acpid: client connected from 23520[0:0]
Feb  1 19:29:20 joe acpid: 1 client rule loaded
Feb  1 19:29:20 joe acpid: client connected from 23521[0:0]
Feb  1 19:29:20 joe acpid: 1 client rule loaded
Feb  1 19:29:20 joe acpid: client connected from 23519[0:0]
Feb  1 19:29:20 joe acpid: 1 client rule loaded
Feb  1 19:29:20 joe acpid: client 23472[0:0] has disconnected
Feb  1 19:29:20 joe acpid: client 23483[0:0] has disconnected
Feb  1 19:29:20 joe acpid: client 23478[0:0] has disconnected
Feb  1 19:29:20 joe acpid: client 23482[0:0] has disconnected
Feb  1 19:29:20 joe acpid: client connected from 23522[0:0]
Feb  1 19:29:20 joe acpid: 1 client rule loaded
Feb  1 19:29:20 joe acpid: client 23474[0:0] has disconnected
Feb  1 19:29:20 joe acpid: client 23477[0:0] has disconnected
Feb  1 19:29:20 joe acpid: client connected from 23517[0:0]
Feb  1 19:29:20 joe acpid: 1 client rule loaded
Feb  1 19:29:37 joe acpid: client 23495[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23469[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23484[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23497[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23501[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23504[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23508[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23499[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23500[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23498[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23496[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23520[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23521[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23519[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23522[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23517[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client connected from 23930[0:0]
Feb  1 19:29:37 joe acpid: 1 client rule loaded
Feb  1 19:29:37 joe acpid: client connected from 23931[0:0]
Feb  1 19:29:37 joe acpid: 1 client rule loaded
Feb  1 19:29:37 joe acpid: client connected from 23939[0:0]
Feb  1 19:29:37 joe acpid: 1 client rule loaded
Feb  1 19:29:37 joe acpid: client connected from 23933[0:0]
Feb  1 19:29:37 joe acpid: 1 client rule loaded
Feb  1 19:29:37 joe acpid: client connected from 23938[0:0]
Feb  1 19:29:37 joe acpid: 1 client rule loaded
Feb  1 19:29:37 joe acpid: client connected from 23936[0:0]
Feb  1 19:29:37 joe acpid: 1 client rule loaded
Feb  1 19:29:37 joe acpid: client connected from 23937[0:0]
Feb  1 19:29:37 joe acpid: 1 client rule loaded
Feb  1 19:29:37 joe acpid: client connected from 23932[0:0]
Feb  1 19:29:37 joe acpid: 1 client rule loaded
Feb  1 19:29:37 joe acpid: client connected from 23935[0:0]
Feb  1 19:29:37 joe acpid: 1 client rule loaded
Feb  1 19:29:37 joe acpid: client 23930[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23931[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23939[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23933[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23938[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23936[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23937[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23932[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client 23935[0:0] has disconnected
Feb  1 19:29:37 joe acpid: client connected from 23950[0:0]
Feb  1 19:29:37 joe acpid: 1 client rule loaded
Feb  1 19:29:37 joe acpid: client connected from 23949[0:0]
Feb  1 19:29:37 joe acpid: 1 client rule loaded
Feb  1 19:29:37 joe acpid: client connected from 23953[0:0]
Feb  1 19:29:37 joe acpid: 1 client rule loaded
Feb  1 19:29:37 joe acpid: client connected from 23952[0:0]
Feb  1 19:29:37 joe acpid: 1 client rule loaded
Feb  1 19:29:37 joe acpid: client connected from 23951[0:0]
Feb  1 19:29:37 joe acpid: 1 client rule loaded
Feb  1 19:29:37 joe acpid: client connected from 23954[0:0]
Feb  1 19:29:37 joe acpid: 1 client rule loaded
Feb  1 19:29:37 joe acpid: client connected from 23961[0:0]
Feb  1 19:29:37 joe acpid: 1 client rule loaded
Feb  1 19:29:55 joe acpid: client 23950[0:0] has disconnected
Feb  1 19:29:55 joe acpid: client 23949[0:0] has disconnected
Feb  1 19:29:55 joe acpid: client 23953[0:0] has disconnected
Feb  1 19:29:55 joe acpid: client 23952[0:0] has disconnected
Feb  1 19:29:55 joe acpid: client 23951[0:0] has disconnected
Feb  1 19:29:55 joe acpid: client 23954[0:0] has disconnected
Feb  1 19:29:55 joe acpid: client 23961[0:0] has disconnected
Feb  1 19:29:55 joe acpid: client connected from 24394[0:0]
Feb  1 19:29:55 joe acpid: 1 client rule loaded
Feb  1 19:29:55 joe acpid: client connected from 24399[0:0]
Feb  1 19:29:55 joe acpid: 1 client rule loaded
Feb  1 19:29:55 joe acpid: client connected from 24398[0:0]
Feb  1 19:29:55 joe acpid: 1 client rule loaded
Feb  1 19:29:55 joe acpid: client connected from 24395[0:0]
Feb  1 19:29:55 joe acpid: 1 client rule loaded
Feb  1 19:29:55 joe acpid: client connected from 24397[0:0]
Feb  1 19:29:55 joe acpid: 1 client rule loaded
Feb  1 19:29:55 joe acpid: client connected from 24396[0:0]
Feb  1 19:29:55 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client 24394[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client 24399[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client 24398[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client 24395[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client 24397[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client 24396[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client connected from 24869[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client connected from 24866[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client connected from 24865[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client 24869[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client 24866[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client 24865[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client connected from 24875[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client 24875[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client connected from 24870[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client 24870[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client connected from 24868[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client 24868[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client connected from 24874[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client 24874[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client connected from 24873[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client 24873[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client connected from 24871[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client 24871[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client connected from 24872[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client 24872[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client connected from 24888[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client 24888[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client connected from 24886[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client 24886[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client connected from 24895[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client 24895[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client connected from 24890[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client 24890[0:0] has disconnected
Feb  1 19:30:15 joe acpid: client connected from 24898[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client connected from 24892[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client connected from 24893[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client connected from 24889[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client connected from 24897[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client connected from 24887[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client connected from 24894[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client connected from 24885[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client connected from 24906[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client connected from 24901[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client connected from 24891[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client connected from 24905[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client connected from 24900[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client connected from 24908[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:15 joe acpid: client connected from 24907[0:0]
Feb  1 19:30:15 joe acpid: 1 client rule loaded
Feb  1 19:30:30 joe acpid: client 24898[0:0] has disconnected
Feb  1 19:30:30 joe acpid: client 24892[0:0] has disconnected
Feb  1 19:30:30 joe acpid: client 24893[0:0] has disconnected
Feb  1 19:30:30 joe acpid: client 24889[0:0] has disconnected
Feb  1 19:30:30 joe acpid: client 24897[0:0] has disconnected
Feb  1 19:30:30 joe acpid: client 24887[0:0] has disconnected
Feb  1 19:30:30 joe acpid: client 24894[0:0] has disconnected
Feb  1 19:30:30 joe acpid: client 24885[0:0] has disconnected
Feb  1 19:30:30 joe acpid: client 24906[0:0] has disconnected
Feb  1 19:30:30 joe acpid: client 24901[0:0] has disconnected
Feb  1 19:30:30 joe acpid: client 24891[0:0] has disconnected
Feb  1 19:30:30 joe acpid: client 24905[0:0] has disconnected
Feb  1 19:30:30 joe acpid: client 24900[0:0] has disconnected
Feb  1 19:30:30 joe acpid: client 24908[0:0] has disconnected
Feb  1 19:30:30 joe acpid: client 24907[0:0] has disconnected
Feb  1 19:30:30 joe acpid: client connected from 25339[0:0]
Feb  1 19:30:30 joe acpid: 1 client rule loaded
Feb  1 19:30:30 joe acpid: client connected from 25340[0:0]
Feb  1 19:30:30 joe acpid: 1 client rule loaded
Feb  1 19:30:30 joe acpid: client connected from 25351[0:0]
Feb  1 19:30:30 joe acpid: 1 client rule loaded
Feb  1 19:30:30 joe acpid: client connected from 25343[0:0]
Feb  1 19:30:30 joe acpid: 1 client rule loaded
Feb  1 19:30:30 joe acpid: client connected from 25341[0:0]
Feb  1 19:30:30 joe acpid: 1 client rule loaded
Feb  1 19:30:30 joe acpid: client connected from 25352[0:0]
Feb  1 19:30:30 joe acpid: 1 client rule loaded
Feb  1 19:30:30 joe acpid: client connected from 25342[0:0]
Feb  1 19:30:30 joe acpid: 1 client rule loaded
Feb  1 19:30:30 joe acpid: client connected from 25344[0:0]
Feb  1 19:30:30 joe acpid: 1 client rule loaded
Feb  1 19:30:30 joe acpid: client connected from 25348[0:0]
Feb  1 19:30:30 joe acpid: 1 client rule loaded
Feb  1 19:30:30 joe acpid: client connected from 25350[0:0]
Feb  1 19:30:30 joe acpid: 1 client rule loaded
Feb  1 19:30:30 joe acpid: client connected from 25345[0:0]
Feb  1 19:30:30 joe acpid: 1 client rule loaded
Feb  1 19:30:48 joe acpid: client 25339[0:0] has disconnected
Feb  1 19:30:48 joe acpid: client 25340[0:0] has disconnected
Feb  1 19:30:48 joe acpid: client 25351[0:0] has disconnected
Feb  1 19:30:48 joe acpid: client 25343[0:0] has disconnected
Feb  1 19:30:48 joe acpid: client 25341[0:0] has disconnected
Feb  1 19:30:48 joe acpid: client 25352[0:0] has disconnected
Feb  1 19:30:48 joe acpid: client 25342[0:0] has disconnected
Feb  1 19:30:48 joe acpid: client 25344[0:0] has disconnected
Feb  1 19:30:48 joe acpid: client 25348[0:0] has disconnected
Feb  1 19:30:48 joe acpid: client 25350[0:0] has disconnected
Feb  1 19:30:48 joe acpid: client 25345[0:0] has disconnected
Feb  1 19:30:51 joe acpid: client connected from 25823[0:0]
Feb  1 19:30:51 joe acpid: 1 client rule loaded
Feb  1 19:30:51 joe acpid: client connected from 25824[0:0]
Feb  1 19:30:51 joe acpid: 1 client rule loaded
Feb  1 19:30:51 joe acpid: client connected from 25822[0:0]
Feb  1 19:30:51 joe acpid: 1 client rule loaded
Feb  1 19:30:51 joe acpid: client connected from 25819[0:0]
Feb  1 19:30:51 joe acpid: 1 client rule loaded
Feb  1 19:30:51 joe acpid: client 25824[0:0] has disconnected
Feb  1 19:30:51 joe acpid: client 25822[0:0] has disconnected
Feb  1 19:30:51 joe acpid: client 25819[0:0] has disconnected
Feb  1 19:30:51 joe acpid: client connected from 25820[0:0]
Feb  1 19:30:51 joe acpid: 1 client rule loaded
Feb  1 19:30:51 joe acpid: client 25823[0:0] has disconnected
Feb  1 19:30:51 joe acpid: client 25820[0:0] has disconnected
Feb  1 19:30:51 joe acpid: client connected from 25821[0:0]
Feb  1 19:30:51 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client 25821[0:0] has disconnected
Feb  1 19:31:08 joe acpid: client connected from 26293[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26294[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26302[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26299[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26295[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26296[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26297[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26300[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26311[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26312[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26301[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26317[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26318[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26315[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26323[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26325[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26316[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26327[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26328[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26329[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26332[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26334[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26333[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26326[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26330[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client 26293[0:0] has disconnected
Feb  1 19:31:08 joe acpid: client connected from 26324[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client 26297[0:0] has disconnected
Feb  1 19:31:08 joe acpid: client connected from 26331[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client 26299[0:0] has disconnected
Feb  1 19:31:08 joe acpid: client 26295[0:0] has disconnected
Feb  1 19:31:08 joe acpid: client connected from 26348[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26349[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client 26300[0:0] has disconnected
Feb  1 19:31:08 joe acpid: client connected from 26347[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26350[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client 26294[0:0] has disconnected
Feb  1 19:31:08 joe acpid: client 26302[0:0] has disconnected
Feb  1 19:31:08 joe acpid: client 26296[0:0] has disconnected
Feb  1 19:31:08 joe acpid: client 26311[0:0] has disconnected
Feb  1 19:31:08 joe acpid: client 26312[0:0] has disconnected
Feb  1 19:31:08 joe acpid: client 26301[0:0] has disconnected
Feb  1 19:31:08 joe acpid: client 26318[0:0] has disconnected
Feb  1 19:31:08 joe acpid: client connected from 26351[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:08 joe acpid: client connected from 26352[0:0]
Feb  1 19:31:08 joe acpid: 1 client rule loaded
Feb  1 19:31:29 joe acpid: client 26317[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26315[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26323[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26325[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26316[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26327[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26328[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26329[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26332[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26334[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26333[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26326[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26330[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26324[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26331[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26348[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26349[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26347[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26350[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26351[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client 26352[0:0] has disconnected
Feb  1 19:31:29 joe acpid: client connected from 26905[0:0]
Feb  1 19:31:29 joe acpid: 1 client rule loaded
Feb  1 19:31:29 joe acpid: client connected from 26915[0:0]
Feb  1 19:31:29 joe acpid: 1 client rule loaded
Feb  1 19:31:29 joe acpid: client connected from 26916[0:0]
Feb  1 19:31:29 joe acpid: 1 client rule loaded
Feb  1 19:31:29 joe acpid: client connected from 26917[0:0]
Feb  1 19:31:29 joe acpid: 1 client rule loaded
Feb  1 19:31:29 joe acpid: client connected from 26912[0:0]
Feb  1 19:31:29 joe acpid: 1 client rule loaded
Feb  1 19:31:29 joe acpid: client connected from 26913[0:0]
Feb  1 19:31:29 joe acpid: 1 client rule loaded
Feb  1 19:31:29 joe acpid: client connected from 26910[0:0]
Feb  1 19:31:29 joe acpid: 1 client rule loaded
Feb  1 19:31:29 joe acpid: client connected from 26909[0:0]
Feb  1 19:31:29 joe acpid: 1 client rule loaded
Feb  1 19:31:29 joe acpid: client connected from 26914[0:0]
Feb  1 19:31:29 joe acpid: 1 client rule loaded
Feb  1 19:31:29 joe acpid: client connected from 26918[0:0]
Feb  1 19:31:29 joe acpid: 1 client rule loaded
Feb  1 19:31:29 joe acpid: client connected from 26920[0:0]
Feb  1 19:31:29 joe acpid: 1 client rule loaded
Feb  1 19:31:29 joe acpid: client connected from 26908[0:0]
Feb  1 19:31:29 joe acpid: 1 client rule loaded
Feb  1 19:31:29 joe acpid: client connected from 26906[0:0]
Feb  1 19:31:29 joe acpid: 1 client rule loaded
Feb  1 19:31:29 joe acpid: client connected from 26911[0:0]
Feb  1 19:31:29 joe acpid: 1 client rule loaded
Feb  1 19:31:29 joe acpid: client connected from 26919[0:0]
Feb  1 19:31:29 joe acpid: 1 client rule loaded
Feb  1 19:31:30 joe pulseaudio[26953]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:31:30 joe dbus[1463]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Feb  1 19:31:37 joe dbus[1463]: [system] Activated service 'org.freedesktop.PackageKit' failed: Process /usr/lib/dbus-1.0/dbus-daemon-launch-helper received signal 11
Feb  1 19:31:37 joe kernel: [18921.802652] packagekitd[26960]: segfault at 8 ip 0000000008057124 sp 00000000fff569c0 error 4 in packagekitd[8048000+49000]
Feb  1 19:31:37 joe pulseaudio[27077]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:31:43 joe gnome-session[26373]: WARNING: Failed to start app: Unable to start application: Kindprozess »/usr/lib/gnome-volume-manager/gnome-volume-manager« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) 
Feb  1 19:31:43 joe gnome-session[26373]: WARNING: Failed to start app: Unable to start application: Kindprozess »beagle-search« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) 
Feb  1 19:31:43 joe pulseaudio[27209]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:31:43 joe gnome-session[26373]: WARNING: Failed to start app: Unable to start application: Kindprozess »beagled« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) 
Feb  1 19:31:46 joe pulseaudio[27270]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:32:33 joe pulseaudio[27276]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:32:33 joe gdm-simple-slave[26411]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24967]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24409]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26416]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23530]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23971]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24966]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26398]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26955]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display37732: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24964]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26408]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23981]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23551]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26941]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display37724: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23533]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23975]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23969]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23543]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23550]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23557]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24927]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23545]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26392]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24971]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23554]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26401]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23974]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23976]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26363]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25364]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23555]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26402]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26936]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display37719: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25834]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24931]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23534]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24961]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26945]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display37726: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25370]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26419]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25836]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25371]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23531]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23541]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26403]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26414]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24935]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25366]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26361]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24928]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26938]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display37721: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26415]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25831]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25365]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23552]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23532]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23536]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26410]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25368]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26406]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26413]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23546]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24936]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23966]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23970]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24962]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26404]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26944]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display37725: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26424]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26946]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display37727: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23548]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24970]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24968]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23538]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24411]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24406]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26377]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26420]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23556]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24958]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25362]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23967]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24926]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26949]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display37728: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23968]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23544]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24934]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24937]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24930]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25363]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25832]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25835]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24957]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26937]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display37720: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24410]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24933]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26384]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24960]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26375]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24963]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23549]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25833]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23542]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24932]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26417]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23537]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23980]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26405]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24407]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26362]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25367]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23540]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26940]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display37723: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26950]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display37729: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26400]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26939]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display37722: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24965]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23977]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24969]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26412]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26366]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24925]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23553]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23535]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25369]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23973]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26935]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display37718: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26418]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26407]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23539]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26409]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24912]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24924]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26952]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display37730: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25361]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23547]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24959]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26954]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display37731: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23978]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[24408]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[26399]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23979]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[25900]: WARNING: Failed to get value: 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. 
Feb  1 19:32:33 joe gdm-simple-slave[23972]: WARNING: Failed to get value: 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. 
Feb  1 19:32:34 joe pulseaudio[27317]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:32:34 joe pulseaudio[27322]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:32:34 joe acpid: client 26905[0:0] has disconnected
Feb  1 19:32:34 joe pulseaudio[27518]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:32:34 joe goa[27521]: goa-daemon version 3.2.1 starting [main.c:112, main()]
Feb  1 19:32:34 joe gdm-simple-slave[26411]: WARNING: Failed to get value: 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. 
Feb  1 19:32:34 joe gdm-simple-slave[26398]: WARNING: Failed to get value: 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. 
Feb  1 19:32:34 joe gdm-simple-slave[26416]: WARNING: Failed to get value: 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. 
Feb  1 19:32:34 joe acpid: client 26915[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client 26916[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client 26917[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client 26912[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client 26913[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client 26910[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client 26909[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client 26914[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client 26918[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client 26920[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client 26908[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client 26906[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client 26911[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client 26919[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client connected from 27290[0:0]
Feb  1 19:32:34 joe acpid: 1 client rule loaded
Feb  1 19:32:34 joe acpid: client 27290[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client connected from 27286[0:0]
Feb  1 19:32:34 joe acpid: 1 client rule loaded
Feb  1 19:32:34 joe acpid: client 27286[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client connected from 27289[0:0]
Feb  1 19:32:34 joe acpid: 1 client rule loaded
Feb  1 19:32:34 joe acpid: client 27289[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client connected from 27285[0:0]
Feb  1 19:32:34 joe acpid: 1 client rule loaded
Feb  1 19:32:34 joe acpid: client 27285[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client connected from 27288[0:0]
Feb  1 19:32:34 joe acpid: 1 client rule loaded
Feb  1 19:32:34 joe acpid: client 27288[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client connected from 27284[0:0]
Feb  1 19:32:34 joe acpid: 1 client rule loaded
Feb  1 19:32:34 joe acpid: client 27284[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client connected from 27287[0:0]
Feb  1 19:32:34 joe acpid: 1 client rule loaded
Feb  1 19:32:34 joe acpid: client 27287[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client connected from 27362[0:0]
Feb  1 19:32:34 joe acpid: 1 client rule loaded
Feb  1 19:32:34 joe acpid: client 27362[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client connected from 27363[0:0]
Feb  1 19:32:34 joe acpid: 1 client rule loaded
Feb  1 19:32:34 joe acpid: client 27363[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client connected from 27361[0:0]
Feb  1 19:32:34 joe acpid: 1 client rule loaded
Feb  1 19:32:34 joe acpid: client 27361[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client connected from 27360[0:0]
Feb  1 19:32:34 joe acpid: 1 client rule loaded
Feb  1 19:32:34 joe acpid: client 27360[0:0] has disconnected
Feb  1 19:32:34 joe acpid: client connected from 27364[0:0]
Feb  1 19:32:34 joe acpid: 1 client rule loaded
Feb  1 19:32:41 joe gdm-simple-slave[27472]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38028: 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. 
Feb  1 19:32:41 joe gdm-simple-slave[27474]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38029: 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. 
Feb  1 19:32:41 joe gdm-simple-slave[27476]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38031: 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. 
Feb  1 19:32:41 joe gdm-simple-slave[27475]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38030: 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. 
Feb  1 19:32:41 joe gdm-simple-slave[27485]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38038: 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. 
Feb  1 19:32:42 joe gdm-simple-slave[27483]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38036: 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. 
Feb  1 19:32:42 joe gdm-simple-slave[27478]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38033: 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. 
Feb  1 19:32:42 joe gdm-simple-slave[27484]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38037: 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. 
Feb  1 19:32:42 joe gdm-simple-slave[27477]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38032: 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. 
Feb  1 19:32:42 joe gdm-simple-slave[27481]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38034: 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. 
Feb  1 19:32:42 joe gdm-simple-slave[27482]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38035: 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. 
Feb  1 19:32:42 joe gdm-simple-slave[27486]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38039: 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. 
Feb  1 19:32:44 joe pulseaudio[27571]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:32:44 joe pulseaudio[27572]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:32:47 joe dbus[1463]: [system] Activating service name='org.gnome.SettingsDaemon.DateTimeMechanism' (using servicehelper)
Feb  1 19:32:48 joe acpid: client 27364[0:0] has disconnected
Feb  1 19:32:52 joe acpid: client connected from 27731[0:0]
Feb  1 19:32:52 joe acpid: 1 client rule loaded
Feb  1 19:32:52 joe acpid: client 27731[0:0] has disconnected
Feb  1 19:32:52 joe acpid: client connected from 27730[0:0]
Feb  1 19:32:52 joe acpid: 1 client rule loaded
Feb  1 19:33:24 joe dbus[1463]: [system] Successfully activated service 'org.gnome.SettingsDaemon.DateTimeMechanism'
Feb  1 19:33:25 joe acpid: client connected from 27696[0:0]
Feb  1 19:33:25 joe acpid: 1 client rule loaded
Feb  1 19:33:25 joe acpid: client connected from 27713[0:0]
Feb  1 19:33:25 joe pulseaudio[27914]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:33:25 joe acpid: 1 client rule loaded
Feb  1 19:33:25 joe acpid: client connected from 27648[0:0]
Feb  1 19:33:25 joe acpid: 1 client rule loaded
Feb  1 19:33:25 joe acpid: client connected from 27697[0:0]
Feb  1 19:33:25 joe acpid: 1 client rule loaded
Feb  1 19:33:25 joe pulseaudio[27916]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:33:25 joe acpid: client connected from 27665[0:0]
Feb  1 19:33:25 joe gdm-simple-slave[26392]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[26406]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[26361]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[26414]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[26366]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[26402]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[26362]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[26424]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[26399]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[26417]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[26377]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[26410]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[26375]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[26420]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[26418]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27798]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38103: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[26415]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27888]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38110: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[26405]: WARNING: Failed to get value: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27899]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38118: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27898]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38117: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27902]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38121: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27900]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38119: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27907]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38126: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27906]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38125: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27908]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38127: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27904]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38123: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27909]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38128: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27903]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38122: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27910]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38129: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27901]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38120: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27905]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38124: 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. 
Feb  1 19:33:25 joe pulseaudio[27930]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:33:25 joe dbus[1463]: [system] Activating service name='org.debian.apt' (using servicehelper)
Feb  1 19:33:25 joe gdm-simple-slave[27897]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38116: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27895]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38114: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27890]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38111: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27896]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38115: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27891]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38112: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27879]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38104: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27887]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38109: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27886]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38108: 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. 
Feb  1 19:33:25 joe gdm-simple-slave[27884]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38106: 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. 
Feb  1 19:33:26 joe gdm-simple-slave[27893]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38113: 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. 
Feb  1 19:33:26 joe gdm-simple-slave[27880]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38105: 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. 
Feb  1 19:33:26 joe gdm-simple-slave[27552]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:33:26 joe gdm-simple-slave[27885]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display38107: 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. 
Feb  1 19:33:26 joe gdm-simple-slave[26404]: WARNING: Failed to get value: 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. 
Feb  1 19:33:26 joe gdm-simple-slave[26384]: WARNING: Failed to get value: 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. 
Feb  1 19:33:26 joe gdm-simple-slave[26400]: WARNING: Failed to get value: 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. 
Feb  1 19:33:26 joe gdm-simple-slave[26407]: WARNING: Failed to get value: 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. 
Feb  1 19:33:26 joe gdm-simple-slave[26419]: WARNING: Failed to get value: 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. 
Feb  1 19:33:26 joe gdm-simple-slave[26403]: WARNING: Failed to get value: 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. 
Feb  1 19:33:26 joe gdm-simple-slave[26363]: WARNING: Failed to get value: 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. 
Feb  1 19:33:26 joe gdm-simple-slave[26409]: WARNING: Failed to get value: 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. 
Feb  1 19:33:26 joe gdm-simple-slave[26412]: WARNING: Failed to get value: 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. 
Feb  1 19:33:26 joe gdm-simple-slave[26408]: WARNING: Failed to get value: 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. 
Feb  1 19:33:26 joe gdm-simple-slave[26413]: WARNING: Failed to get value: 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. 
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe gdm-simple-slave[26401]: WARNING: Failed to get value: 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. 
Feb  1 19:33:26 joe /USR/SBIN/CRON[27974]: (Debian-exim) CMD ([ -x /usr/share/sa-exim/greylistclean ] && /usr/share/sa-exim/greylistclean)
Feb  1 19:33:26 joe acpid: client 27730[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client 27696[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client 27713[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client 27648[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client 27697[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client 27665[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client connected from 27666[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client 27666[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client connected from 27670[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client 27670[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client connected from 27667[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client 27667[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client connected from 27659[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client 27659[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client connected from 27722[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client 27722[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client connected from 27674[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client 27674[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client connected from 27688[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client 27688[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client connected from 27709[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client 27709[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client connected from 27711[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client 27711[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client connected from 27675[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client 27675[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client connected from 27686[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client 27686[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client connected from 27669[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client 27669[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client connected from 27684[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client 27684[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client connected from 27714[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27710[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27641[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27646[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27687[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27658[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27723[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27639[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27691[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27692[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27642[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27664[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27649[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27650[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27638[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27634[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27656[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27637[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27640[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27657[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27689[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27647[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27643[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27739[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27737[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27724[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27726[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27673[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27738[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27725[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27693[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27645[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27712[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27690[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27698[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27715[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27635[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27699[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27655[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27671[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27736[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27636[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client 27641[0:0] has disconnected
Feb  1 19:33:26 joe acpid: client connected from 27732[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27685[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27701[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27717[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27654[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27700[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27695[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27729[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27672[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27694[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27716[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:26 joe acpid: client connected from 27668[0:0]
Feb  1 19:33:26 joe acpid: 1 client rule loaded
Feb  1 19:33:33 joe sa-exim[27981]: Removed 0 of 0 greylist tuplets in 0 seconds 
Feb  1 19:33:33 joe sa-exim[27981]: Removed 0 of 0 greylist directories in 0 seconds 
Feb  1 19:33:33 joe pulseaudio[28022]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:33:38 joe pulseaudio[28137]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:33:42 joe pulseaudio[28214]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:33:44 joe dbus[1463]: [system] Failed to activate service 'org.debian.apt': timed out
Feb  1 19:33:48 joe pulseaudio[28423]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:33:49 joe AptDaemon: INFO: Initializing daemon
Feb  1 19:33:52 joe pulseaudio[28516]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:33:53 joe pulseaudio[28540]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:33:57 joe pulseaudio[28637]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:33:58 joe pulseaudio[28662]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:02 joe pulseaudio[28757]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:03 joe pulseaudio[28782]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:07 joe pulseaudio[28883]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:08 joe pulseaudio[28907]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:12 joe pulseaudio[29008]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:13 joe pulseaudio[29033]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:17 joe pulseaudio[29123]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:18 joe pulseaudio[29145]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:22 joe pulseaudio[29240]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:23 joe pulseaudio[29265]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:27 joe pulseaudio[29365]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:28 joe pulseaudio[29389]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:32 joe pulseaudio[29491]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:33 joe pulseaudio[29516]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:37 joe pulseaudio[29616]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:38 joe pulseaudio[29640]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:42 joe pulseaudio[29733]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:43 joe pulseaudio[29757]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:47 joe pulseaudio[29859]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:48 joe pulseaudio[29882]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:53 joe pulseaudio[29984]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:53 joe pulseaudio[30009]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:58 joe pulseaudio[30108]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:34:58 joe pulseaudio[30133]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:03 joe pulseaudio[30228]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:03 joe pulseaudio[30253]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:08 joe pulseaudio[30353]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:08 joe pulseaudio[30377]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:13 joe pulseaudio[30476]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:13 joe pulseaudio[30501]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:18 joe pulseaudio[30602]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:18 joe pulseaudio[30625]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:20 joe acpid: client 27714[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27710[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27646[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27687[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27658[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27723[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27639[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27691[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27692[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27642[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27664[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27649[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27650[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27638[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27634[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27656[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27637[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27640[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27657[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27689[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27647[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27643[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27739[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27737[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27724[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27726[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27673[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27738[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27725[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27693[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27645[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27712[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27690[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27698[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27715[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27635[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27699[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27655[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27671[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27736[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27636[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27732[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27685[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27701[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27717[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27654[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27700[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27695[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27729[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27672[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27694[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27716[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client 27668[0:0] has disconnected
Feb  1 19:35:20 joe acpid: client connected from 30660[0:0]
Feb  1 19:35:20 joe acpid: 1 client rule loaded
Feb  1 19:35:22 joe pulseaudio[30700]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:23 joe pulseaudio[30723]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:27 joe pulseaudio[30812]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:29 joe pulseaudio[30846]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:32 joe pulseaudio[30914]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:34 joe pulseaudio[30970]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:37 joe pulseaudio[31037]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:39 joe pulseaudio[31093]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:42 joe pulseaudio[31153]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:45 joe pulseaudio[31208]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:47 joe pulseaudio[31276]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:49 joe pulseaudio[31330]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:52 joe pulseaudio[31399]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:55 joe pulseaudio[31454]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:35:57 joe pulseaudio[31522]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:00 joe pulseaudio[31578]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:02 joe acpid: client 30660[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client connected from 31635[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31633[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31634[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31640[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client 31633[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client connected from 31653[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31652[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31644[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31650[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31642[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31639[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31643[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31646[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31648[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31651[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31641[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31645[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31647[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31654[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client 31635[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31634[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client connected from 31670[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31681[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31680[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31678[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31676[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31687[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31679[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31691[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31682[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31685[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31688[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31689[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31690[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31669[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31686[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31677[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31673[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31675[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31683[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31684[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client 31640[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client connected from 31674[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31672[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe pulseaudio[31717]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:02 joe acpid: client 31653[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31652[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31644[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31650[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31642[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31639[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31643[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31646[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31648[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31651[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31641[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31645[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31647[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31654[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31681[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client connected from 31727[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31725[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31721[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31714[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31715[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31729[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31726[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31720[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31722[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client connected from 31723[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client 31683[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client connected from 31728[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:02 joe acpid: client 31669[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31686[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client 31673[0:0] has disconnected
Feb  1 19:36:02 joe acpid: client connected from 31724[0:0]
Feb  1 19:36:02 joe acpid: 1 client rule loaded
Feb  1 19:36:09 joe pulseaudio[31779]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:09 joe pulseaudio[31839]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:09 joe pulseaudio[3668]: [pulseaudio] module-console-kit.c: GetUnixUser() call failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetUnixUser" with signature "" on interface "org.freedesktop.ConsoleKit.Session" doesn't exist
Feb  1 19:36:12 joe pulseaudio[31953]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:12 joe pulseaudio[31952]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:17 joe pulseaudio[32075]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:17 joe pulseaudio[32076]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:20 joe acpid: client 31670[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31680[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31678[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31676[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31687[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31679[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31691[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31682[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31685[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31688[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31689[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31690[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31677[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31675[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31684[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31674[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31672[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31727[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31725[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31721[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31714[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31715[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31729[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31726[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31720[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31722[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31723[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31728[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client 31724[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client connected from 32129[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client 32129[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client connected from 32127[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client 32127[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client connected from 32128[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client 32128[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client connected from 32135[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client 32135[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client connected from 32131[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client 32131[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client connected from 32138[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client 32138[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client connected from 32136[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client 32136[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client connected from 32126[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client 32126[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client connected from 32134[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client 32134[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client connected from 32143[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client 32143[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client connected from 32140[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client 32140[0:0] has disconnected
Feb  1 19:36:20 joe acpid: client connected from 32139[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client connected from 32142[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client connected from 32137[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client connected from 32145[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client connected from 32144[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client connected from 32141[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client connected from 32157[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client connected from 32147[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:20 joe acpid: client connected from 32146[0:0]
Feb  1 19:36:20 joe acpid: 1 client rule loaded
Feb  1 19:36:22 joe pulseaudio[32223]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:22 joe pulseaudio[32222]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:27 joe pulseaudio[32344]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:27 joe pulseaudio[32343]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:30 joe gdm-simple-slave[31774]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39880: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31775]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39881: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31776]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39882: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31778]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39883: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31780]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39884: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31781]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39885: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31782]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39886: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31783]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39887: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31784]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39888: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31785]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39889: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31786]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39890: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31787]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39891: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31788]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39892: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31790]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39894: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31792]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39896: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31794]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39898: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31797]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39900: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31799]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39902: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31800]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39903: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31801]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39904: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31789]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39893: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31791]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39895: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31793]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39897: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31796]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39899: 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. 
Feb  1 19:36:30 joe gdm-simple-slave[31798]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39901: 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. 
Feb  1 19:36:32 joe pulseaudio[32466]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:32 joe pulseaudio[32467]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:33 joe gdm-simple-slave[31860]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display39944: 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. 
Feb  1 19:36:37 joe pulseaudio[32587]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:37 joe pulseaudio[32586]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:38 joe acpid: client 32139[0:0] has disconnected
Feb  1 19:36:38 joe acpid: client 32142[0:0] has disconnected
Feb  1 19:36:38 joe acpid: client 32137[0:0] has disconnected
Feb  1 19:36:38 joe acpid: client 32145[0:0] has disconnected
Feb  1 19:36:38 joe acpid: client 32144[0:0] has disconnected
Feb  1 19:36:38 joe acpid: client 32141[0:0] has disconnected
Feb  1 19:36:38 joe acpid: client 32157[0:0] has disconnected
Feb  1 19:36:38 joe acpid: client 32147[0:0] has disconnected
Feb  1 19:36:38 joe acpid: client 32146[0:0] has disconnected
Feb  1 19:36:38 joe acpid: client connected from 32627[0:0]
Feb  1 19:36:38 joe acpid: 1 client rule loaded
Feb  1 19:36:38 joe acpid: client connected from 32631[0:0]
Feb  1 19:36:38 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32623[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32621[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32636[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32630[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32624[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32639[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32620[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32638[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32634[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32626[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32635[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32637[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32625[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32632[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32619[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32629[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32617[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32616[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32628[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:39 joe acpid: client connected from 32618[0:0]
Feb  1 19:36:39 joe acpid: 1 client rule loaded
Feb  1 19:36:41 joe pulseaudio[3668]: [pulseaudio] module-console-kit.c: GetUnixUser() call failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetUnixUser" with signature "" on interface "org.freedesktop.ConsoleKit.Session" doesn't exist
Feb  1 19:36:42 joe pulseaudio[329]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:42 joe pulseaudio[330]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:47 joe pulseaudio[452]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:47 joe pulseaudio[453]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:52 joe pulseaudio[574]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:52 joe pulseaudio[575]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:57 joe pulseaudio[700]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:57 joe pulseaudio[701]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:36:58 joe acpid: client 32627[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32631[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32623[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32621[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32636[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32630[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32624[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32639[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32620[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32638[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32634[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32626[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32635[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32637[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32625[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32632[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32619[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32629[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32617[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32616[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32628[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client 32618[0:0] has disconnected
Feb  1 19:36:58 joe acpid: client connected from 711[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 718[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 712[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 715[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 721[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 723[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 725[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 726[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 720[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 735[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 738[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 733[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 716[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 739[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 741[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 713[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 736[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 730[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 734[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 743[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 745[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 748[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 732[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 747[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 740[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 749[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 744[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 799[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 815[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 779[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 728[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 724[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 816[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 731[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 722[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 729[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 777[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 778[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 780[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 714[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 790[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 786[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 791[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 781[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 787[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 794[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 788[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 792[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 782[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 783[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 795[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 785[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 818[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 796[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 797[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:36:58 joe acpid: client connected from 817[0:0]
Feb  1 19:36:58 joe acpid: 1 client rule loaded
Feb  1 19:37:05 joe pulseaudio[900]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:05 joe pulseaudio[901]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:06 joe gdm-simple-slave[32766]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40323: 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. 
Feb  1 19:37:06 joe gdm-simple-slave[32767]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40324: 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. 
Feb  1 19:37:06 joe gdm-simple-slave[302]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40325: 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. 
Feb  1 19:37:06 joe gdm-simple-slave[303]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40326: 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. 
Feb  1 19:37:06 joe gdm-simple-slave[304]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40327: 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. 
Feb  1 19:37:06 joe gdm-simple-slave[305]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40328: 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. 
Feb  1 19:37:06 joe gdm-simple-slave[306]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40329: 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. 
Feb  1 19:37:06 joe gdm-simple-slave[307]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40330: 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. 
Feb  1 19:37:06 joe gdm-simple-slave[308]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40331: 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. 
Feb  1 19:37:06 joe gdm-simple-slave[309]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40332: 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. 
Feb  1 19:37:06 joe gdm-simple-slave[311]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40333: 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. 
Feb  1 19:37:06 joe gdm-simple-slave[313]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40334: 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. 
Feb  1 19:37:06 joe gdm-simple-slave[314]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40335: 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. 
Feb  1 19:37:06 joe gdm-simple-slave[316]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40336: 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. 
Feb  1 19:37:06 joe gdm-simple-slave[317]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40337: 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. 
Feb  1 19:37:06 joe gdm-simple-slave[318]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40338: 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. 
Feb  1 19:37:07 joe gdm-simple-slave[319]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display40339: 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. 
Feb  1 19:37:09 joe pulseaudio[1060]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:09 joe pulseaudio[1058]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:14 joe pulseaudio[1193]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:14 joe pulseaudio[1192]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:15 joe gdm-simple-slave[1234]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 19:37:19 joe pulseaudio[1337]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:19 joe pulseaudio[1338]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:24 joe pulseaudio[1465]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:24 joe pulseaudio[1466]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:29 joe pulseaudio[1605]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:29 joe pulseaudio[1606]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:34 joe pulseaudio[1724]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:34 joe pulseaudio[1725]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:39 joe pulseaudio[1838]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:39 joe pulseaudio[1839]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:44 joe pulseaudio[1960]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:44 joe pulseaudio[1962]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:49 joe pulseaudio[2080]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:49 joe pulseaudio[2081]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:54 joe pulseaudio[2212]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:54 joe pulseaudio[2213]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:59 joe pulseaudio[2397]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:37:59 joe pulseaudio[2396]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:04 joe pulseaudio[2522]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:04 joe pulseaudio[2525]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:09 joe pulseaudio[2646]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:09 joe pulseaudio[2645]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:14 joe pulseaudio[2767]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:14 joe pulseaudio[2766]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:17 joe acpid: client 711[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 718[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 712[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 715[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 721[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 723[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 725[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 726[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 720[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 735[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 738[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 733[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 716[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 739[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 741[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 713[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 736[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 730[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 734[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 743[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 745[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 748[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 732[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 747[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 740[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 749[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 744[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 799[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 815[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 779[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 728[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 724[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 816[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 731[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 722[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 729[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 777[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 778[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 780[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 714[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 790[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 786[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 791[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 781[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 787[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 794[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 788[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 792[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 782[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 783[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 795[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 785[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 818[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 796[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 797[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client 817[0:0] has disconnected
Feb  1 19:38:17 joe acpid: client connected from 2819[0:0]
Feb  1 19:38:17 joe acpid: 1 client rule loaded
Feb  1 19:38:19 joe pulseaudio[2883]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:19 joe pulseaudio[2882]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:24 joe pulseaudio[3009]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:24 joe pulseaudio[3008]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:29 joe pulseaudio[3128]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:29 joe pulseaudio[3129]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:34 joe pulseaudio[3247]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:34 joe pulseaudio[3246]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:39 joe pulseaudio[3359]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:39 joe pulseaudio[3360]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:44 joe pulseaudio[3484]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:44 joe pulseaudio[3483]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:49 joe pulseaudio[3627]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:49 joe pulseaudio[3626]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:54 joe pulseaudio[3778]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:54 joe pulseaudio[3779]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:38:57 joe acpid: client 2819[0:0] has disconnected
Feb  1 19:38:57 joe acpid: client connected from 3857[0:0]
Feb  1 19:38:57 joe acpid: 1 client rule loaded
Feb  1 19:38:57 joe acpid: client 3857[0:0] has disconnected
Feb  1 19:38:57 joe acpid: client connected from 3858[0:0]
Feb  1 19:38:57 joe acpid: 1 client rule loaded
Feb  1 19:38:57 joe acpid: client connected from 3861[0:0]
Feb  1 19:38:57 joe acpid: 1 client rule loaded
Feb  1 19:38:57 joe acpid: client connected from 3862[0:0]
Feb  1 19:38:57 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3864[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3870[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3872[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3868[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3873[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3875[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3869[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3867[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3876[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3865[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3877[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3882[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3881[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3880[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client 3858[0:0] has disconnected
Feb  1 19:38:58 joe acpid: client connected from 3874[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3866[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3879[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3878[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3883[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3871[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3884[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:38:58 joe acpid: client connected from 3895[0:0]
Feb  1 19:38:58 joe acpid: 1 client rule loaded
Feb  1 19:39:03 joe pulseaudio[3936]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:03 joe pulseaudio[3937]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:04 joe /USR/SBIN/CRON[3968]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \; -delete)
Feb  1 19:39:06 joe pulseaudio[4056]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:06 joe pulseaudio[4055]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:12 joe pulseaudio[4170]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:12 joe pulseaudio[4171]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:18 joe pulseaudio[4278]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:18 joe pulseaudio[4277]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:19 joe acpid: client 3861[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3862[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3864[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3870[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3872[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3868[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3873[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3875[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3869[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3867[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3876[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3865[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3877[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3882[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3881[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3880[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3874[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3866[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3879[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3878[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3883[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3871[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3884[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client 3895[0:0] has disconnected
Feb  1 19:39:19 joe acpid: client connected from 4342[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4339[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4335[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4326[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4324[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4332[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4343[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4334[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4348[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4325[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4341[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4347[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4337[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4338[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4344[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4340[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4345[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4327[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4336[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:19 joe acpid: client connected from 4346[0:0]
Feb  1 19:39:19 joe acpid: 1 client rule loaded
Feb  1 19:39:25 joe pulseaudio[4451]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:25 joe pulseaudio[4450]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:28 joe pulseaudio[4557]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:28 joe pulseaudio[4556]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:34 joe pulseaudio[4658]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:34 joe pulseaudio[4659]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:39 joe pulseaudio[4776]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:39 joe pulseaudio[4775]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:40 joe acpid: client 4342[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4339[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4335[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4326[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4324[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4332[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4343[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4334[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4348[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4325[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4341[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4347[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4337[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4338[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4344[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4340[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4345[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4327[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4336[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4346[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client connected from 4801[0:0]
Feb  1 19:39:40 joe acpid: 1 client rule loaded
Feb  1 19:39:40 joe acpid: client 4801[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client connected from 4803[0:0]
Feb  1 19:39:40 joe acpid: 1 client rule loaded
Feb  1 19:39:40 joe acpid: client connected from 4800[0:0]
Feb  1 19:39:40 joe acpid: 1 client rule loaded
Feb  1 19:39:40 joe acpid: client connected from 4808[0:0]
Feb  1 19:39:40 joe acpid: 1 client rule loaded
Feb  1 19:39:40 joe acpid: client connected from 4804[0:0]
Feb  1 19:39:40 joe acpid: 1 client rule loaded
Feb  1 19:39:40 joe acpid: client connected from 4805[0:0]
Feb  1 19:39:40 joe acpid: 1 client rule loaded
Feb  1 19:39:40 joe acpid: client connected from 4806[0:0]
Feb  1 19:39:40 joe acpid: 1 client rule loaded
Feb  1 19:39:40 joe acpid: client connected from 4811[0:0]
Feb  1 19:39:40 joe acpid: 1 client rule loaded
Feb  1 19:39:40 joe acpid: client connected from 4810[0:0]
Feb  1 19:39:40 joe acpid: 1 client rule loaded
Feb  1 19:39:40 joe acpid: client connected from 4817[0:0]
Feb  1 19:39:40 joe acpid: 1 client rule loaded
Feb  1 19:39:40 joe acpid: client connected from 4820[0:0]
Feb  1 19:39:40 joe acpid: 1 client rule loaded
Feb  1 19:39:40 joe acpid: client connected from 4821[0:0]
Feb  1 19:39:40 joe acpid: 1 client rule loaded
Feb  1 19:39:40 joe acpid: client 4803[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4800[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4808[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4804[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4805[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4806[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4811[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4810[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4817[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4820[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client 4821[0:0] has disconnected
Feb  1 19:39:40 joe acpid: client connected from 4816[0:0]
Feb  1 19:39:40 joe acpid: 1 client rule loaded
Feb  1 19:39:40 joe acpid: client connected from 4830[0:0]
Feb  1 19:39:40 joe acpid: 1 client rule loaded
Feb  1 19:39:40 joe acpid: client connected from 4829[0:0]
Feb  1 19:39:40 joe acpid: 1 client rule loaded
Feb  1 19:39:41 joe acpid: client connected from 4828[0:0]
Feb  1 19:39:41 joe acpid: 1 client rule loaded
Feb  1 19:39:41 joe acpid: client connected from 4832[0:0]
Feb  1 19:39:41 joe acpid: 1 client rule loaded
Feb  1 19:39:41 joe acpid: client connected from 4824[0:0]
Feb  1 19:39:41 joe acpid: 1 client rule loaded
Feb  1 19:39:41 joe acpid: client connected from 4831[0:0]
Feb  1 19:39:41 joe acpid: 1 client rule loaded
Feb  1 19:39:41 joe acpid: client connected from 4826[0:0]
Feb  1 19:39:41 joe acpid: 1 client rule loaded
Feb  1 19:39:41 joe acpid: client connected from 4834[0:0]
Feb  1 19:39:41 joe acpid: 1 client rule loaded
Feb  1 19:39:41 joe acpid: client connected from 4837[0:0]
Feb  1 19:39:41 joe acpid: 1 client rule loaded
Feb  1 19:39:41 joe acpid: client connected from 4839[0:0]
Feb  1 19:39:41 joe acpid: 1 client rule loaded
Feb  1 19:39:41 joe acpid: client connected from 4822[0:0]
Feb  1 19:39:41 joe acpid: 1 client rule loaded
Feb  1 19:39:41 joe acpid: client connected from 4818[0:0]
Feb  1 19:39:41 joe acpid: 1 client rule loaded
Feb  1 19:39:41 joe acpid: client connected from 4836[0:0]
Feb  1 19:39:41 joe acpid: 1 client rule loaded
Feb  1 19:39:41 joe acpid: client connected from 4840[0:0]
Feb  1 19:39:41 joe acpid: 1 client rule loaded
Feb  1 19:39:41 joe acpid: client connected from 4814[0:0]
Feb  1 19:39:41 joe acpid: 1 client rule loaded
Feb  1 19:39:41 joe acpid: client connected from 4827[0:0]
Feb  1 19:39:41 joe acpid: 1 client rule loaded
Feb  1 19:39:41 joe acpid: client connected from 4819[0:0]
Feb  1 19:39:41 joe acpid: 1 client rule loaded
Feb  1 19:39:41 joe acpid: client connected from 4838[0:0]
Feb  1 19:39:41 joe acpid: 1 client rule loaded
Feb  1 19:39:46 joe pulseaudio[4930]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:46 joe pulseaudio[4931]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:51 joe pulseaudio[5046]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:51 joe pulseaudio[5047]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:57 joe pulseaudio[5136]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:39:57 joe pulseaudio[5135]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:02 joe pulseaudio[5283]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:02 joe pulseaudio[5280]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:03 joe acpid: client 4816[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4830[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4829[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4828[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4832[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4824[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4831[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4826[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4834[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4837[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4839[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4822[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4818[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4836[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4840[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4814[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4827[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4819[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client 4838[0:0] has disconnected
Feb  1 19:40:03 joe acpid: client connected from 5309[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5270[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5276[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5294[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5289[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5272[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5275[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5293[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5291[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5292[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5273[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5296[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5288[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5305[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5274[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5312[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5271[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5290[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5310[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5307[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5311[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:03 joe acpid: client connected from 5306[0:0]
Feb  1 19:40:03 joe acpid: 1 client rule loaded
Feb  1 19:40:07 joe pulseaudio[5393]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:10 joe pulseaudio[5420]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:12 joe pulseaudio[5501]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:15 joe pulseaudio[5552]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:17 joe pulseaudio[5615]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:20 joe pulseaudio[5666]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:22 joe pulseaudio[5729]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:23 joe acpid: client 5309[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5270[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5276[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5294[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5289[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5272[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5275[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5293[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5291[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5292[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5273[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5296[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5288[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5305[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5274[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5312[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5271[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5290[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5310[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5307[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5311[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client 5306[0:0] has disconnected
Feb  1 19:40:23 joe acpid: client connected from 5756[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5755[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5758[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5763[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5762[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5764[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5760[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5772[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5774[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5781[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5776[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5777[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5778[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5782[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5803[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5757[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5775[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5783[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5767[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5779[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5780[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5801[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5765[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:23 joe acpid: client connected from 5766[0:0]
Feb  1 19:40:23 joe acpid: 1 client rule loaded
Feb  1 19:40:24 joe acpid: client connected from 5802[0:0]
Feb  1 19:40:24 joe acpid: 1 client rule loaded
Feb  1 19:40:24 joe acpid: client connected from 5770[0:0]
Feb  1 19:40:24 joe acpid: 1 client rule loaded
Feb  1 19:40:24 joe acpid: client connected from 5769[0:0]
Feb  1 19:40:24 joe acpid: 1 client rule loaded
Feb  1 19:40:24 joe acpid: client connected from 5806[0:0]
Feb  1 19:40:24 joe acpid: 1 client rule loaded
Feb  1 19:40:24 joe acpid: client connected from 5761[0:0]
Feb  1 19:40:24 joe acpid: 1 client rule loaded
Feb  1 19:40:24 joe acpid: client connected from 5807[0:0]
Feb  1 19:40:24 joe acpid: 1 client rule loaded
Feb  1 19:40:24 joe acpid: client connected from 5805[0:0]
Feb  1 19:40:24 joe acpid: 1 client rule loaded
Feb  1 19:40:24 joe acpid: client connected from 5759[0:0]
Feb  1 19:40:24 joe acpid: 1 client rule loaded
Feb  1 19:40:24 joe acpid: client connected from 5771[0:0]
Feb  1 19:40:24 joe acpid: 1 client rule loaded
Feb  1 19:40:24 joe acpid: client connected from 5800[0:0]
Feb  1 19:40:24 joe acpid: 1 client rule loaded
Feb  1 19:40:27 joe pulseaudio[5849]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:28 joe pulseaudio[3668]: [pulseaudio] module-console-kit.c: GetUnixUser() call failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetUnixUser" with signature "" on interface "org.freedesktop.ConsoleKit.Session" doesn't exist
Feb  1 19:40:28 joe pulseaudio[5903]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:31 joe pulseaudio[5979]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:33 joe pulseaudio[6005]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:36 joe pulseaudio[6089]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:38 joe pulseaudio[6122]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:41 joe pulseaudio[6207]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:43 joe pulseaudio[6238]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:44 joe acpid: client 5756[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5755[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5758[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5763[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5762[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5764[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5760[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5772[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5774[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5781[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5776[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5777[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5778[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5782[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5803[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5757[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5775[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5783[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5767[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5779[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5780[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5801[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5765[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5766[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5802[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5770[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5769[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5806[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5761[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5807[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5805[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5759[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5771[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client 5800[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client connected from 6281[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:44 joe acpid: client 6281[0:0] has disconnected
Feb  1 19:40:44 joe acpid: client connected from 6282[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:44 joe acpid: client connected from 6290[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:44 joe acpid: client connected from 6292[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:44 joe acpid: client connected from 6284[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:44 joe acpid: client connected from 6283[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:44 joe acpid: client connected from 6293[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:44 joe acpid: client connected from 6294[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:44 joe acpid: client connected from 6285[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:44 joe acpid: client connected from 6286[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:44 joe acpid: client connected from 6297[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:44 joe acpid: client connected from 6295[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:44 joe acpid: client connected from 6288[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:44 joe acpid: client connected from 6298[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:44 joe acpid: client connected from 6296[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:44 joe acpid: client connected from 6300[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:44 joe acpid: client connected from 6299[0:0]
Feb  1 19:40:44 joe acpid: 1 client rule loaded
Feb  1 19:40:46 joe pulseaudio[6344]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:47 joe pulseaudio[6367]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:51 joe pulseaudio[6460]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:52 joe pulseaudio[6483]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:56 joe pulseaudio[6578]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:40:57 joe pulseaudio[6601]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:01 joe pulseaudio[6695]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:02 joe pulseaudio[6717]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:05 joe acpid: client 6282[0:0] has disconnected
Feb  1 19:41:05 joe acpid: client 6290[0:0] has disconnected
Feb  1 19:41:05 joe acpid: client 6292[0:0] has disconnected
Feb  1 19:41:05 joe acpid: client 6284[0:0] has disconnected
Feb  1 19:41:05 joe acpid: client 6283[0:0] has disconnected
Feb  1 19:41:05 joe acpid: client 6293[0:0] has disconnected
Feb  1 19:41:05 joe acpid: client 6294[0:0] has disconnected
Feb  1 19:41:05 joe acpid: client 6285[0:0] has disconnected
Feb  1 19:41:05 joe acpid: client 6286[0:0] has disconnected
Feb  1 19:41:05 joe acpid: client 6297[0:0] has disconnected
Feb  1 19:41:05 joe acpid: client 6295[0:0] has disconnected
Feb  1 19:41:05 joe acpid: client 6288[0:0] has disconnected
Feb  1 19:41:05 joe acpid: client 6298[0:0] has disconnected
Feb  1 19:41:05 joe acpid: client 6296[0:0] has disconnected
Feb  1 19:41:05 joe acpid: client 6300[0:0] has disconnected
Feb  1 19:41:05 joe acpid: client 6299[0:0] has disconnected
Feb  1 19:41:05 joe acpid: client connected from 6793[0:0]
Feb  1 19:41:05 joe acpid: 1 client rule loaded
Feb  1 19:41:06 joe pulseaudio[6803]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:07 joe pulseaudio[6825]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:11 joe pulseaudio[6918]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:12 joe pulseaudio[6940]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:16 joe pulseaudio[7034]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:17 joe pulseaudio[7056]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:21 joe pulseaudio[7148]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:22 joe pulseaudio[7171]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:26 joe pulseaudio[7263]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:27 joe pulseaudio[7283]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:31 joe pulseaudio[7372]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:32 joe pulseaudio[7394]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:36 joe pulseaudio[7488]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:37 joe pulseaudio[7510]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:41 joe pulseaudio[7603]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:42 joe pulseaudio[7625]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:46 joe pulseaudio[7718]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:47 joe pulseaudio[7740]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:51 joe acpid: client 6793[0:0] has disconnected
Feb  1 19:41:51 joe acpid: client connected from 7782[0:0]
Feb  1 19:41:51 joe acpid: 1 client rule loaded
Feb  1 19:41:51 joe acpid: client 7782[0:0] has disconnected
Feb  1 19:41:51 joe acpid: client connected from 7783[0:0]
Feb  1 19:41:51 joe acpid: 1 client rule loaded
Feb  1 19:41:51 joe acpid: client connected from 7787[0:0]
Feb  1 19:41:51 joe acpid: 1 client rule loaded
Feb  1 19:41:51 joe acpid: client 7783[0:0] has disconnected
Feb  1 19:41:51 joe acpid: client 7787[0:0] has disconnected
Feb  1 19:41:51 joe acpid: client connected from 7784[0:0]
Feb  1 19:41:51 joe pulseaudio[7853]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:51 joe acpid: 1 client rule loaded
Feb  1 19:41:51 joe acpid: client 7784[0:0] has disconnected
Feb  1 19:41:51 joe acpid: client connected from 7798[0:0]
Feb  1 19:41:51 joe acpid: 1 client rule loaded
Feb  1 19:41:51 joe acpid: client 7798[0:0] has disconnected
Feb  1 19:41:51 joe acpid: client connected from 7796[0:0]
Feb  1 19:41:51 joe acpid: 1 client rule loaded
Feb  1 19:41:51 joe acpid: client 7796[0:0] has disconnected
Feb  1 19:41:51 joe acpid: client connected from 7799[0:0]
Feb  1 19:41:51 joe acpid: 1 client rule loaded
Feb  1 19:41:51 joe acpid: client 7799[0:0] has disconnected
Feb  1 19:41:51 joe acpid: client connected from 7797[0:0]
Feb  1 19:41:51 joe acpid: 1 client rule loaded
Feb  1 19:41:51 joe acpid: client 7797[0:0] has disconnected
Feb  1 19:41:51 joe acpid: client connected from 7802[0:0]
Feb  1 19:41:51 joe acpid: 1 client rule loaded
Feb  1 19:41:51 joe acpid: client 7802[0:0] has disconnected
Feb  1 19:41:51 joe acpid: client connected from 7804[0:0]
Feb  1 19:41:51 joe acpid: 1 client rule loaded
Feb  1 19:41:51 joe acpid: client 7804[0:0] has disconnected
Feb  1 19:41:51 joe acpid: client connected from 7801[0:0]
Feb  1 19:41:51 joe acpid: 1 client rule loaded
Feb  1 19:41:51 joe acpid: client 7801[0:0] has disconnected
Feb  1 19:41:51 joe acpid: client connected from 7795[0:0]
Feb  1 19:41:51 joe acpid: 1 client rule loaded
Feb  1 19:41:51 joe acpid: client 7795[0:0] has disconnected
Feb  1 19:41:51 joe acpid: client connected from 7800[0:0]
Feb  1 19:41:51 joe acpid: 1 client rule loaded
Feb  1 19:41:51 joe acpid: client 7800[0:0] has disconnected
Feb  1 19:41:51 joe acpid: client connected from 7785[0:0]
Feb  1 19:41:51 joe acpid: 1 client rule loaded
Feb  1 19:41:51 joe acpid: client 7785[0:0] has disconnected
Feb  1 19:41:51 joe acpid: client connected from 7786[0:0]
Feb  1 19:41:51 joe acpid: 1 client rule loaded
Feb  1 19:41:52 joe pulseaudio[7875]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:56 joe pulseaudio[7968]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:41:57 joe pulseaudio[7991]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:01 joe pulseaudio[8083]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:02 joe pulseaudio[8105]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:06 joe pulseaudio[8198]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:07 joe pulseaudio[8220]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:12 joe acpid: client 7786[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client connected from 8294[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client connected from 8293[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client connected from 8292[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client connected from 8298[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client connected from 8302[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe pulseaudio[8358]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:12 joe acpid: client 8294[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client 8293[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client 8292[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client 8298[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client 8302[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client connected from 8301[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client 8301[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client connected from 8299[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe pulseaudio[8378]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:12 joe acpid: client 8299[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client connected from 8304[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client 8304[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client connected from 8305[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client 8305[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client connected from 8306[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client 8306[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client connected from 8318[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client 8318[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client connected from 8311[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client 8311[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client connected from 8313[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client 8313[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client connected from 8291[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client 8291[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client connected from 8319[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client 8319[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client connected from 8320[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client 8320[0:0] has disconnected
Feb  1 19:42:12 joe acpid: client connected from 8312[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client connected from 8322[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client connected from 8323[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client connected from 8324[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client connected from 8326[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client connected from 8308[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client connected from 8309[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client connected from 8315[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client connected from 8321[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client connected from 8310[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client connected from 8316[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client connected from 8314[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:12 joe acpid: client connected from 8317[0:0]
Feb  1 19:42:12 joe acpid: 1 client rule loaded
Feb  1 19:42:18 joe pulseaudio[8493]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:18 joe pulseaudio[8495]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:23 joe pulseaudio[8609]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:23 joe pulseaudio[8610]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:28 joe pulseaudio[8723]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:28 joe pulseaudio[8722]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:32 joe acpid: client 8312[0:0] has disconnected
Feb  1 19:42:32 joe acpid: client 8322[0:0] has disconnected
Feb  1 19:42:32 joe acpid: client 8323[0:0] has disconnected
Feb  1 19:42:32 joe acpid: client 8324[0:0] has disconnected
Feb  1 19:42:32 joe acpid: client 8326[0:0] has disconnected
Feb  1 19:42:32 joe acpid: client 8308[0:0] has disconnected
Feb  1 19:42:32 joe acpid: client 8309[0:0] has disconnected
Feb  1 19:42:32 joe acpid: client 8315[0:0] has disconnected
Feb  1 19:42:32 joe acpid: client 8321[0:0] has disconnected
Feb  1 19:42:32 joe acpid: client 8310[0:0] has disconnected
Feb  1 19:42:32 joe acpid: client 8316[0:0] has disconnected
Feb  1 19:42:32 joe acpid: client 8314[0:0] has disconnected
Feb  1 19:42:32 joe acpid: client 8317[0:0] has disconnected
Feb  1 19:42:32 joe acpid: client connected from 8788[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8789[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client 8788[0:0] has disconnected
Feb  1 19:42:32 joe acpid: client 8789[0:0] has disconnected
Feb  1 19:42:32 joe acpid: client connected from 8798[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8794[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8801[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8792[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8802[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8805[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8795[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8807[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8804[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8796[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8803[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8797[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8793[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8799[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8810[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8824[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:32 joe acpid: client connected from 8823[0:0]
Feb  1 19:42:32 joe acpid: 1 client rule loaded
Feb  1 19:42:33 joe pulseaudio[8847]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:33 joe pulseaudio[8846]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:39 joe pulseaudio[8965]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:39 joe pulseaudio[8962]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:44 joe pulseaudio[9078]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:44 joe pulseaudio[9079]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:49 joe pulseaudio[9192]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:49 joe pulseaudio[9193]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:55 joe acpid: client 8798[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client 8794[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client 8801[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client 8792[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client 8802[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client 8805[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client 8795[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client 8807[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client 8804[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client 8796[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client 8803[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client 8797[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client 8793[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client 8799[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client 8810[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client 8824[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client 8823[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client connected from 9300[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client 9300[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client connected from 9287[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe pulseaudio[9336]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:55 joe pulseaudio[9337]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:42:55 joe acpid: client 9287[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client connected from 9295[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client 9295[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client connected from 9315[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client 9315[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client connected from 9296[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client 9296[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client connected from 9291[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client 9291[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client connected from 9318[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client 9318[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client connected from 9292[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client 9292[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client connected from 9293[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client 9293[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client connected from 9303[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client 9303[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client connected from 9302[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client 9302[0:0] has disconnected
Feb  1 19:42:55 joe acpid: client connected from 9290[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client connected from 9286[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client connected from 9317[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client connected from 9316[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client connected from 9305[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client connected from 9289[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client connected from 9319[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:42:55 joe acpid: client connected from 9297[0:0]
Feb  1 19:42:55 joe acpid: 1 client rule loaded
Feb  1 19:43:01 joe pulseaudio[9453]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:01 joe pulseaudio[9454]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:05 joe pulseaudio[9567]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:05 joe pulseaudio[9568]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:10 joe pulseaudio[9679]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:10 joe pulseaudio[9681]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:16 joe pulseaudio[9793]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:16 joe pulseaudio[9792]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:16 joe acpid: client 9290[0:0] has disconnected
Feb  1 19:43:16 joe acpid: client 9286[0:0] has disconnected
Feb  1 19:43:16 joe acpid: client 9317[0:0] has disconnected
Feb  1 19:43:16 joe acpid: client 9316[0:0] has disconnected
Feb  1 19:43:16 joe acpid: client 9305[0:0] has disconnected
Feb  1 19:43:16 joe acpid: client 9289[0:0] has disconnected
Feb  1 19:43:16 joe acpid: client 9319[0:0] has disconnected
Feb  1 19:43:16 joe acpid: client 9297[0:0] has disconnected
Feb  1 19:43:16 joe acpid: client connected from 9804[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:16 joe acpid: client connected from 9807[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:16 joe acpid: client connected from 9812[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:16 joe acpid: client connected from 9808[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:16 joe acpid: client connected from 9811[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:16 joe acpid: client connected from 9806[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:16 joe acpid: client connected from 9810[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:16 joe acpid: client connected from 9820[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:16 joe acpid: client connected from 9824[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:16 joe acpid: client connected from 9822[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:16 joe acpid: client connected from 9821[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:16 joe acpid: client connected from 9805[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:16 joe acpid: client connected from 9823[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:16 joe acpid: client connected from 9826[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:16 joe acpid: client connected from 9827[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:16 joe acpid: client connected from 9828[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:16 joe acpid: client connected from 9825[0:0]
Feb  1 19:43:16 joe acpid: 1 client rule loaded
Feb  1 19:43:21 joe pulseaudio[9940]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:21 joe pulseaudio[9939]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:26 joe pulseaudio[10047]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:26 joe pulseaudio[10048]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:31 joe pulseaudio[10151]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:31 joe pulseaudio[10150]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:36 joe pulseaudio[10264]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:36 joe pulseaudio[10263]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:38 joe acpid: client 9804[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 9807[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 9812[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 9808[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 9811[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 9806[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 9810[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 9820[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 9824[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 9822[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 9821[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 9805[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 9823[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 9826[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 9827[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 9828[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 9825[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client connected from 10301[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10305[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10303[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10307[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10304[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10300[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10306[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10302[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10318[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10331[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10327[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10330[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10320[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10322[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10316[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10335[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10332[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10359[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10324[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10317[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10333[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10319[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10321[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10357[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10356[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10358[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10323[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10326[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10329[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10325[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10334[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client connected from 10355[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client 10307[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client connected from 10328[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:38 joe acpid: client 10300[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client 10306[0:0] has disconnected
Feb  1 19:43:38 joe acpid: client connected from 10366[0:0]
Feb  1 19:43:38 joe acpid: 1 client rule loaded
Feb  1 19:43:43 joe pulseaudio[10423]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:43 joe pulseaudio[10425]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:47 joe pulseaudio[10542]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:47 joe pulseaudio[10540]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:52 joe pulseaudio[10653]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:52 joe pulseaudio[10654]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:57 joe pulseaudio[10770]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:43:57 joe pulseaudio[10771]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:01 joe acpid: client 10301[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10305[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10303[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10304[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10302[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10318[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10331[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10327[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10330[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10320[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10322[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10316[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10335[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10332[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10359[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10324[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10317[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10333[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10319[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10321[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10357[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10356[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10358[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10323[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10326[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10329[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10325[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10334[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10355[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10328[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client 10366[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client connected from 10817[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:01 joe acpid: client 10817[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client connected from 10815[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:01 joe acpid: client 10815[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client connected from 10813[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:01 joe acpid: client 10813[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client connected from 10820[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:01 joe acpid: client 10820[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client connected from 10821[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:01 joe acpid: client 10821[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client connected from 10825[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:01 joe acpid: client 10825[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client connected from 10818[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:01 joe acpid: client 10818[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client connected from 10814[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:01 joe acpid: client 10814[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client connected from 10819[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:01 joe acpid: client 10819[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client connected from 10816[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:01 joe acpid: client 10816[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client connected from 10837[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:01 joe acpid: client 10837[0:0] has disconnected
Feb  1 19:44:01 joe acpid: client connected from 10838[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:01 joe acpid: client connected from 10835[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:01 joe acpid: client connected from 10836[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:01 joe acpid: client connected from 10833[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:01 joe acpid: client connected from 10834[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:01 joe acpid: client connected from 10845[0:0]
Feb  1 19:44:01 joe acpid: 1 client rule loaded
Feb  1 19:44:02 joe pulseaudio[10890]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:02 joe pulseaudio[10892]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:07 joe pulseaudio[11002]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:07 joe pulseaudio[11004]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:12 joe pulseaudio[11114]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:12 joe pulseaudio[11115]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:17 joe pulseaudio[11227]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:17 joe pulseaudio[11226]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:21 joe acpid: client 10838[0:0] has disconnected
Feb  1 19:44:21 joe acpid: client 10835[0:0] has disconnected
Feb  1 19:44:21 joe acpid: client 10836[0:0] has disconnected
Feb  1 19:44:21 joe acpid: client 10833[0:0] has disconnected
Feb  1 19:44:21 joe acpid: client 10834[0:0] has disconnected
Feb  1 19:44:21 joe acpid: client 10845[0:0] has disconnected
Feb  1 19:44:21 joe acpid: client connected from 11321[0:0]
Feb  1 19:44:21 joe acpid: 1 client rule loaded
Feb  1 19:44:22 joe pulseaudio[11335]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:22 joe pulseaudio[11336]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:27 joe pulseaudio[11447]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:27 joe pulseaudio[11445]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:32 joe pulseaudio[11557]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:32 joe pulseaudio[11558]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:37 joe pulseaudio[11667]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:37 joe pulseaudio[11666]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:42 joe pulseaudio[11776]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:42 joe pulseaudio[11777]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:47 joe pulseaudio[11886]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:47 joe pulseaudio[11885]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:52 joe pulseaudio[11996]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:52 joe pulseaudio[11998]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:57 joe pulseaudio[12107]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:44:57 joe pulseaudio[12110]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:02 joe pulseaudio[12220]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:02 joe pulseaudio[12219]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:07 joe acpid: client 11321[0:0] has disconnected
Feb  1 19:45:07 joe acpid: client connected from 12326[0:0]
Feb  1 19:45:07 joe acpid: 1 client rule loaded
Feb  1 19:45:07 joe acpid: client connected from 12332[0:0]
Feb  1 19:45:07 joe acpid: 1 client rule loaded
Feb  1 19:45:07 joe acpid: client connected from 12327[0:0]
Feb  1 19:45:07 joe acpid: 1 client rule loaded
Feb  1 19:45:07 joe acpid: client connected from 12330[0:0]
Feb  1 19:45:07 joe acpid: 1 client rule loaded
Feb  1 19:45:07 joe acpid: client connected from 12328[0:0]
Feb  1 19:45:07 joe acpid: 1 client rule loaded
Feb  1 19:45:07 joe acpid: client connected from 12329[0:0]
Feb  1 19:45:07 joe acpid: 1 client rule loaded
Feb  1 19:45:07 joe acpid: client connected from 12336[0:0]
Feb  1 19:45:07 joe acpid: 1 client rule loaded
Feb  1 19:45:07 joe acpid: client connected from 12335[0:0]
Feb  1 19:45:07 joe acpid: 1 client rule loaded
Feb  1 19:45:07 joe acpid: client connected from 12334[0:0]
Feb  1 19:45:07 joe acpid: 1 client rule loaded
Feb  1 19:45:07 joe pulseaudio[12324]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:07 joe pulseaudio[12325]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:07 joe acpid: client connected from 12346[0:0]
Feb  1 19:45:07 joe acpid: 1 client rule loaded
Feb  1 19:45:07 joe acpid: client connected from 12345[0:0]
Feb  1 19:45:07 joe acpid: 1 client rule loaded
Feb  1 19:45:07 joe acpid: client 12327[0:0] has disconnected
Feb  1 19:45:07 joe acpid: client connected from 12348[0:0]
Feb  1 19:45:07 joe acpid: 1 client rule loaded
Feb  1 19:45:07 joe acpid: client connected from 12344[0:0]
Feb  1 19:45:07 joe acpid: 1 client rule loaded
Feb  1 19:45:07 joe acpid: client connected from 12349[0:0]
Feb  1 19:45:07 joe acpid: 1 client rule loaded
Feb  1 19:45:07 joe acpid: client 12326[0:0] has disconnected
Feb  1 19:45:07 joe acpid: client connected from 12347[0:0]
Feb  1 19:45:07 joe acpid: 1 client rule loaded
Feb  1 19:45:12 joe pulseaudio[12443]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:12 joe pulseaudio[12445]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:17 joe pulseaudio[12554]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:17 joe pulseaudio[12555]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:22 joe pulseaudio[12665]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:22 joe pulseaudio[12666]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:27 joe pulseaudio[12775]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:27 joe pulseaudio[12776]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:29 joe acpid: client 12332[0:0] has disconnected
Feb  1 19:45:29 joe acpid: client 12330[0:0] has disconnected
Feb  1 19:45:29 joe acpid: client 12328[0:0] has disconnected
Feb  1 19:45:29 joe acpid: client 12329[0:0] has disconnected
Feb  1 19:45:29 joe acpid: client 12336[0:0] has disconnected
Feb  1 19:45:29 joe acpid: client 12335[0:0] has disconnected
Feb  1 19:45:29 joe acpid: client 12334[0:0] has disconnected
Feb  1 19:45:29 joe acpid: client 12346[0:0] has disconnected
Feb  1 19:45:29 joe acpid: client 12345[0:0] has disconnected
Feb  1 19:45:29 joe acpid: client 12348[0:0] has disconnected
Feb  1 19:45:29 joe acpid: client 12344[0:0] has disconnected
Feb  1 19:45:29 joe acpid: client 12349[0:0] has disconnected
Feb  1 19:45:29 joe acpid: client 12347[0:0] has disconnected
Feb  1 19:45:29 joe acpid: client connected from 12817[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12819[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12823[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12820[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12818[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12822[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12821[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12824[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12848[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12834[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12836[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12850[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12840[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12847[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12835[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12843[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12853[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12842[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12870[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12844[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12849[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12846[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12851[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12852[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12833[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12845[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12869[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client connected from 12868[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:29 joe acpid: client 12817[0:0] has disconnected
Feb  1 19:45:29 joe acpid: client connected from 12867[0:0]
Feb  1 19:45:29 joe acpid: 1 client rule loaded
Feb  1 19:45:34 joe pulseaudio[12923]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:34 joe pulseaudio[12924]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:38 joe pulseaudio[13056]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:38 joe pulseaudio[13054]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:44 joe pulseaudio[13164]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:44 joe pulseaudio[13166]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:49 joe pulseaudio[13271]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:49 joe pulseaudio[13270]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:51 joe acpid: client 12819[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12823[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12820[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12818[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12822[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12821[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12824[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12848[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12834[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12836[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12850[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12840[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12847[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12835[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12843[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12853[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12842[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12870[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12844[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12849[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12846[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12851[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12852[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12833[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12845[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12869[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12868[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client 12867[0:0] has disconnected
Feb  1 19:45:51 joe acpid: client connected from 13336[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13338[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13343[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13339[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13345[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13340[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13341[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13337[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13347[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13356[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13355[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13353[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13358[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13360[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13346[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13354[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13351[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13359[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:51 joe acpid: client connected from 13361[0:0]
Feb  1 19:45:51 joe acpid: 1 client rule loaded
Feb  1 19:45:55 joe pulseaudio[13404]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:45:55 joe pulseaudio[13405]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:00 joe pulseaudio[13544]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:00 joe pulseaudio[13545]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:04 joe pulseaudio[13646]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:04 joe pulseaudio[13647]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:09 joe pulseaudio[13753]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:09 joe pulseaudio[13754]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:13 joe acpid: client 13336[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13338[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13343[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13339[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13345[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13340[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13341[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13337[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13347[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13356[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13355[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13353[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13358[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13360[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13346[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13354[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13351[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13359[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client 13361[0:0] has disconnected
Feb  1 19:46:13 joe acpid: client connected from 13852[0:0]
Feb  1 19:46:13 joe acpid: 1 client rule loaded
Feb  1 19:46:13 joe acpid: client connected from 13849[0:0]
Feb  1 19:46:13 joe acpid: 1 client rule loaded
Feb  1 19:46:13 joe acpid: client connected from 13853[0:0]
Feb  1 19:46:13 joe acpid: 1 client rule loaded
Feb  1 19:46:13 joe acpid: client connected from 13856[0:0]
Feb  1 19:46:13 joe acpid: 1 client rule loaded
Feb  1 19:46:13 joe acpid: client connected from 13863[0:0]
Feb  1 19:46:13 joe acpid: 1 client rule loaded
Feb  1 19:46:13 joe acpid: client connected from 13850[0:0]
Feb  1 19:46:13 joe acpid: 1 client rule loaded
Feb  1 19:46:13 joe acpid: client connected from 13865[0:0]
Feb  1 19:46:13 joe acpid: 1 client rule loaded
Feb  1 19:46:13 joe acpid: client connected from 13851[0:0]
Feb  1 19:46:13 joe acpid: 1 client rule loaded
Feb  1 19:46:13 joe acpid: client connected from 13867[0:0]
Feb  1 19:46:13 joe acpid: 1 client rule loaded
Feb  1 19:46:13 joe acpid: client connected from 13855[0:0]
Feb  1 19:46:13 joe acpid: 1 client rule loaded
Feb  1 19:46:13 joe acpid: client connected from 13870[0:0]
Feb  1 19:46:13 joe acpid: 1 client rule loaded
Feb  1 19:46:13 joe acpid: client connected from 13864[0:0]
Feb  1 19:46:13 joe acpid: 1 client rule loaded
Feb  1 19:46:13 joe acpid: client connected from 13869[0:0]
Feb  1 19:46:13 joe acpid: 1 client rule loaded
Feb  1 19:46:13 joe acpid: client connected from 13868[0:0]
Feb  1 19:46:13 joe acpid: 1 client rule loaded
Feb  1 19:46:13 joe acpid: client connected from 13866[0:0]
Feb  1 19:46:13 joe acpid: 1 client rule loaded
Feb  1 19:46:13 joe acpid: client connected from 13883[0:0]
Feb  1 19:46:13 joe acpid: 1 client rule loaded
Feb  1 19:46:14 joe acpid: client connected from 13882[0:0]
Feb  1 19:46:14 joe acpid: 1 client rule loaded
Feb  1 19:46:14 joe acpid: client connected from 13884[0:0]
Feb  1 19:46:14 joe acpid: 1 client rule loaded
Feb  1 19:46:14 joe acpid: client connected from 13879[0:0]
Feb  1 19:46:14 joe acpid: 1 client rule loaded
Feb  1 19:46:14 joe pulseaudio[13895]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:14 joe pulseaudio[13894]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:19 joe pulseaudio[14004]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:19 joe pulseaudio[14005]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:24 joe pulseaudio[14105]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:24 joe pulseaudio[14107]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:29 joe pulseaudio[14218]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:29 joe pulseaudio[14219]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:34 joe pulseaudio[14329]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:34 joe pulseaudio[14330]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:38 joe acpid: client 13852[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13849[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13853[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13856[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13863[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13850[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13865[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13851[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13867[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13855[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13870[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13864[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13869[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13868[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13866[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13883[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13882[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13884[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client 13879[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client connected from 14371[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:38 joe acpid: client 14371[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client connected from 14373[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:38 joe acpid: client 14373[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client connected from 14374[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:38 joe acpid: client 14374[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client connected from 14375[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:38 joe acpid: client 14375[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client connected from 14372[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:38 joe acpid: client 14372[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client connected from 14380[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:38 joe acpid: client 14380[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client connected from 14381[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:38 joe acpid: client 14381[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client connected from 14382[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:38 joe acpid: client 14382[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client connected from 14383[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:38 joe acpid: client 14383[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client connected from 14369[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:38 joe acpid: client 14369[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client connected from 14376[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:38 joe acpid: client 14376[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client connected from 14379[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:38 joe acpid: client 14379[0:0] has disconnected
Feb  1 19:46:38 joe acpid: client connected from 14377[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:38 joe acpid: client connected from 14384[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:38 joe acpid: client connected from 14370[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:38 joe acpid: client connected from 14378[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:38 joe acpid: client connected from 14402[0:0]
Feb  1 19:46:38 joe acpid: 1 client rule loaded
Feb  1 19:46:39 joe pulseaudio[14464]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:39 joe pulseaudio[14463]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:44 joe pulseaudio[14572]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:44 joe pulseaudio[14573]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:49 joe pulseaudio[14675]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:49 joe pulseaudio[14676]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:54 joe pulseaudio[14785]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:46:54 joe pulseaudio[14786]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:01 joe acpid: client 14377[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client 14384[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client 14370[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client 14378[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client 14402[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client connected from 14880[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe pulseaudio[14940]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:01 joe pulseaudio[14944]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:01 joe acpid: client 14880[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client connected from 14878[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client 14878[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client connected from 14886[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client 14886[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client connected from 14881[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client 14881[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client connected from 14883[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client 14883[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client connected from 14890[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client 14890[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client connected from 14889[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client 14889[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client connected from 14879[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client 14879[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client connected from 14885[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client 14885[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client connected from 14891[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client 14891[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client connected from 14887[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client 14887[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client connected from 14882[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client 14882[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client connected from 14907[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client 14907[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client connected from 14904[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client connected from 14906[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client connected from 14908[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client connected from 14902[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client connected from 14901[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client 14904[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client 14902[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client connected from 14903[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client connected from 14921[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client connected from 14924[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client connected from 14928[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client connected from 14926[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client 14908[0:0] has disconnected
Feb  1 19:47:01 joe acpid: client connected from 14922[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client connected from 14917[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client connected from 14920[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client connected from 14918[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client connected from 14925[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client connected from 14929[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client connected from 14919[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:01 joe acpid: client connected from 14927[0:0]
Feb  1 19:47:01 joe acpid: 1 client rule loaded
Feb  1 19:47:06 joe pulseaudio[15072]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:06 joe pulseaudio[15073]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:11 joe pulseaudio[15185]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:11 joe pulseaudio[15186]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:16 joe pulseaudio[15295]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:16 joe pulseaudio[15296]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:22 joe acpid: client 14906[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client 14901[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client 14903[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client 14921[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client 14924[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client 14928[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client 14926[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client 14922[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client 14917[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client 14920[0:0] has disconnected
Feb  1 19:47:22 joe pulseaudio[15433]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:22 joe pulseaudio[15434]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:22 joe acpid: client 14918[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client 14925[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client 14929[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client 14919[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client 14927[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client connected from 15388[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client 15388[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client connected from 15389[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client 15389[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client connected from 15387[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client 15387[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client connected from 15397[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client 15397[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client connected from 15395[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client 15395[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client connected from 15406[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client 15406[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client connected from 15403[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client 15403[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client connected from 15398[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client 15398[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client connected from 15405[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client 15405[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client connected from 15400[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client 15400[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client connected from 15394[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client 15394[0:0] has disconnected
Feb  1 19:47:22 joe acpid: client connected from 15408[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client connected from 15407[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client connected from 15399[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client connected from 15396[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client connected from 15393[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client connected from 15419[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client connected from 15420[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client connected from 15418[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:22 joe acpid: client connected from 15421[0:0]
Feb  1 19:47:22 joe acpid: 1 client rule loaded
Feb  1 19:47:28 joe pulseaudio[15575]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:28 joe pulseaudio[15576]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:33 joe pulseaudio[15677]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:33 joe pulseaudio[15675]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:38 joe pulseaudio[15785]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:38 joe pulseaudio[15786]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:43 joe pulseaudio[15890]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:43 joe pulseaudio[15891]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:44 joe acpid: client 15408[0:0] has disconnected
Feb  1 19:47:44 joe acpid: client 15407[0:0] has disconnected
Feb  1 19:47:44 joe acpid: client 15399[0:0] has disconnected
Feb  1 19:47:44 joe acpid: client 15396[0:0] has disconnected
Feb  1 19:47:44 joe acpid: client 15393[0:0] has disconnected
Feb  1 19:47:44 joe acpid: client 15419[0:0] has disconnected
Feb  1 19:47:44 joe acpid: client 15420[0:0] has disconnected
Feb  1 19:47:44 joe acpid: client 15418[0:0] has disconnected
Feb  1 19:47:44 joe acpid: client 15421[0:0] has disconnected
Feb  1 19:47:44 joe acpid: client connected from 15900[0:0]
Feb  1 19:47:44 joe acpid: 1 client rule loaded
Feb  1 19:47:49 joe pulseaudio[16015]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:49 joe pulseaudio[16016]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:54 joe pulseaudio[16123]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:54 joe pulseaudio[16124]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:59 joe pulseaudio[16232]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:47:59 joe pulseaudio[16233]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:04 joe pulseaudio[16340]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:04 joe pulseaudio[16342]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:08 joe acpid: client 15900[0:0] has disconnected
Feb  1 19:48:08 joe acpid: client connected from 16409[0:0]
Feb  1 19:48:08 joe acpid: 1 client rule loaded
Feb  1 19:48:08 joe acpid: client connected from 16406[0:0]
Feb  1 19:48:08 joe acpid: 1 client rule loaded
Feb  1 19:48:08 joe acpid: client connected from 16416[0:0]
Feb  1 19:48:08 joe acpid: 1 client rule loaded
Feb  1 19:48:08 joe acpid: client 16409[0:0] has disconnected
Feb  1 19:48:08 joe acpid: client 16406[0:0] has disconnected
Feb  1 19:48:08 joe acpid: client 16416[0:0] has disconnected
Feb  1 19:48:08 joe acpid: client connected from 16414[0:0]
Feb  1 19:48:08 joe acpid: 1 client rule loaded
Feb  1 19:48:08 joe acpid: client 16414[0:0] has disconnected
Feb  1 19:48:08 joe acpid: client connected from 16412[0:0]
Feb  1 19:48:08 joe acpid: 1 client rule loaded
Feb  1 19:48:08 joe acpid: client 16412[0:0] has disconnected
Feb  1 19:48:08 joe acpid: client connected from 16419[0:0]
Feb  1 19:48:08 joe acpid: 1 client rule loaded
Feb  1 19:48:08 joe acpid: client 16419[0:0] has disconnected
Feb  1 19:48:08 joe acpid: client connected from 16413[0:0]
Feb  1 19:48:08 joe acpid: 1 client rule loaded
Feb  1 19:48:08 joe acpid: client 16413[0:0] has disconnected
Feb  1 19:48:08 joe acpid: client connected from 16408[0:0]
Feb  1 19:48:08 joe acpid: 1 client rule loaded
Feb  1 19:48:08 joe acpid: client 16408[0:0] has disconnected
Feb  1 19:48:08 joe acpid: client connected from 16411[0:0]
Feb  1 19:48:08 joe acpid: 1 client rule loaded
Feb  1 19:48:08 joe acpid: client 16411[0:0] has disconnected
Feb  1 19:48:08 joe acpid: client connected from 16415[0:0]
Feb  1 19:48:08 joe acpid: 1 client rule loaded
Feb  1 19:48:08 joe acpid: client 16415[0:0] has disconnected
Feb  1 19:48:08 joe acpid: client connected from 16418[0:0]
Feb  1 19:48:08 joe acpid: 1 client rule loaded
Feb  1 19:48:08 joe acpid: client 16418[0:0] has disconnected
Feb  1 19:48:08 joe acpid: client connected from 16430[0:0]
Feb  1 19:48:08 joe acpid: 1 client rule loaded
Feb  1 19:48:08 joe acpid: client 16430[0:0] has disconnected
Feb  1 19:48:08 joe acpid: client connected from 16433[0:0]
Feb  1 19:48:08 joe acpid: 1 client rule loaded
Feb  1 19:48:08 joe acpid: client 16433[0:0] has disconnected
Feb  1 19:48:08 joe acpid: client connected from 16429[0:0]
Feb  1 19:48:08 joe acpid: 1 client rule loaded
Feb  1 19:48:08 joe acpid: client 16429[0:0] has disconnected
Feb  1 19:48:08 joe acpid: client connected from 16432[0:0]
Feb  1 19:48:08 joe acpid: 1 client rule loaded
Feb  1 19:48:09 joe pulseaudio[16467]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:09 joe pulseaudio[16469]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:14 joe pulseaudio[16575]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:14 joe pulseaudio[16577]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:19 joe pulseaudio[16681]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:19 joe pulseaudio[16683]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:24 joe pulseaudio[16792]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:24 joe pulseaudio[16791]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:29 joe pulseaudio[16899]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:29 joe pulseaudio[16898]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:30 joe acpid: client 16432[0:0] has disconnected
Feb  1 19:48:30 joe acpid: client connected from 16919[0:0]
Feb  1 19:48:30 joe acpid: 1 client rule loaded
Feb  1 19:48:30 joe acpid: client connected from 16920[0:0]
Feb  1 19:48:30 joe acpid: 1 client rule loaded
Feb  1 19:48:30 joe acpid: client connected from 16929[0:0]
Feb  1 19:48:30 joe acpid: 1 client rule loaded
Feb  1 19:48:30 joe acpid: client 16919[0:0] has disconnected
Feb  1 19:48:30 joe acpid: client connected from 16924[0:0]
Feb  1 19:48:30 joe acpid: 1 client rule loaded
Feb  1 19:48:30 joe acpid: client connected from 16925[0:0]
Feb  1 19:48:30 joe acpid: 1 client rule loaded
Feb  1 19:48:30 joe acpid: client connected from 16926[0:0]
Feb  1 19:48:30 joe acpid: 1 client rule loaded
Feb  1 19:48:30 joe acpid: client connected from 16928[0:0]
Feb  1 19:48:30 joe acpid: 1 client rule loaded
Feb  1 19:48:30 joe acpid: client connected from 16927[0:0]
Feb  1 19:48:30 joe acpid: 1 client rule loaded
Feb  1 19:48:34 joe pulseaudio[17014]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:34 joe pulseaudio[17013]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:39 joe pulseaudio[17120]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:39 joe pulseaudio[17121]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:44 joe pulseaudio[17215]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:44 joe pulseaudio[17214]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:49 joe pulseaudio[17320]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:49 joe pulseaudio[17322]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:56 joe pulseaudio[17426]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:56 joe pulseaudio[17425]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:48:56 joe acpid: client 16920[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client 16929[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client 16924[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client 16925[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client 16926[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client 16928[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client 16927[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client connected from 17427[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client 17427[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client connected from 17431[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client 17431[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client connected from 17430[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client 17430[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client connected from 17434[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client 17434[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client connected from 17428[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client 17428[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client connected from 17437[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client 17437[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client connected from 17432[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client 17432[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client connected from 17439[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client 17439[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client connected from 17433[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client 17433[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client connected from 17441[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client 17441[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client connected from 17442[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client 17442[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client connected from 17446[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client 17446[0:0] has disconnected
Feb  1 19:48:56 joe acpid: client connected from 17445[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client connected from 17444[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client connected from 17448[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client connected from 17440[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client connected from 17443[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client connected from 17465[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client connected from 17438[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client connected from 17464[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:48:56 joe acpid: client connected from 17463[0:0]
Feb  1 19:48:56 joe acpid: 1 client rule loaded
Feb  1 19:49:00 joe pulseaudio[17565]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:00 joe pulseaudio[17566]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:05 joe pulseaudio[17671]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:05 joe pulseaudio[17672]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:10 joe pulseaudio[17778]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:10 joe pulseaudio[17780]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:14 joe pulseaudio[17875]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:15 joe pulseaudio[17900]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:18 joe acpid: client 17445[0:0] has disconnected
Feb  1 19:49:18 joe acpid: client 17444[0:0] has disconnected
Feb  1 19:49:18 joe acpid: client 17448[0:0] has disconnected
Feb  1 19:49:18 joe acpid: client 17440[0:0] has disconnected
Feb  1 19:49:18 joe acpid: client 17443[0:0] has disconnected
Feb  1 19:49:18 joe acpid: client 17465[0:0] has disconnected
Feb  1 19:49:18 joe acpid: client 17438[0:0] has disconnected
Feb  1 19:49:18 joe acpid: client 17464[0:0] has disconnected
Feb  1 19:49:18 joe acpid: client 17463[0:0] has disconnected
Feb  1 19:49:18 joe acpid: client connected from 17933[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17934[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17950[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17938[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17942[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17945[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17936[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17939[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17940[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17954[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17941[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17944[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17943[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17949[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17953[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17947[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17952[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17948[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:18 joe acpid: client connected from 17937[0:0]
Feb  1 19:49:18 joe acpid: 1 client rule loaded
Feb  1 19:49:19 joe pulseaudio[17988]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:22 joe pulseaudio[18019]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:24 joe pulseaudio[18092]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:26 joe pulseaudio[18131]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:29 joe pulseaudio[18198]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:31 joe pulseaudio[18236]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:34 joe pulseaudio[18304]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:36 joe pulseaudio[18345]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:39 joe pulseaudio[18411]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:41 joe acpid: client 17933[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17934[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17950[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17938[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17942[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17945[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17936[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17939[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17940[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17954[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17941[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17944[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17943[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17949[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17953[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17947[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17952[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17948[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 17937[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client connected from 18436[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client connected from 18437[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client connected from 18440[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client connected from 18448[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client connected from 18455[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client connected from 18441[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client connected from 18449[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client connected from 18446[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client connected from 18444[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client connected from 18453[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client connected from 18450[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client 18437[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client connected from 18442[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client connected from 18447[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client connected from 18454[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client connected from 18451[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client connected from 18443[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client connected from 18456[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client 18436[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 18440[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 18448[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 18455[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 18441[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 18449[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 18446[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 18444[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 18453[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 18450[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 18442[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 18447[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 18454[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 18451[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 18443[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client 18456[0:0] has disconnected
Feb  1 19:49:41 joe acpid: client connected from 18472[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe acpid: client connected from 18473[0:0]
Feb  1 19:49:41 joe acpid: 1 client rule loaded
Feb  1 19:49:41 joe pulseaudio[18465]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:45 joe pulseaudio[18546]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:48 joe pulseaudio[18609]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:49 joe pulseaudio[18639]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:53 joe pulseaudio[18725]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:54 joe pulseaudio[18746]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:59 joe pulseaudio[18831]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:49:59 joe pulseaudio[18851]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:03 joe pulseaudio[18930]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:04 joe acpid: client 18472[0:0] has disconnected
Feb  1 19:50:04 joe acpid: client 18473[0:0] has disconnected
Feb  1 19:50:04 joe acpid: client connected from 18940[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe acpid: client connected from 18946[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe acpid: client connected from 18948[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe acpid: client connected from 18959[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe acpid: client connected from 18950[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe acpid: client connected from 18945[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe acpid: client connected from 18947[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe acpid: client connected from 18951[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe acpid: client connected from 18954[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe acpid: client connected from 18941[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe acpid: client connected from 18955[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe acpid: client connected from 18956[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe acpid: client connected from 18957[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe acpid: client 18946[0:0] has disconnected
Feb  1 19:50:04 joe acpid: client connected from 18942[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe acpid: client 18940[0:0] has disconnected
Feb  1 19:50:04 joe acpid: client connected from 18944[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe acpid: client connected from 18949[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe acpid: client connected from 18953[0:0]
Feb  1 19:50:04 joe acpid: 1 client rule loaded
Feb  1 19:50:04 joe pulseaudio[18975]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:10 joe pulseaudio[19074]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:10 joe pulseaudio[19075]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:14 joe pulseaudio[19176]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:14 joe pulseaudio[19177]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:19 joe pulseaudio[19281]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:19 joe pulseaudio[19282]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:25 joe pulseaudio[19387]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:25 joe pulseaudio[19389]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:27 joe acpid: client 18948[0:0] has disconnected
Feb  1 19:50:27 joe acpid: client 18959[0:0] has disconnected
Feb  1 19:50:27 joe acpid: client 18950[0:0] has disconnected
Feb  1 19:50:27 joe acpid: client 18945[0:0] has disconnected
Feb  1 19:50:27 joe acpid: client 18947[0:0] has disconnected
Feb  1 19:50:27 joe acpid: client 18951[0:0] has disconnected
Feb  1 19:50:27 joe acpid: client 18954[0:0] has disconnected
Feb  1 19:50:27 joe acpid: client 18941[0:0] has disconnected
Feb  1 19:50:27 joe acpid: client 18955[0:0] has disconnected
Feb  1 19:50:27 joe acpid: client 18956[0:0] has disconnected
Feb  1 19:50:27 joe acpid: client 18957[0:0] has disconnected
Feb  1 19:50:27 joe acpid: client 18942[0:0] has disconnected
Feb  1 19:50:27 joe acpid: client 18944[0:0] has disconnected
Feb  1 19:50:27 joe acpid: client 18949[0:0] has disconnected
Feb  1 19:50:27 joe acpid: client 18953[0:0] has disconnected
Feb  1 19:50:27 joe acpid: client connected from 19455[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19442[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19460[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19456[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19451[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19440[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19469[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19470[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19467[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19452[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19458[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19475[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19457[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19464[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19448[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19449[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19471[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19463[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19474[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19473[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19454[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19453[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19472[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19450[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19459[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19466[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19468[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19443[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19441[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19462[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:27 joe acpid: client connected from 19465[0:0]
Feb  1 19:50:27 joe acpid: 1 client rule loaded
Feb  1 19:50:33 joe pulseaudio[19535]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:33 joe pulseaudio[19536]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:38 joe pulseaudio[19690]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:38 joe pulseaudio[19691]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:44 joe pulseaudio[19797]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:44 joe pulseaudio[19798]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:49 joe pulseaudio[19898]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:49 joe pulseaudio[19899]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:51 joe acpid: client 19455[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19442[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19460[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19456[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19451[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19440[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19469[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19470[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19467[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19452[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19458[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19475[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19457[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19464[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19448[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19449[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19471[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19463[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19474[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19473[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19454[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19453[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19472[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19450[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19459[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19466[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19468[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19443[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19441[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19462[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client 19465[0:0] has disconnected
Feb  1 19:50:51 joe acpid: client connected from 19948[0:0]
Feb  1 19:50:51 joe acpid: 1 client rule loaded
Feb  1 19:50:51 joe acpid: client connected from 19949[0:0]
Feb  1 19:50:51 joe acpid: 1 client rule loaded
Feb  1 19:50:51 joe acpid: client connected from 19952[0:0]
Feb  1 19:50:51 joe acpid: 1 client rule loaded
Feb  1 19:50:51 joe acpid: client connected from 19954[0:0]
Feb  1 19:50:51 joe acpid: 1 client rule loaded
Feb  1 19:50:51 joe acpid: client connected from 19953[0:0]
Feb  1 19:50:51 joe acpid: 1 client rule loaded
Feb  1 19:50:51 joe acpid: client connected from 19956[0:0]
Feb  1 19:50:51 joe acpid: 1 client rule loaded
Feb  1 19:50:51 joe acpid: client connected from 19955[0:0]
Feb  1 19:50:51 joe acpid: 1 client rule loaded
Feb  1 19:50:51 joe acpid: client connected from 19962[0:0]
Feb  1 19:50:51 joe acpid: 1 client rule loaded
Feb  1 19:50:51 joe acpid: client connected from 19965[0:0]
Feb  1 19:50:51 joe acpid: 1 client rule loaded
Feb  1 19:50:51 joe acpid: client connected from 19964[0:0]
Feb  1 19:50:51 joe acpid: 1 client rule loaded
Feb  1 19:50:51 joe acpid: client connected from 19968[0:0]
Feb  1 19:50:51 joe acpid: 1 client rule loaded
Feb  1 19:50:51 joe acpid: client connected from 19967[0:0]
Feb  1 19:50:51 joe acpid: 1 client rule loaded
Feb  1 19:50:51 joe acpid: client connected from 19969[0:0]
Feb  1 19:50:51 joe acpid: 1 client rule loaded
Feb  1 19:50:51 joe acpid: client connected from 19966[0:0]
Feb  1 19:50:51 joe acpid: 1 client rule loaded
Feb  1 19:50:54 joe pulseaudio[20021]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:54 joe pulseaudio[20042]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:59 joe pulseaudio[20131]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:50:59 joe pulseaudio[20152]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:03 joe pulseaudio[20230]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:04 joe pulseaudio[20261]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:08 joe pulseaudio[20333]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:09 joe pulseaudio[20364]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:13 joe pulseaudio[20440]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:14 joe acpid: client 19948[0:0] has disconnected
Feb  1 19:51:14 joe acpid: client 19949[0:0] has disconnected
Feb  1 19:51:14 joe acpid: client 19952[0:0] has disconnected
Feb  1 19:51:14 joe acpid: client 19954[0:0] has disconnected
Feb  1 19:51:14 joe acpid: client 19953[0:0] has disconnected
Feb  1 19:51:14 joe acpid: client 19956[0:0] has disconnected
Feb  1 19:51:14 joe acpid: client 19955[0:0] has disconnected
Feb  1 19:51:14 joe acpid: client 19962[0:0] has disconnected
Feb  1 19:51:14 joe acpid: client 19965[0:0] has disconnected
Feb  1 19:51:15 joe acpid: client 19964[0:0] has disconnected
Feb  1 19:51:15 joe pulseaudio[20475]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:15 joe acpid: client 19968[0:0] has disconnected
Feb  1 19:51:15 joe acpid: client 19967[0:0] has disconnected
Feb  1 19:51:15 joe acpid: client 19969[0:0] has disconnected
Feb  1 19:51:15 joe acpid: client 19966[0:0] has disconnected
Feb  1 19:51:15 joe acpid: client connected from 20450[0:0]
Feb  1 19:51:15 joe acpid: 1 client rule loaded
Feb  1 19:51:15 joe acpid: client 20450[0:0] has disconnected
Feb  1 19:51:15 joe acpid: client connected from 20451[0:0]
Feb  1 19:51:15 joe acpid: 1 client rule loaded
Feb  1 19:51:15 joe acpid: client 20451[0:0] has disconnected
Feb  1 19:51:15 joe acpid: client connected from 20457[0:0]
Feb  1 19:51:15 joe acpid: 1 client rule loaded
Feb  1 19:51:15 joe acpid: client 20457[0:0] has disconnected
Feb  1 19:51:15 joe acpid: client connected from 20452[0:0]
Feb  1 19:51:15 joe acpid: 1 client rule loaded
Feb  1 19:51:15 joe acpid: client 20452[0:0] has disconnected
Feb  1 19:51:15 joe acpid: client connected from 20453[0:0]
Feb  1 19:51:15 joe acpid: 1 client rule loaded
Feb  1 19:51:15 joe acpid: client 20453[0:0] has disconnected
Feb  1 19:51:15 joe acpid: client connected from 20456[0:0]
Feb  1 19:51:15 joe acpid: 1 client rule loaded
Feb  1 19:51:15 joe acpid: client 20456[0:0] has disconnected
Feb  1 19:51:15 joe acpid: client connected from 20463[0:0]
Feb  1 19:51:15 joe acpid: 1 client rule loaded
Feb  1 19:51:18 joe pulseaudio[20556]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:21 joe pulseaudio[20604]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:23 joe pulseaudio[20664]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:26 joe pulseaudio[20712]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:28 joe pulseaudio[20772]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:31 joe pulseaudio[20841]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:33 joe pulseaudio[20880]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:37 joe acpid: client 20463[0:0] has disconnected
Feb  1 19:51:37 joe acpid: client connected from 20959[0:0]
Feb  1 19:51:37 joe acpid: 1 client rule loaded
Feb  1 19:51:37 joe acpid: client connected from 20958[0:0]
Feb  1 19:51:37 joe acpid: 1 client rule loaded
Feb  1 19:51:37 joe acpid: client connected from 20960[0:0]
Feb  1 19:51:37 joe acpid: 1 client rule loaded
Feb  1 19:51:37 joe acpid: client connected from 20964[0:0]
Feb  1 19:51:37 joe acpid: 1 client rule loaded
Feb  1 19:51:37 joe acpid: client connected from 20975[0:0]
Feb  1 19:51:37 joe acpid: 1 client rule loaded
Feb  1 19:51:37 joe acpid: client connected from 20961[0:0]
Feb  1 19:51:37 joe pulseaudio[20949]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:37 joe acpid: 1 client rule loaded
Feb  1 19:51:37 joe acpid: client 20959[0:0] has disconnected
Feb  1 19:51:37 joe acpid: client 20958[0:0] has disconnected
Feb  1 19:51:37 joe acpid: client 20960[0:0] has disconnected
Feb  1 19:51:37 joe acpid: client 20964[0:0] has disconnected
Feb  1 19:51:37 joe acpid: client 20975[0:0] has disconnected
Feb  1 19:51:37 joe acpid: client 20961[0:0] has disconnected
Feb  1 19:51:37 joe acpid: client connected from 20967[0:0]
Feb  1 19:51:37 joe acpid: 1 client rule loaded
Feb  1 19:51:37 joe acpid: client 20967[0:0] has disconnected
Feb  1 19:51:37 joe acpid: client connected from 20970[0:0]
Feb  1 19:51:37 joe acpid: 1 client rule loaded
Feb  1 19:51:37 joe acpid: client 20970[0:0] has disconnected
Feb  1 19:51:37 joe acpid: client connected from 20963[0:0]
Feb  1 19:51:37 joe acpid: 1 client rule loaded
Feb  1 19:51:37 joe acpid: client 20963[0:0] has disconnected
Feb  1 19:51:37 joe acpid: client connected from 20971[0:0]
Feb  1 19:51:37 joe acpid: 1 client rule loaded
Feb  1 19:51:37 joe acpid: client 20971[0:0] has disconnected
Feb  1 19:51:37 joe acpid: client connected from 20973[0:0]
Feb  1 19:51:37 joe acpid: 1 client rule loaded
Feb  1 19:51:37 joe acpid: client 20973[0:0] has disconnected
Feb  1 19:51:37 joe acpid: client connected from 20962[0:0]
Feb  1 19:51:37 joe acpid: 1 client rule loaded
Feb  1 19:51:37 joe acpid: client 20962[0:0] has disconnected
Feb  1 19:51:37 joe acpid: client connected from 20972[0:0]
Feb  1 19:51:37 joe acpid: 1 client rule loaded
Feb  1 19:51:37 joe acpid: client 20972[0:0] has disconnected
Feb  1 19:51:37 joe acpid: client connected from 20974[0:0]
Feb  1 19:51:37 joe acpid: 1 client rule loaded
Feb  1 19:51:37 joe acpid: client 20974[0:0] has disconnected
Feb  1 19:51:37 joe acpid: client connected from 20969[0:0]
Feb  1 19:51:37 joe acpid: 1 client rule loaded
Feb  1 19:51:38 joe pulseaudio[21005]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:43 joe pulseaudio[21091]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:43 joe pulseaudio[21092]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:48 joe pulseaudio[21201]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:48 joe pulseaudio[21200]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:53 joe pulseaudio[21307]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:53 joe pulseaudio[21309]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:58 joe pulseaudio[21420]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:51:58 joe pulseaudio[21419]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:01 joe acpid: client 20969[0:0] has disconnected
Feb  1 19:52:01 joe acpid: client connected from 21478[0:0]
Feb  1 19:52:01 joe acpid: 1 client rule loaded
Feb  1 19:52:01 joe acpid: client connected from 21476[0:0]
Feb  1 19:52:01 joe acpid: 1 client rule loaded
Feb  1 19:52:01 joe acpid: client connected from 21479[0:0]
Feb  1 19:52:01 joe acpid: 1 client rule loaded
Feb  1 19:52:01 joe acpid: client connected from 21480[0:0]
Feb  1 19:52:01 joe acpid: 1 client rule loaded
Feb  1 19:52:01 joe acpid: client connected from 21474[0:0]
Feb  1 19:52:01 joe acpid: 1 client rule loaded
Feb  1 19:52:01 joe acpid: client connected from 21473[0:0]
Feb  1 19:52:01 joe acpid: 1 client rule loaded
Feb  1 19:52:01 joe acpid: client connected from 21477[0:0]
Feb  1 19:52:01 joe acpid: 1 client rule loaded
Feb  1 19:52:01 joe acpid: client connected from 21475[0:0]
Feb  1 19:52:01 joe acpid: 1 client rule loaded
Feb  1 19:52:04 joe pulseaudio[21533]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:04 joe pulseaudio[21534]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:09 joe pulseaudio[21658]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:09 joe pulseaudio[21659]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:14 joe pulseaudio[21766]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:14 joe pulseaudio[21767]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:19 joe pulseaudio[21874]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:19 joe pulseaudio[21875]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:24 joe pulseaudio[21992]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:24 joe pulseaudio[21991]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:24 joe acpid: client 21478[0:0] has disconnected
Feb  1 19:52:24 joe acpid: client 21476[0:0] has disconnected
Feb  1 19:52:24 joe acpid: client 21479[0:0] has disconnected
Feb  1 19:52:24 joe acpid: client 21480[0:0] has disconnected
Feb  1 19:52:24 joe acpid: client 21474[0:0] has disconnected
Feb  1 19:52:24 joe acpid: client 21473[0:0] has disconnected
Feb  1 19:52:24 joe acpid: client 21477[0:0] has disconnected
Feb  1 19:52:24 joe acpid: client 21475[0:0] has disconnected
Feb  1 19:52:24 joe acpid: client connected from 22000[0:0]
Feb  1 19:52:24 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22003[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22001[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22008[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22011[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22014[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22017[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client 22000[0:0] has disconnected
Feb  1 19:52:25 joe acpid: client connected from 22007[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22005[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22013[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22015[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22006[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22018[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22023[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22024[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22026[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22016[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22020[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22022[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client connected from 22021[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:25 joe acpid: client 22003[0:0] has disconnected
Feb  1 19:52:25 joe acpid: client 22001[0:0] has disconnected
Feb  1 19:52:25 joe acpid: client 22007[0:0] has disconnected
Feb  1 19:52:25 joe acpid: client 22013[0:0] has disconnected
Feb  1 19:52:25 joe acpid: client connected from 22035[0:0]
Feb  1 19:52:25 joe acpid: 1 client rule loaded
Feb  1 19:52:29 joe pulseaudio[22132]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:29 joe pulseaudio[22133]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:34 joe pulseaudio[22232]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:34 joe pulseaudio[22230]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:39 joe pulseaudio[22341]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:39 joe pulseaudio[22346]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:45 joe pulseaudio[22455]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:45 joe pulseaudio[22456]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:48 joe acpid: client 22008[0:0] has disconnected
Feb  1 19:52:48 joe acpid: client 22011[0:0] has disconnected
Feb  1 19:52:48 joe acpid: client 22014[0:0] has disconnected
Feb  1 19:52:48 joe acpid: client 22017[0:0] has disconnected
Feb  1 19:52:48 joe acpid: client 22005[0:0] has disconnected
Feb  1 19:52:48 joe acpid: client 22015[0:0] has disconnected
Feb  1 19:52:48 joe acpid: client 22006[0:0] has disconnected
Feb  1 19:52:48 joe acpid: client 22018[0:0] has disconnected
Feb  1 19:52:48 joe acpid: client 22023[0:0] has disconnected
Feb  1 19:52:48 joe acpid: client 22024[0:0] has disconnected
Feb  1 19:52:48 joe acpid: client 22026[0:0] has disconnected
Feb  1 19:52:48 joe acpid: client 22016[0:0] has disconnected
Feb  1 19:52:48 joe acpid: client 22020[0:0] has disconnected
Feb  1 19:52:48 joe acpid: client 22022[0:0] has disconnected
Feb  1 19:52:48 joe acpid: client 22021[0:0] has disconnected
Feb  1 19:52:48 joe acpid: client 22035[0:0] has disconnected
Feb  1 19:52:48 joe acpid: client connected from 22521[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22519[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22523[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22517[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22525[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22522[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22518[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22520[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22536[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22542[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22535[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22540[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22534[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22537[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22550[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22547[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22545[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22546[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:48 joe acpid: client connected from 22548[0:0]
Feb  1 19:52:48 joe acpid: 1 client rule loaded
Feb  1 19:52:50 joe pulseaudio[22585]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:50 joe pulseaudio[22584]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:56 joe pulseaudio[22696]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:52:56 joe pulseaudio[22695]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:01 joe pulseaudio[22806]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:01 joe pulseaudio[22808]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:06 joe pulseaudio[22945]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:06 joe pulseaudio[22944]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:10 joe pulseaudio[23064]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:10 joe pulseaudio[23065]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:12 joe acpid: client 22521[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22519[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22523[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22517[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22525[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22522[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22518[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22520[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22536[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22542[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22535[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22540[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22534[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22537[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22550[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22547[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22545[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22546[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client 22548[0:0] has disconnected
Feb  1 19:53:12 joe acpid: client connected from 23201[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23209[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23203[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23204[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23213[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23212[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23211[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23208[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23215[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23205[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23202[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23217[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23214[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23220[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23206[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23216[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23236[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23237[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:12 joe acpid: client connected from 23235[0:0]
Feb  1 19:53:12 joe acpid: 1 client rule loaded
Feb  1 19:53:15 joe pulseaudio[23290]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:15 joe pulseaudio[23291]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:21 joe pulseaudio[23470]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:21 joe pulseaudio[23468]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:26 joe pulseaudio[23578]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:26 joe pulseaudio[23580]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:31 joe pulseaudio[23683]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:31 joe pulseaudio[23684]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:35 joe acpid: client 23201[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23209[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23203[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23204[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23213[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23212[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23211[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23208[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23215[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23205[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23202[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23217[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23214[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23220[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23206[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23216[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23236[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23237[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23235[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client connected from 23762[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:35 joe acpid: client connected from 23761[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:35 joe acpid: client connected from 23764[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:35 joe acpid: client connected from 23765[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:35 joe acpid: client connected from 23766[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:35 joe acpid: client connected from 23763[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:35 joe acpid: client connected from 23760[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:35 joe acpid: client connected from 23775[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:35 joe acpid: client connected from 23779[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:35 joe acpid: client 23762[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client 23765[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client connected from 23781[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:35 joe acpid: client connected from 23782[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:35 joe acpid: client 23761[0:0] has disconnected
Feb  1 19:53:35 joe acpid: client connected from 23783[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:35 joe acpid: client connected from 23776[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:35 joe acpid: client connected from 23784[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:35 joe acpid: client connected from 23785[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:35 joe acpid: client connected from 23780[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:35 joe acpid: client connected from 23777[0:0]
Feb  1 19:53:35 joe acpid: 1 client rule loaded
Feb  1 19:53:36 joe pulseaudio[23813]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:36 joe pulseaudio[23814]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:41 joe pulseaudio[23918]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:41 joe pulseaudio[23917]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:46 joe pulseaudio[24022]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:46 joe pulseaudio[24023]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:48 joe acpid: client 23764[0:0] has disconnected
Feb  1 19:53:48 joe acpid: client 23766[0:0] has disconnected
Feb  1 19:53:48 joe acpid: client 23763[0:0] has disconnected
Feb  1 19:53:48 joe acpid: client 23760[0:0] has disconnected
Feb  1 19:53:48 joe acpid: client 23775[0:0] has disconnected
Feb  1 19:53:48 joe acpid: client 23779[0:0] has disconnected
Feb  1 19:53:48 joe acpid: client 23781[0:0] has disconnected
Feb  1 19:53:48 joe acpid: client 23782[0:0] has disconnected
Feb  1 19:53:48 joe acpid: client 23783[0:0] has disconnected
Feb  1 19:53:48 joe acpid: client 23776[0:0] has disconnected
Feb  1 19:53:48 joe acpid: client 23784[0:0] has disconnected
Feb  1 19:53:48 joe acpid: client 23785[0:0] has disconnected
Feb  1 19:53:48 joe acpid: client 23780[0:0] has disconnected
Feb  1 19:53:48 joe acpid: client 23777[0:0] has disconnected
Feb  1 19:53:51 joe pulseaudio[24124]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:51 joe pulseaudio[24125]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:56 joe pulseaudio[24226]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:53:56 joe pulseaudio[24228]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:01 joe acpid: client connected from 24282[0:0]
Feb  1 19:54:01 joe acpid: 1 client rule loaded
Feb  1 19:54:01 joe acpid: client connected from 24279[0:0]
Feb  1 19:54:01 joe acpid: 1 client rule loaded
Feb  1 19:54:01 joe acpid: client connected from 24280[0:0]
Feb  1 19:54:01 joe acpid: 1 client rule loaded
Feb  1 19:54:01 joe acpid: client 24282[0:0] has disconnected
Feb  1 19:54:01 joe acpid: client 24279[0:0] has disconnected
Feb  1 19:54:01 joe acpid: client 24280[0:0] has disconnected
Feb  1 19:54:01 joe acpid: client connected from 24278[0:0]
Feb  1 19:54:01 joe acpid: 1 client rule loaded
Feb  1 19:54:01 joe acpid: client 24278[0:0] has disconnected
Feb  1 19:54:01 joe acpid: client connected from 24281[0:0]
Feb  1 19:54:01 joe acpid: 1 client rule loaded
Feb  1 19:54:01 joe pulseaudio[24326]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:01 joe pulseaudio[24327]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:06 joe pulseaudio[24420]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:06 joe pulseaudio[24421]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:11 joe pulseaudio[24523]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:11 joe pulseaudio[24524]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:16 joe pulseaudio[24624]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:16 joe pulseaudio[24625]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:21 joe pulseaudio[24726]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:21 joe pulseaudio[24727]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:24 joe gdm-simple-slave[19977]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[19978]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[19979]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[19980]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[19981]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[19982]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[19983]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[19984]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[19985]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[19986]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[19987]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[19988]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[19989]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[19990]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20466]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20467]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20468]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20470]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20469]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20471]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20472]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20989]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20990]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20991]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20992]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20993]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20994]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20995]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20996]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20997]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20998]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22581]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23234]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23241]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23242]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23243]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23244]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23245]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23246]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23247]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23248]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23249]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22047]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22048]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22052]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22050]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22053]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22056]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[21999]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22054]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[21528]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22049]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[21527]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22060]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22061]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22064]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22059]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22063]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22057]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22065]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22058]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23797]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23798]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23799]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23809]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22561]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23815]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22533]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22557]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22560]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22562]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22563]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22564]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22565]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22568]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22571]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22572]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22573]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22576]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22577]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22578]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22579]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22580]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23250]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23251]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23252]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23253]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23254]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23255]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23256]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23257]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23258]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23772]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23796]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[21003]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[21002]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[21523]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[21000]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[21522]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[21526]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[21001]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[21525]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[21520]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[21524]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[20999]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23800]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23802]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23804]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23801]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23803]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23806]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23805]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23808]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23807]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[23810]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22066]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22062]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22067]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22559]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe gdm-simple-slave[22068]: WARNING: Failed to get value: 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. 
Feb  1 19:54:24 joe acpid: client 24281[0:0] has disconnected
Feb  1 19:54:24 joe acpid: client connected from 24794[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24780[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24781[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24785[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24776[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24769[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24782[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24791[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24770[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24784[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24787[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24774[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24773[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24798[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24796[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24779[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24783[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24793[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24797[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24788[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24777[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24800[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24790[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24778[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24775[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe acpid: client connected from 24799[0:0]
Feb  1 19:54:24 joe acpid: 1 client rule loaded
Feb  1 19:54:24 joe gdm-simple-slave[24277]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display50580: 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. 
Feb  1 19:54:30 joe gdm-simple-slave[24289]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display50581: 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. 
Feb  1 19:54:30 joe gdm-simple-slave[24290]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display50582: 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. 
Feb  1 19:54:30 joe gdm-simple-slave[24291]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display50583: 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. 
Feb  1 19:54:30 joe acpid: client connected from 24840[0:0]
Feb  1 19:54:30 joe acpid: 1 client rule loaded
Feb  1 19:54:30 joe acpid: client connected from 24836[0:0]
Feb  1 19:54:30 joe acpid: 1 client rule loaded
Feb  1 19:54:30 joe acpid: client connected from 24834[0:0]
Feb  1 19:54:30 joe acpid: 1 client rule loaded
Feb  1 19:54:30 joe pulseaudio[25050]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:30 joe pulseaudio[25048]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:31 joe acpid: client 24794[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24780[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24781[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24785[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24776[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24769[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24782[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24791[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24770[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24784[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24787[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24774[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24773[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24798[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24796[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24779[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24783[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24793[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24797[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24788[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24777[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24800[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24790[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24778[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24775[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24799[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24840[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24836[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client 24834[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client connected from 24841[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client 24841[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client connected from 24854[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client 24854[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client connected from 24847[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client 24847[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client connected from 24838[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client 24838[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client connected from 24870[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client 24870[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client connected from 24852[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client 24852[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client connected from 24872[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client 24872[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client connected from 24846[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client 24846[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client connected from 24875[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client 24875[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client connected from 24877[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client 24877[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client connected from 24876[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client 24876[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client connected from 24849[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24851[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24880[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24878[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24885[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24884[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24887[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24882[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24881[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24886[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24879[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24853[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24835[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24848[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24883[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24869[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24850[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24888[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24911[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24914[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24918[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24919[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client 24835[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client connected from 24910[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24916[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24920[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24917[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24908[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24909[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24978[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24968[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24972[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24966[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24973[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24975[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24977[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24970[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24967[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24980[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24971[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24976[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24839[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24969[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24913[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24844[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24912[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24974[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24873[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client 24879[0:0] has disconnected
Feb  1 19:54:31 joe acpid: client connected from 24979[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24837[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24915[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:31 joe acpid: client connected from 24871[0:0]
Feb  1 19:54:31 joe acpid: 1 client rule loaded
Feb  1 19:54:35 joe pulseaudio[25172]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:35 joe pulseaudio[25173]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:40 joe pulseaudio[25232]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:40 joe pulseaudio[25230]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:45 joe pulseaudio[25335]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:45 joe pulseaudio[25333]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:51 joe pulseaudio[25466]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:51 joe pulseaudio[25465]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:56 joe pulseaudio[25567]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:54:56 joe pulseaudio[25566]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:01 joe pulseaudio[25664]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:01 joe pulseaudio[25665]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:06 joe pulseaudio[25759]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:06 joe pulseaudio[25757]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:12 joe pulseaudio[25860]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:12 joe pulseaudio[25861]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:17 joe pulseaudio[25973]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:17 joe pulseaudio[25972]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:22 joe pulseaudio[26073]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:22 joe pulseaudio[26074]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:27 joe pulseaudio[26175]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:27 joe pulseaudio[26176]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:33 joe pulseaudio[26276]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:33 joe pulseaudio[26275]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:37 joe pulseaudio[26352]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:37 joe gdm-simple-slave[25083]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25084]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25085]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25086]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25087]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25088]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25089]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25090]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25091]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25092]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25093]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25094]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25095]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25096]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25097]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25098]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25099]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25100]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25102]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25103]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25104]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25105]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25106]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25107]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25108]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25109]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25110]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25111]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25112]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25116]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25042]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25043]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25044]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25115]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25118]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25114]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25120]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25045]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25049]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25051]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25124]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25128]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25130]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25129]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25125]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25133]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25127]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25126]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25135]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25134]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25131]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25146]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25138]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25137]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25140]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25145]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25144]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25136]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25139]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25142]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25143]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25141]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25150]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25433]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25434]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25435]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25436]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25437]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25147]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25153]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25148]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25151]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25149]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23772]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25062]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25058]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25063]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25056]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25061]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25057]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25438]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25439]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25081]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25079]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25080]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25065]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25066]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25067]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25068]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25069]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25070]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25071]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25072]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25073]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25074]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25075]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25076]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25155]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25156]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25157]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25158]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25159]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25160]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25161]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25162]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25163]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25164]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25165]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25166]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25167]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25168]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25169]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25077]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25078]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25394]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25397]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25432]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25119]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25123]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25117]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25122]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25113]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25121]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25152]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25154]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25053]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25052]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25101]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25082]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25055]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25060]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25054]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25059]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[25064]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23796]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23797]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23798]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23799]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23815]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23800]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23801]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23802]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23803]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23804]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23805]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23806]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23807]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23808]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[24292]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23809]: WARNING: Failed to get value: 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. 
Feb  1 19:55:37 joe gdm-simple-slave[23810]: WARNING: Failed to get value: 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. 
Feb  1 19:55:40 joe pulseaudio[26601]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:41 joe acpid: client 24849[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24851[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24880[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24878[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24885[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24884[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24887[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24882[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24881[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24886[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24853[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24848[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24883[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24869[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24850[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24888[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24911[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24914[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24918[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24919[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24910[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24916[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24920[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24917[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24908[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24909[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24978[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24968[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24972[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24966[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24973[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24975[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24977[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24970[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24967[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24980[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24971[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24976[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24839[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24969[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24913[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24844[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24912[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24974[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24873[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24979[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24837[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24915[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client 24871[0:0] has disconnected
Feb  1 19:55:41 joe acpid: client connected from 26481[0:0]
Feb  1 19:55:41 joe acpid: 1 client rule loaded
Feb  1 19:55:41 joe acpid: client connected from 26541[0:0]
Feb  1 19:55:41 joe acpid: 1 client rule loaded
Feb  1 19:55:42 joe pulseaudio[26665]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:43 joe pulseaudio[26685]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:47 joe pulseaudio[26770]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:48 joe pulseaudio[26788]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:52 joe pulseaudio[26859]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:53 joe pulseaudio[26878]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:57 joe pulseaudio[26967]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:55:58 joe pulseaudio[26988]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:02 joe acpid: client 26481[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client 26541[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client connected from 27023[0:0]
Feb  1 19:56:02 joe acpid: 1 client rule loaded
Feb  1 19:56:02 joe acpid: client 27023[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client connected from 27038[0:0]
Feb  1 19:56:02 joe acpid: 1 client rule loaded
Feb  1 19:56:02 joe acpid: client 27038[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client connected from 27032[0:0]
Feb  1 19:56:02 joe acpid: 1 client rule loaded
Feb  1 19:56:02 joe acpid: client 27032[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client connected from 27036[0:0]
Feb  1 19:56:02 joe acpid: 1 client rule loaded
Feb  1 19:56:02 joe acpid: client 27036[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client connected from 27040[0:0]
Feb  1 19:56:02 joe pulseaudio[27091]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:02 joe acpid: 1 client rule loaded
Feb  1 19:56:02 joe acpid: client 27040[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client connected from 27037[0:0]
Feb  1 19:56:02 joe acpid: 1 client rule loaded
Feb  1 19:56:02 joe acpid: client 27037[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client connected from 27041[0:0]
Feb  1 19:56:02 joe acpid: 1 client rule loaded
Feb  1 19:56:02 joe acpid: client 27041[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client connected from 27048[0:0]
Feb  1 19:56:02 joe acpid: 1 client rule loaded
Feb  1 19:56:02 joe acpid: client 27048[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client connected from 27043[0:0]
Feb  1 19:56:02 joe acpid: 1 client rule loaded
Feb  1 19:56:02 joe acpid: client 27043[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client connected from 27044[0:0]
Feb  1 19:56:02 joe acpid: 1 client rule loaded
Feb  1 19:56:02 joe acpid: client 27044[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client connected from 27042[0:0]
Feb  1 19:56:02 joe acpid: 1 client rule loaded
Feb  1 19:56:02 joe acpid: client 27042[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client connected from 27046[0:0]
Feb  1 19:56:02 joe acpid: 1 client rule loaded
Feb  1 19:56:02 joe acpid: client 27046[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client connected from 27047[0:0]
Feb  1 19:56:02 joe acpid: 1 client rule loaded
Feb  1 19:56:02 joe acpid: client 27047[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client connected from 27031[0:0]
Feb  1 19:56:02 joe acpid: 1 client rule loaded
Feb  1 19:56:02 joe acpid: client 27031[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client connected from 27039[0:0]
Feb  1 19:56:02 joe acpid: 1 client rule loaded
Feb  1 19:56:02 joe acpid: client 27039[0:0] has disconnected
Feb  1 19:56:02 joe acpid: client connected from 27033[0:0]
Feb  1 19:56:02 joe acpid: 1 client rule loaded
Feb  1 19:56:03 joe pulseaudio[27110]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:08 joe pulseaudio[27221]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:08 joe pulseaudio[27223]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:13 joe pulseaudio[27328]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:13 joe pulseaudio[27329]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:18 joe pulseaudio[27436]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:18 joe pulseaudio[27437]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:23 joe pulseaudio[27548]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:23 joe pulseaudio[27547]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:25 joe gdm-simple-slave[26666]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26667]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26668]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26669]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26670]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26671]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26672]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26673]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26674]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26676]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26677]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26678]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26679]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26683]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26692]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26694]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26695]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26698]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26700]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26704]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26706]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26707]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26709]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26717]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26719]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26720]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26722]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26723]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26724]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26725]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26726]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26727]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26728]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26729]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26730]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26731]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26732]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26733]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26734]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26735]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26736]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26737]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26738]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26741]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26742]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26747]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26748]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26749]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26750]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26751]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26752]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[25437]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26754]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26755]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26756]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26757]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26758]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26760]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26761]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26762]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26763]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26764]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26765]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26766]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26767]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26768]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26771]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26772]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26773]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26774]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26775]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26776]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26777]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26778]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26779]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26780]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26781]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26782]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26783]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26784]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26785]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26786]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26789]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26790]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26791]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26792]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26793]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[25394]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[25397]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[25432]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[25433]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[25434]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[25435]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[25436]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26753]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[25438]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[25439]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26619]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26620]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26621]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26622]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26623]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26624]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26625]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26626]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26627]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26628]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26629]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26630]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26631]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26632]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26633]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26634]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26635]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26637]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26642]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26636]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26640]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26649]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26650]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26651]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26653]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26654]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26655]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26656]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26657]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26658]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26659]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26660]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26661]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26662]: WARNING: Failed to get value: 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. 
Feb  1 19:56:25 joe gdm-simple-slave[26663]: WARNING: Failed to get value: 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. 
Feb  1 19:56:28 joe gdm-simple-slave[27050]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display51677: 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. 
Feb  1 19:56:28 joe gdm-simple-slave[27067]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display51678: 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. 
Feb  1 19:56:28 joe acpid: client 27033[0:0] has disconnected
Feb  1 19:56:28 joe acpid: client connected from 27597[0:0]
Feb  1 19:56:28 joe acpid: 1 client rule loaded
Feb  1 19:56:28 joe acpid: client 27597[0:0] has disconnected
Feb  1 19:56:28 joe acpid: client connected from 27599[0:0]
Feb  1 19:56:28 joe acpid: 1 client rule loaded
Feb  1 19:56:28 joe acpid: client 27599[0:0] has disconnected
Feb  1 19:56:28 joe acpid: client connected from 27598[0:0]
Feb  1 19:56:28 joe acpid: 1 client rule loaded
Feb  1 19:56:29 joe pulseaudio[27646]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:29 joe pulseaudio[27645]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:34 joe pulseaudio[27745]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:34 joe pulseaudio[27746]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:39 joe pulseaudio[27844]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:39 joe pulseaudio[27845]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:44 joe pulseaudio[27948]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:44 joe pulseaudio[27949]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:49 joe pulseaudio[28050]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:49 joe pulseaudio[28051]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:50 joe gdm-simple-slave[26786]: WARNING: Failed to get value: 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. 
Feb  1 19:56:50 joe gdm-simple-slave[26789]: WARNING: Failed to get value: 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. 
Feb  1 19:56:50 joe gdm-simple-slave[26790]: WARNING: Failed to get value: 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. 
Feb  1 19:56:50 joe gdm-simple-slave[26791]: WARNING: Failed to get value: 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. 
Feb  1 19:56:50 joe gdm-simple-slave[26792]: WARNING: Failed to get value: 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. 
Feb  1 19:56:50 joe gdm-simple-slave[26793]: WARNING: Failed to get value: 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. 
Feb  1 19:56:50 joe gdm-simple-slave[26753]: WARNING: Failed to get value: 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. 
Feb  1 19:56:50 joe acpid: client 27598[0:0] has disconnected
Feb  1 19:56:50 joe acpid: client connected from 28066[0:0]
Feb  1 19:56:50 joe acpid: 1 client rule loaded
Feb  1 19:56:50 joe acpid: client connected from 28064[0:0]
Feb  1 19:56:50 joe acpid: 1 client rule loaded
Feb  1 19:56:50 joe acpid: client connected from 28069[0:0]
Feb  1 19:56:50 joe acpid: 1 client rule loaded
Feb  1 19:56:50 joe acpid: client connected from 28067[0:0]
Feb  1 19:56:50 joe acpid: 1 client rule loaded
Feb  1 19:56:50 joe acpid: client 28064[0:0] has disconnected
Feb  1 19:56:50 joe acpid: client 28069[0:0] has disconnected
Feb  1 19:56:50 joe acpid: client 28067[0:0] has disconnected
Feb  1 19:56:50 joe acpid: client connected from 28070[0:0]
Feb  1 19:56:50 joe acpid: 1 client rule loaded
Feb  1 19:56:50 joe acpid: client connected from 28068[0:0]
Feb  1 19:56:50 joe acpid: 1 client rule loaded
Feb  1 19:56:50 joe acpid: client connected from 28065[0:0]
Feb  1 19:56:50 joe acpid: 1 client rule loaded
Feb  1 19:56:51 joe gdm-simple-slave[27068]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[27069]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[27070]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[27071]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[27073]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[27074]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[27075]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[27076]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[27077]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[27078]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[27079]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[27080]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[27081]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[27082]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[27083]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[27087]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[27088]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26666]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26667]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26668]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26669]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26670]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26678]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26679]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26683]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26692]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26694]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26695]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26698]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26700]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26704]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26706]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26707]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26728]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26724]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26726]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26725]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26727]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26720]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26719]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26722]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26709]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26717]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26723]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26729]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26673]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26674]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26677]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26676]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26671]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26672]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26730]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26731]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26732]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26733]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26763]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26741]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26762]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26738]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26761]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26747]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26760]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26742]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26758]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26735]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26771]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26737]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26768]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26757]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26767]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26751]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26766]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26755]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26765]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26752]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26764]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26754]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26772]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26736]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26734]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26750]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26749]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26748]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26773]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26774]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26775]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26776]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26777]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26778]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26779]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26780]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26756]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26781]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26782]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26783]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26784]: WARNING: Failed to get value: 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. 
Feb  1 19:56:51 joe gdm-simple-slave[26785]: WARNING: Failed to get value: 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. 
Feb  1 19:56:55 joe pulseaudio[28247]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:56:55 joe pulseaudio[28251]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:00 joe pulseaudio[28345]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:00 joe pulseaudio[28346]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:05 joe pulseaudio[28445]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:05 joe pulseaudio[28447]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:10 joe pulseaudio[28546]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:10 joe pulseaudio[28548]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:15 joe pulseaudio[28646]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:15 joe pulseaudio[28648]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:15 joe gdm-simple-slave[28149]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52101: 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. 
Feb  1 19:57:15 joe gdm-simple-slave[28150]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52102: 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. 
Feb  1 19:57:15 joe gdm-simple-slave[28151]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52103: 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. 
Feb  1 19:57:15 joe gdm-simple-slave[28152]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52104: 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. 
Feb  1 19:57:15 joe gdm-simple-slave[28153]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52105: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[28154]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52106: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[28155]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52107: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[28156]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52108: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27068]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27069]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27070]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27071]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27073]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27074]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27075]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27076]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27077]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27078]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27079]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27080]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27081]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27082]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27083]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27087]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[27088]: WARNING: Failed to get value: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[28159]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52109: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[28163]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52110: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[28164]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52111: 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. 
Feb  1 19:57:16 joe gdm-simple-slave[28165]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52112: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28166]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52113: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[27605]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[27606]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[27607]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28063]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28167]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52114: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28183]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52115: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28184]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52116: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28185]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52117: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28186]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52118: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28187]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52119: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28188]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52120: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28189]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52121: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28190]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52122: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28193]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52124: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28192]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52123: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28194]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52125: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28195]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52126: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28212]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52127: 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. 
Feb  1 19:57:17 joe gdm-simple-slave[28213]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52128: 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. 
Feb  1 19:57:18 joe gdm-simple-slave[28214]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52129: 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. 
Feb  1 19:57:18 joe gdm-simple-slave[28215]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52130: 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. 
Feb  1 19:57:18 joe gdm-simple-slave[28216]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52131: 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. 
Feb  1 19:57:18 joe gdm-simple-slave[28217]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52132: 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. 
Feb  1 19:57:18 joe gdm-simple-slave[28218]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52133: 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. 
Feb  1 19:57:21 joe pulseaudio[28969]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:21 joe pulseaudio[28970]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:26 joe pulseaudio[29101]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:26 joe pulseaudio[29102]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:31 joe pulseaudio[29206]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:31 joe pulseaudio[29207]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:35 joe pulseaudio[29290]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:35 joe pulseaudio[29291]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:40 joe pulseaudio[29387]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:40 joe pulseaudio[29388]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:43 joe gdm-simple-slave[28219]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28220]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28221]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28222]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28223]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28224]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28225]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28226]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28227]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28228]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28235]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28245]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28248]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28249]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28252]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28281]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28282]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[27605]: WARNING: Failed to get value: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[27606]: WARNING: Failed to get value: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[27607]: WARNING: Failed to get value: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28063]: WARNING: Failed to get value: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28840]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28838]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28841]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28847]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28846]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28947]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52349: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28948]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52350: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28949]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52351: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28950]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52352: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28951]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52353: 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. 
Feb  1 19:57:43 joe gdm-simple-slave[28952]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52354: 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. 
Feb  1 19:57:44 joe gdm-simple-slave[28954]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52355: 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. 
Feb  1 19:57:44 joe gdm-simple-slave[28955]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52356: 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. 
Feb  1 19:57:44 joe gdm-simple-slave[28956]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52357: 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. 
Feb  1 19:57:44 joe gdm-simple-slave[28957]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52358: 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. 
Feb  1 19:57:44 joe gdm-simple-slave[28958]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52359: 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. 
Feb  1 19:57:44 joe gdm-simple-slave[28959]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52360: 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. 
Feb  1 19:57:44 joe gdm-simple-slave[28961]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52361: 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. 
Feb  1 19:57:44 joe gdm-simple-slave[28963]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52362: 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. 
Feb  1 19:57:44 joe gdm-simple-slave[28966]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52363: 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. 
Feb  1 19:57:44 joe gdm-simple-slave[28971]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52364: 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. 
Feb  1 19:57:44 joe gdm-simple-slave[28974]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52365: 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. 
Feb  1 19:57:44 joe gdm-simple-slave[28977]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52366: 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. 
Feb  1 19:57:44 joe gdm-simple-slave[28986]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52367: 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. 
Feb  1 19:57:45 joe gdm-simple-slave[28987]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52368: 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. 
Feb  1 19:57:45 joe gdm-simple-slave[28988]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52369: 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. 
Feb  1 19:57:45 joe gdm-simple-slave[28989]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52370: 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. 
Feb  1 19:57:45 joe gdm-simple-slave[28990]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52371: 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. 
Feb  1 19:57:45 joe gdm-simple-slave[28991]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52372: 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. 
Feb  1 19:57:45 joe pulseaudio[29537]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:45 joe pulseaudio[29535]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:50 joe pulseaudio[29629]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:50 joe pulseaudio[29630]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:55 joe pulseaudio[29721]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:57:55 joe pulseaudio[29723]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:00 joe pulseaudio[29821]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:00 joe pulseaudio[29822]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:05 joe pulseaudio[29914]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:05 joe pulseaudio[29915]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:10 joe gdm-simple-slave[29030]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29031]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29032]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29033]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29034]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29035]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29036]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29037]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29038]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29039]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29040]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29041]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29042]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29043]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29044]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29045]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29046]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29047]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29048]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29049]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29050]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29051]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29052]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29053]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29054]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29055]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29056]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29057]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29058]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29059]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29060]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29061]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29062]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29063]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29064]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29065]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29066]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29067]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29068]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29069]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29070]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29071]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29072]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29073]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29081]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29089]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29098]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29103]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29104]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29105]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29106]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29107]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29108]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29111]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29119]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29110]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28224]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28225]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28226]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28227]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28228]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28235]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28245]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28248]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28219]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28223]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28222]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28221]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28220]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29120]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29121]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29124]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29123]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29122]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29125]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28249]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28252]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28281]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28282]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29109]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29118]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29116]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29117]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29114]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29115]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29113]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29112]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29444]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28838]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28840]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28841]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28847]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28846]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[28998]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29002]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29001]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29003]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29004]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29009]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29005]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29008]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29006]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29007]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29010]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29011]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29012]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29013]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29014]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29015]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29016]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29017]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29018]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29019]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29020]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29028]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29029]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29025]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29027]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29024]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29023]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29022]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29026]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe gdm-simple-slave[29021]: WARNING: Failed to get value: 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. 
Feb  1 19:58:10 joe pulseaudio[30011]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:10 joe pulseaudio[30010]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:16 joe pulseaudio[30116]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:16 joe pulseaudio[30117]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:21 joe pulseaudio[30217]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:21 joe pulseaudio[30216]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:26 joe pulseaudio[30313]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:26 joe pulseaudio[30314]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:31 joe pulseaudio[30411]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:31 joe pulseaudio[30412]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:35 joe gdm-simple-slave[29072]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29073]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29081]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29089]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29098]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29103]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29104]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29105]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29106]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29107]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29108]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29110]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29111]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29119]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29120]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29121]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29122]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29123]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29124]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29125]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29118]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29114]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29444]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29113]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29117]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29112]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29116]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29109]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29115]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29539]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29583]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29584]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29585]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29586]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29587]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29588]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29589]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29590]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29591]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29592]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29593]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29594]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29595]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29596]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29597]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29598]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29599]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29600]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29601]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29602]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29616]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29617]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29618]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29619]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29030]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29031]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29032]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29033]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29034]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29035]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29036]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29615]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29614]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29613]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29037]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29038]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29039]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29040]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29041]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29042]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29043]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29044]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29045]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29046]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29047]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29053]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29054]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29055]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29056]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29057]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29058]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29059]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29060]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29061]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29051]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29052]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29049]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29048]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29050]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29062]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29063]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29064]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29065]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29066]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29067]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29068]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29069]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29070]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[29071]: WARNING: Failed to get value: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[30015]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52845: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[30019]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52846: 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. 
Feb  1 19:58:35 joe gdm-simple-slave[30020]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display52847: 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. 
Feb  1 19:58:36 joe gdm-simple-slave[30614]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 19:58:36 joe pulseaudio[30626]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:36 joe pulseaudio[30627]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:41 joe pulseaudio[30844]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:41 joe pulseaudio[30843]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:46 joe pulseaudio[30932]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:46 joe pulseaudio[30933]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:51 joe pulseaudio[31031]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:51 joe pulseaudio[31032]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:56 joe pulseaudio[31129]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:58:56 joe pulseaudio[31130]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:02 joe pulseaudio[31226]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:02 joe pulseaudio[31225]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:02 joe gdm-simple-slave[29539]: WARNING: Failed to get value: 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. 
Feb  1 19:59:02 joe gdm-simple-slave[29583]: WARNING: Failed to get value: 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. 
Feb  1 19:59:08 joe pulseaudio[31321]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:08 joe pulseaudio[31322]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:13 joe pulseaudio[31419]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:13 joe pulseaudio[31420]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:18 joe pulseaudio[31520]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:18 joe pulseaudio[31521]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:23 joe pulseaudio[31618]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:23 joe pulseaudio[31620]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:26 joe gdm-simple-slave[29586]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29587]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29588]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29589]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29590]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29591]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29592]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29593]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29594]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29595]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29596]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29597]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29598]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29599]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29600]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29601]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29602]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29613]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29614]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29615]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29616]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29617]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29618]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29619]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30486]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30487]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30588]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30589]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30590]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30591]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30592]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30593]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30594]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30595]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30596]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30751]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30752]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30753]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30754]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30755]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30756]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30757]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30758]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30759]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30760]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30762]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30763]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30764]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30765]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30766]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30767]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30772]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30777]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30778]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30779]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30780]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30781]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30782]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30783]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30784]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30785]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30786]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30787]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30788]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30793]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30794]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30795]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30796]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30797]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30798]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30799]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30800]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30801]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30802]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30803]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30804]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30805]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30806]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30807]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30809]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30810]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30814]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30815]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30818]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30823]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30824]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30825]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30826]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30827]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30829]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30830]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30831]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30832]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30833]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30834]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30835]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30836]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30837]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30838]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30839]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30840]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30845]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30846]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30847]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30848]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30849]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30850]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30851]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30852]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30853]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30854]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30855]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30856]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30857]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30858]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30860]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30859]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30862]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30864]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30861]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30865]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30867]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30863]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30869]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30866]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30871]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30868]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30873]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30870]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30875]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30872]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30877]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30874]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30879]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30876]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30881]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30878]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30880]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30882]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30884]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30883]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30886]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30885]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30888]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30887]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29584]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30889]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[29585]: WARNING: Failed to get value: 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. 
Feb  1 19:59:26 joe gdm-simple-slave[30488]: WARNING: Failed to get value: 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. 
Feb  1 19:59:31 joe gdm-simple-slave[31234]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display53319: 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. 
Feb  1 19:59:31 joe pulseaudio[31715]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:31 joe gdm-simple-slave[31237]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display53320: 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. 
Feb  1 19:59:33 joe pulseaudio[31762]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:33 joe acpid: client 28066[0:0] has disconnected
Feb  1 19:59:33 joe acpid: client 28070[0:0] has disconnected
Feb  1 19:59:33 joe acpid: client 28068[0:0] has disconnected
Feb  1 19:59:33 joe acpid: client 28065[0:0] has disconnected
Feb  1 19:59:33 joe acpid: client connected from 31739[0:0]
Feb  1 19:59:33 joe acpid: 1 client rule loaded
Feb  1 19:59:33 joe acpid: client connected from 31731[0:0]
Feb  1 19:59:33 joe acpid: 1 client rule loaded
Feb  1 19:59:33 joe acpid: client connected from 31736[0:0]
Feb  1 19:59:33 joe acpid: 1 client rule loaded
Feb  1 19:59:33 joe acpid: client connected from 31740[0:0]
Feb  1 19:59:33 joe acpid: 1 client rule loaded
Feb  1 19:59:33 joe acpid: client 31739[0:0] has disconnected
Feb  1 19:59:33 joe acpid: client 31731[0:0] has disconnected
Feb  1 19:59:33 joe acpid: client 31736[0:0] has disconnected
Feb  1 19:59:33 joe acpid: client 31740[0:0] has disconnected
Feb  1 19:59:33 joe acpid: client connected from 31734[0:0]
Feb  1 19:59:33 joe acpid: 1 client rule loaded
Feb  1 19:59:33 joe acpid: client 31734[0:0] has disconnected
Feb  1 19:59:33 joe acpid: client connected from 31735[0:0]
Feb  1 19:59:33 joe acpid: 1 client rule loaded
Feb  1 19:59:33 joe acpid: client 31735[0:0] has disconnected
Feb  1 19:59:33 joe acpid: client connected from 31749[0:0]
Feb  1 19:59:33 joe acpid: 1 client rule loaded
Feb  1 19:59:33 joe acpid: client 31749[0:0] has disconnected
Feb  1 19:59:33 joe acpid: client connected from 31746[0:0]
Feb  1 19:59:33 joe acpid: 1 client rule loaded
Feb  1 19:59:33 joe acpid: client 31746[0:0] has disconnected
Feb  1 19:59:34 joe acpid: client connected from 31744[0:0]
Feb  1 19:59:34 joe acpid: 1 client rule loaded
Feb  1 19:59:34 joe acpid: client 31744[0:0] has disconnected
Feb  1 19:59:34 joe acpid: client connected from 31747[0:0]
Feb  1 19:59:34 joe acpid: 1 client rule loaded
Feb  1 19:59:34 joe acpid: client 31747[0:0] has disconnected
Feb  1 19:59:34 joe acpid: client connected from 31745[0:0]
Feb  1 19:59:34 joe acpid: 1 client rule loaded
Feb  1 19:59:34 joe acpid: client 31745[0:0] has disconnected
Feb  1 19:59:34 joe acpid: client connected from 31743[0:0]
Feb  1 19:59:34 joe acpid: 1 client rule loaded
Feb  1 19:59:34 joe acpid: client 31743[0:0] has disconnected
Feb  1 19:59:34 joe acpid: client connected from 31742[0:0]
Feb  1 19:59:34 joe acpid: 1 client rule loaded
Feb  1 19:59:34 joe acpid: client 31742[0:0] has disconnected
Feb  1 19:59:34 joe acpid: client connected from 31727[0:0]
Feb  1 19:59:34 joe acpid: 1 client rule loaded
Feb  1 19:59:34 joe acpid: client 31727[0:0] has disconnected
Feb  1 19:59:34 joe acpid: client connected from 31732[0:0]
Feb  1 19:59:34 joe acpid: 1 client rule loaded
Feb  1 19:59:34 joe acpid: client 31732[0:0] has disconnected
Feb  1 19:59:34 joe acpid: client connected from 31729[0:0]
Feb  1 19:59:34 joe acpid: 1 client rule loaded
Feb  1 19:59:34 joe acpid: client 31729[0:0] has disconnected
Feb  1 19:59:34 joe acpid: client connected from 31733[0:0]
Feb  1 19:59:34 joe acpid: 1 client rule loaded
Feb  1 19:59:34 joe acpid: client 31733[0:0] has disconnected
Feb  1 19:59:34 joe acpid: client connected from 31728[0:0]
Feb  1 19:59:34 joe acpid: 1 client rule loaded
Feb  1 19:59:34 joe acpid: client 31728[0:0] has disconnected
Feb  1 19:59:34 joe acpid: client connected from 31738[0:0]
Feb  1 19:59:34 joe acpid: 1 client rule loaded
Feb  1 19:59:34 joe acpid: client 31738[0:0] has disconnected
Feb  1 19:59:34 joe acpid: client connected from 31730[0:0]
Feb  1 19:59:34 joe acpid: 1 client rule loaded
Feb  1 19:59:34 joe acpid: client 31730[0:0] has disconnected
Feb  1 19:59:34 joe acpid: client connected from 31726[0:0]
Feb  1 19:59:34 joe acpid: 1 client rule loaded
Feb  1 19:59:34 joe acpid: client 31726[0:0] has disconnected
Feb  1 19:59:34 joe acpid: client connected from 31725[0:0]
Feb  1 19:59:34 joe acpid: 1 client rule loaded
Feb  1 19:59:34 joe acpid: client 31725[0:0] has disconnected
Feb  1 19:59:34 joe acpid: client connected from 31741[0:0]
Feb  1 19:59:34 joe acpid: 1 client rule loaded
Feb  1 19:59:35 joe pulseaudio[31862]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:35 joe pulseaudio[31861]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:35 joe acpid: client 31741[0:0] has disconnected
Feb  1 19:59:35 joe acpid: client connected from 31737[0:0]
Feb  1 19:59:35 joe acpid: 1 client rule loaded
Feb  1 19:59:39 joe pulseaudio[31960]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:39 joe pulseaudio[31958]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:44 joe pulseaudio[32058]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:44 joe pulseaudio[32057]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:49 joe pulseaudio[32155]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:49 joe pulseaudio[32156]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:51 joe gdm-simple-slave[30824]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30826]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30825]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30827]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30829]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30830]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30831]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30832]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30833]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30839]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30834]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30840]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30835]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30845]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30836]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30846]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30847]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30837]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30848]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30838]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30849]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30850]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30851]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30852]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30853]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30854]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30855]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30862]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30856]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30857]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30864]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30858]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30865]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30859]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30866]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30860]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30873]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30867]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30861]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30868]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30875]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30869]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30863]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30870]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30877]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30871]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30878]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30872]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30879]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30880]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30874]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30881]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30882]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30876]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30883]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30884]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30885]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30886]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30887]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30888]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe gdm-simple-slave[30889]: WARNING: Failed to get value: 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. 
Feb  1 19:59:51 joe acpid: client 31737[0:0] has disconnected
Feb  1 19:59:51 joe acpid: client connected from 32207[0:0]
Feb  1 19:59:51 joe acpid: 1 client rule loaded
Feb  1 19:59:51 joe acpid: client connected from 32208[0:0]
Feb  1 19:59:51 joe acpid: 1 client rule loaded
Feb  1 19:59:53 joe gdm-simple-slave[30751]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30752]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30753]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30754]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30755]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30756]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30757]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30758]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30759]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30760]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30762]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30763]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30764]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30765]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30766]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30767]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30772]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30777]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30778]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30779]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30780]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30781]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30782]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30783]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30784]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30797]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30799]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30801]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30803]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30805]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30807]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30810]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30785]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30815]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30786]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30823]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30787]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30788]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30793]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30794]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30795]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30796]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30798]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30800]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30802]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30804]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30806]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30809]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30814]: WARNING: Failed to get value: 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. 
Feb  1 19:59:53 joe gdm-simple-slave[30818]: WARNING: Failed to get value: 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. 
Feb  1 19:59:54 joe gdm-simple-slave[32272]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 19:59:54 joe gdm-simple-slave[32264]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 19:59:54 joe pulseaudio[32471]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:54 joe pulseaudio[32475]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:59 joe pulseaudio[32573]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 19:59:59 joe pulseaudio[32574]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:04 joe pulseaudio[32675]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:04 joe pulseaudio[32676]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:09 joe pulseaudio[307]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:09 joe pulseaudio[308]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:14 joe pulseaudio[413]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:14 joe pulseaudio[415]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:19 joe pulseaudio[508]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:19 joe pulseaudio[509]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:24 joe pulseaudio[605]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:24 joe pulseaudio[607]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:29 joe pulseaudio[707]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:29 joe pulseaudio[708]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:34 joe pulseaudio[804]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:34 joe pulseaudio[806]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:39 joe pulseaudio[912]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:39 joe pulseaudio[914]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:40 joe gdm-simple-slave[32476]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32477]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32478]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32479]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32480]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32481]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32482]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32483]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32485]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32494]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32499]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32511]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32500]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32510]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32501]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32509]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32502]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32508]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32503]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32507]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32506]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32505]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32504]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32514]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32519]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32521]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32526]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32529]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32530]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32531]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32532]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32533]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32534]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32535]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32536]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32537]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32538]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32539]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32540]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32541]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32542]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32543]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32544]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32545]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32546]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32547]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32548]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32549]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32550]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32551]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32552]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32553]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32554]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32555]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32556]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32557]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32558]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32559]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32560]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32561]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32562]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32563]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32564]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32565]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32566]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32567]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32568]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32569]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32570]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32575]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32576]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32577]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32578]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32579]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32580]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32581]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32582]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32583]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32584]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32585]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32586]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32587]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32589]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32590]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32591]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32592]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32593]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32594]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32595]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32596]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32597]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32598]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32599]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32600]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32601]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32602]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32610]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32620]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32621]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32628]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32629]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32630]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32631]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32632]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32633]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32634]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32636]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32635]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32637]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32638]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32639]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31848]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31849]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31850]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31851]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31856]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31857]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31863]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31864]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31865]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31866]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31868]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31870]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31871]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31883]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31890]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31891]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31892]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31893]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31894]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31748]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31785]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31799]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31800]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31801]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31802]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31803]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31804]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31805]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31821]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31822]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31842]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31844]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31845]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31846]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[31847]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32214]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32215]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32216]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32225]: WARNING: Failed to get value: 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. 
Feb  1 20:00:40 joe gdm-simple-slave[32229]: WARNING: Failed to get value: 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. 
Feb  1 20:00:45 joe pulseaudio[1005]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:45 joe pulseaudio[1006]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:49 joe pulseaudio[1102]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:49 joe pulseaudio[1101]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:54 joe pulseaudio[1212]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:54 joe pulseaudio[1213]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:59 joe pulseaudio[1311]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:00:59 joe pulseaudio[1312]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:04 joe pulseaudio[1410]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:04 joe pulseaudio[1411]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:05 joe gdm-simple-slave[32636]: WARNING: Failed to get value: 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. 
Feb  1 20:01:05 joe gdm-simple-slave[32637]: WARNING: Failed to get value: 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. 
Feb  1 20:01:05 joe gdm-simple-slave[32638]: WARNING: Failed to get value: 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. 
Feb  1 20:01:05 joe gdm-simple-slave[32639]: WARNING: Failed to get value: 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. 
Feb  1 20:01:06 joe acpid: client 32207[0:0] has disconnected
Feb  1 20:01:06 joe acpid: client 32208[0:0] has disconnected
Feb  1 20:01:06 joe acpid: client connected from 1462[0:0]
Feb  1 20:01:06 joe acpid: 1 client rule loaded
Feb  1 20:01:06 joe acpid: client connected from 1479[0:0]
Feb  1 20:01:06 joe acpid: 1 client rule loaded
Feb  1 20:01:06 joe acpid: client connected from 1483[0:0]
Feb  1 20:01:06 joe acpid: 1 client rule loaded
Feb  1 20:01:06 joe acpid: client connected from 1472[0:0]
Feb  1 20:01:06 joe acpid: 1 client rule loaded
Feb  1 20:01:06 joe acpid: client connected from 1481[0:0]
Feb  1 20:01:06 joe acpid: 1 client rule loaded
Feb  1 20:01:06 joe acpid: client connected from 1465[0:0]
Feb  1 20:01:06 joe acpid: 1 client rule loaded
Feb  1 20:01:06 joe acpid: client connected from 1468[0:0]
Feb  1 20:01:06 joe acpid: 1 client rule loaded
Feb  1 20:01:06 joe acpid: client connected from 1469[0:0]
Feb  1 20:01:06 joe acpid: 1 client rule loaded
Feb  1 20:01:06 joe acpid: client connected from 1482[0:0]
Feb  1 20:01:06 joe acpid: 1 client rule loaded
Feb  1 20:01:06 joe acpid: client connected from 1471[0:0]
Feb  1 20:01:06 joe acpid: 1 client rule loaded
Feb  1 20:01:06 joe acpid: client connected from 1460[0:0]
Feb  1 20:01:06 joe acpid: 1 client rule loaded
Feb  1 20:01:06 joe acpid: client connected from 1485[0:0]
Feb  1 20:01:06 joe acpid: 1 client rule loaded
Feb  1 20:01:06 joe acpid: client connected from 1478[0:0]
Feb  1 20:01:06 joe acpid: 1 client rule loaded
Feb  1 20:01:06 joe acpid: client connected from 1464[0:0]
Feb  1 20:01:06 joe acpid: 1 client rule loaded
Feb  1 20:01:06 joe acpid: client connected from 1467[0:0]
Feb  1 20:01:06 joe acpid: 1 client rule loaded
Feb  1 20:01:06 joe acpid: client connected from 1477[0:0]
Feb  1 20:01:06 joe acpid: 1 client rule loaded
Feb  1 20:01:07 joe gdm-simple-slave[32476]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32477]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32478]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32479]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32480]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32481]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32482]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32483]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32485]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32494]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32499]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32500]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32501]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32502]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32503]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32504]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32505]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32506]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32507]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32521]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32526]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32529]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32530]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32531]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32532]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32533]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32534]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32535]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32536]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32537]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32544]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32545]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32546]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32547]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32548]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32549]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32550]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32551]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32552]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32553]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32554]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32541]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32559]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32560]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32561]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32562]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32563]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32564]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32565]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32566]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32567]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32568]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32558]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32542]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32555]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32556]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32543]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32570]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32575]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32576]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32577]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32578]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32579]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32580]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32540]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32584]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32585]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32581]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32557]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32587]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32589]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32590]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32591]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32592]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32593]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32586]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32594]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32569]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32511]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32514]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32621]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32628]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32629]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32595]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32596]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32597]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32598]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32599]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32600]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32601]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32602]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32610]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32620]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32539]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32538]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32583]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32582]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32519]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32630]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32631]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32632]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32633]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32634]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32635]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32510]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32508]: WARNING: Failed to get value: 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. 
Feb  1 20:01:07 joe gdm-simple-slave[32509]: WARNING: Failed to get value: 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. 
Feb  1 20:01:08 joe gdm-simple-slave[1734]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:01:08 joe gdm-simple-slave[1775]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:01:11 joe pulseaudio[1809]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:11 joe pulseaudio[1810]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:15 joe pulseaudio[1926]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:15 joe pulseaudio[1927]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:22 joe pulseaudio[2018]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:22 joe pulseaudio[2017]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:26 joe pulseaudio[2099]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:26 joe pulseaudio[2128]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:30 joe pulseaudio[2204]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:32 joe pulseaudio[2249]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:35 joe pulseaudio[2363]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:37 joe pulseaudio[2393]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:40 joe pulseaudio[2469]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:42 joe pulseaudio[2498]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:45 joe pulseaudio[2567]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:47 joe pulseaudio[2596]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:50 joe pulseaudio[2670]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:52 joe pulseaudio[2698]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:55 joe pulseaudio[2767]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:59 joe pulseaudio[2796]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:01:59 joe gdm-simple-slave[1820]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1836]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1835]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1837]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1838]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1839]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1840]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1841]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1842]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1843]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1844]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1846]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1845]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1847]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1859]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1848]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1858]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1849]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1857]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1856]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1855]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1853]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1850]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1860]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1862]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1864]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1861]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1866]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1863]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1868]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1865]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1869]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1867]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1870]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1883]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1881]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1880]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1871]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1872]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1873]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1885]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1879]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1886]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1878]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1887]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1877]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1876]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1875]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1874]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1884]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1922]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1906]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1888]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1889]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1890]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1892]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1891]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1898]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1897]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1896]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1894]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1893]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1923]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1928]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1929]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1930]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1931]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1932]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1933]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1934]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1935]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1936]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1937]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1938]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1939]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1940]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1941]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1942]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1943]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1944]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1945]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1947]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1946]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1948]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1949]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1964]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1963]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1950]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1962]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1951]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1961]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1960]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1952]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1959]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1953]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1958]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1954]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1957]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1955]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1956]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1965]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1967]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1966]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1526]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1968]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1969]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1528]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1529]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1533]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1532]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1531]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1530]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1534]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1536]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1540]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1793]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1789]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1550]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1548]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1547]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1546]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1545]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1544]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1543]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1542]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1541]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1539]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1538]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1537]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1819]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1818]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1817]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1816]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1815]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1814]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1813]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1812]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1811]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1806]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1805]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1804]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1803]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1802]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1801]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1800]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1798]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1797]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1535]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1796]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1795]: WARNING: Failed to get value: 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. 
Feb  1 20:01:59 joe gdm-simple-slave[1794]: WARNING: Failed to get value: 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. 
Feb  1 20:02:00 joe pulseaudio[2854]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:02 joe pulseaudio[2884]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:05 joe pulseaudio[2952]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:06 joe pulseaudio[2975]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:10 joe pulseaudio[3052]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:11 joe pulseaudio[3071]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:15 joe pulseaudio[3144]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:16 joe pulseaudio[3161]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:26 joe pulseaudio[3263]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:26 joe pulseaudio[3262]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:26 joe gdm-simple-slave[1836]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1841]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1840]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1839]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1820]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1838]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1835]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1837]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1843]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1842]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1859]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1845]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1858]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1844]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1857]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1846]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1856]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1847]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1855]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1853]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1849]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1848]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1860]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1862]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1850]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1864]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1861]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1866]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1863]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1865]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1867]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1883]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1868]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1881]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1869]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1871]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1880]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1872]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1870]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1873]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1878]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1877]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1876]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1875]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1886]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1885]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1889]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1874]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1890]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1884]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1891]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1922]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1906]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1892]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1898]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1897]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1933]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1931]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1935]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1937]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1896]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1894]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1939]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1893]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1941]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1923]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1928]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1929]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1943]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1940]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1945]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1930]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1949]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1932]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1950]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1934]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1951]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1938]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1942]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1944]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1947]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1946]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1948]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1964]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1963]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1952]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1962]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1961]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1960]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1955]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1888]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1966]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1959]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1968]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1958]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1957]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1956]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1965]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1967]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1969]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1887]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1879]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1953]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1954]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[1936]: WARNING: Failed to get value: 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. 
Feb  1 20:02:26 joe gdm-simple-slave[3315]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:02:26 joe gdm-simple-slave[3330]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:02:26 joe gdm-simple-slave[3326]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:02:28 joe pulseaudio[3483]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:28 joe pulseaudio[3485]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:28 joe acpid: client 1462[0:0] has disconnected
Feb  1 20:02:28 joe acpid: client 1479[0:0] has disconnected
Feb  1 20:02:28 joe acpid: client 1483[0:0] has disconnected
Feb  1 20:02:28 joe acpid: client 1472[0:0] has disconnected
Feb  1 20:02:28 joe acpid: client 1481[0:0] has disconnected
Feb  1 20:02:28 joe acpid: client 1465[0:0] has disconnected
Feb  1 20:02:28 joe acpid: client 1468[0:0] has disconnected
Feb  1 20:02:28 joe acpid: client 1469[0:0] has disconnected
Feb  1 20:02:28 joe acpid: client 1482[0:0] has disconnected
Feb  1 20:02:28 joe acpid: client 1471[0:0] has disconnected
Feb  1 20:02:28 joe acpid: client 1460[0:0] has disconnected
Feb  1 20:02:28 joe acpid: client 1485[0:0] has disconnected
Feb  1 20:02:28 joe acpid: client 1478[0:0] has disconnected
Feb  1 20:02:28 joe acpid: client 1464[0:0] has disconnected
Feb  1 20:02:28 joe acpid: client 1467[0:0] has disconnected
Feb  1 20:02:28 joe acpid: client 1477[0:0] has disconnected
Feb  1 20:02:33 joe pulseaudio[3600]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:33 joe pulseaudio[3599]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:38 joe pulseaudio[3720]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:38 joe pulseaudio[3718]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:43 joe pulseaudio[3828]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:43 joe pulseaudio[3829]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:48 joe pulseaudio[3927]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:48 joe pulseaudio[3929]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:53 joe pulseaudio[4214]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:53 joe pulseaudio[4215]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:59 joe pulseaudio[4304]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:02:59 joe pulseaudio[4305]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:04 joe pulseaudio[4389]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:04 joe pulseaudio[4392]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:08 joe pulseaudio[4479]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:08 joe pulseaudio[4480]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:13 joe pulseaudio[4572]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:13 joe pulseaudio[4574]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:18 joe pulseaudio[4664]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:18 joe pulseaudio[4665]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:23 joe pulseaudio[4762]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:23 joe pulseaudio[4763]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:28 joe pulseaudio[4858]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:28 joe pulseaudio[4859]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:33 joe pulseaudio[4955]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:33 joe pulseaudio[4956]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:38 joe pulseaudio[5048]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:38 joe pulseaudio[5050]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:39 joe gdm-simple-slave[3480]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3484]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3487]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3488]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3489]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3490]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3491]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3492]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3493]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3494]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3495]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3496]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3501]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3500]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3502]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3499]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3498]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3503]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3497]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3504]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3505]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3506]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3507]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3508]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3509]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3510]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3517]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3518]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3519]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4149]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4150]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4151]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4152]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4153]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4155]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4161]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4162]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4163]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4164]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4165]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4166]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4167]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4168]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4169]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4170]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4171]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4172]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4180]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4183]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4191]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4193]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4194]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4195]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4196]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4198]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4210]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4211]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4216]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4223]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4224]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4225]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4226]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4227]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4228]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4229]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4221]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4220]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4218]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4217]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4219]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4230]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4231]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4232]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4233]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4234]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4235]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4236]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4237]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4238]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4239]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4240]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4241]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4243]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4249]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4250]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4251]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4252]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4253]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4254]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4255]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4256]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4257]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4258]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4259]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4263]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4262]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4264]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4248]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4261]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4246]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4260]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4245]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4244]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4247]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4265]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4266]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4267]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4268]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4269]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4270]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4271]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4272]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4273]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[4274]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3291]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3384]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3386]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3388]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3389]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3390]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3391]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3392]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3385]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3454]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3455]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3456]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3457]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3458]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3459]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3460]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3461]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3462]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3463]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3472]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3471]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3473]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3469]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3467]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3470]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3466]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3474]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3468]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3464]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3465]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3478]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3475]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3477]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3476]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3448]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3394]: WARNING: Failed to get value: 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. 
Feb  1 20:03:39 joe gdm-simple-slave[3393]: WARNING: Failed to get value: 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. 
Feb  1 20:03:44 joe acpid: client connected from 5150[0:0]
Feb  1 20:03:44 joe acpid: 1 client rule loaded
Feb  1 20:03:44 joe acpid: client connected from 5159[0:0]
Feb  1 20:03:44 joe acpid: 1 client rule loaded
Feb  1 20:03:44 joe acpid: client connected from 5157[0:0]
Feb  1 20:03:44 joe acpid: 1 client rule loaded
Feb  1 20:03:44 joe acpid: client connected from 5151[0:0]
Feb  1 20:03:44 joe acpid: 1 client rule loaded
Feb  1 20:03:44 joe acpid: client connected from 5149[0:0]
Feb  1 20:03:44 joe acpid: 1 client rule loaded
Feb  1 20:03:44 joe pulseaudio[5227]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:44 joe pulseaudio[5228]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:44 joe acpid: client 5150[0:0] has disconnected
Feb  1 20:03:44 joe acpid: client 5159[0:0] has disconnected
Feb  1 20:03:44 joe acpid: client 5157[0:0] has disconnected
Feb  1 20:03:44 joe acpid: client 5151[0:0] has disconnected
Feb  1 20:03:44 joe acpid: client 5149[0:0] has disconnected
Feb  1 20:03:44 joe acpid: client connected from 5152[0:0]
Feb  1 20:03:44 joe acpid: 1 client rule loaded
Feb  1 20:03:44 joe acpid: client 5152[0:0] has disconnected
Feb  1 20:03:44 joe acpid: client connected from 5153[0:0]
Feb  1 20:03:44 joe acpid: 1 client rule loaded
Feb  1 20:03:44 joe acpid: client 5153[0:0] has disconnected
Feb  1 20:03:44 joe acpid: client connected from 5156[0:0]
Feb  1 20:03:44 joe acpid: 1 client rule loaded
Feb  1 20:03:44 joe acpid: client 5156[0:0] has disconnected
Feb  1 20:03:44 joe acpid: client connected from 5155[0:0]
Feb  1 20:03:44 joe acpid: 1 client rule loaded
Feb  1 20:03:44 joe acpid: client 5155[0:0] has disconnected
Feb  1 20:03:44 joe acpid: client connected from 5158[0:0]
Feb  1 20:03:44 joe acpid: 1 client rule loaded
Feb  1 20:03:44 joe acpid: client 5158[0:0] has disconnected
Feb  1 20:03:44 joe acpid: client connected from 5154[0:0]
Feb  1 20:03:44 joe acpid: 1 client rule loaded
Feb  1 20:03:45 joe acpid: client 5154[0:0] has disconnected
Feb  1 20:03:49 joe pulseaudio[5345]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:49 joe pulseaudio[5344]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:54 joe pulseaudio[5439]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:54 joe pulseaudio[5438]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:59 joe pulseaudio[5533]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:03:59 joe pulseaudio[5535]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:04 joe gdm-simple-slave[4272]: WARNING: Failed to get value: 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. 
Feb  1 20:04:04 joe gdm-simple-slave[4273]: WARNING: Failed to get value: 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. 
Feb  1 20:04:04 joe gdm-simple-slave[4274]: WARNING: Failed to get value: 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. 
Feb  1 20:04:04 joe gdm-simple-slave[5624]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:04:04 joe gdm-simple-slave[5630]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:04:04 joe pulseaudio[5655]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:04 joe pulseaudio[5656]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:09 joe pulseaudio[5746]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:09 joe pulseaudio[5748]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:14 joe pulseaudio[5841]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:14 joe pulseaudio[5842]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:19 joe pulseaudio[5937]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:19 joe pulseaudio[5936]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:24 joe pulseaudio[6033]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:24 joe pulseaudio[6034]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:29 joe pulseaudio[6128]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:29 joe pulseaudio[6127]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:30 joe gdm-simple-slave[4163]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4164]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4165]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4166]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4167]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4168]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4169]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4170]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4171]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4172]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4180]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4183]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4191]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4193]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4194]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4195]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4220]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4217]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4221]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4223]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4218]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4219]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4210]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4211]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4198]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4196]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4216]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4228]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4229]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4230]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4231]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4232]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4233]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4234]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4235]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4236]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4237]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4238]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4245]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4249]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4247]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4243]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4265]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4266]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4267]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4268]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4269]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4270]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4271]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4255]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4256]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4254]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4257]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4252]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4259]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4261]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4258]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4253]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4251]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4260]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4263]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4262]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4264]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4225]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4226]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4227]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4224]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5175]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5199]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5200]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5201]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5202]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5203]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5204]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5205]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5206]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5207]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5208]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5209]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5211]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4248]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4250]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4246]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4244]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4240]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4239]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4241]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5212]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5213]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5214]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5216]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5217]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5218]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5219]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5220]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5221]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5222]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5223]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5224]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5229]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5230]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5231]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5232]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5233]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5234]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5235]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5236]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5237]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5238]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5239]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5240]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5241]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5242]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5243]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5244]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5245]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5246]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5247]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5248]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5249]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5250]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5251]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5252]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5253]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5254]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5255]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5273]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5649]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5650]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5651]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5652]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5657]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5658]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5659]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5660]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5661]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5662]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5663]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5664]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4149]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4150]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4151]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4152]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4153]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4155]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4161]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[4162]: WARNING: Failed to get value: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5670]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display55954: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5677]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display55955: 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. 
Feb  1 20:04:30 joe gdm-simple-slave[5678]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display55956: 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. 
Feb  1 20:04:31 joe gdm-simple-slave[5693]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display55959: 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. 
Feb  1 20:04:36 joe acpid: client connected from 6189[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6207[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6191[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6204[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe pulseaudio[6368]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:36 joe pulseaudio[6369]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:36 joe acpid: client 6189[0:0] has disconnected
Feb  1 20:04:36 joe acpid: client 6207[0:0] has disconnected
Feb  1 20:04:36 joe acpid: client 6191[0:0] has disconnected
Feb  1 20:04:36 joe acpid: client 6204[0:0] has disconnected
Feb  1 20:04:36 joe acpid: client connected from 6197[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client 6197[0:0] has disconnected
Feb  1 20:04:36 joe acpid: client connected from 6199[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client 6199[0:0] has disconnected
Feb  1 20:04:36 joe acpid: client connected from 6218[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client 6218[0:0] has disconnected
Feb  1 20:04:36 joe acpid: client connected from 6213[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client 6213[0:0] has disconnected
Feb  1 20:04:36 joe acpid: client connected from 6209[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client 6209[0:0] has disconnected
Feb  1 20:04:36 joe acpid: client connected from 6206[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client 6206[0:0] has disconnected
Feb  1 20:04:36 joe acpid: client connected from 6190[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client 6190[0:0] has disconnected
Feb  1 20:04:36 joe acpid: client connected from 6210[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client 6210[0:0] has disconnected
Feb  1 20:04:36 joe acpid: client connected from 6208[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client 6208[0:0] has disconnected
Feb  1 20:04:36 joe acpid: client connected from 6192[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client 6192[0:0] has disconnected
Feb  1 20:04:36 joe acpid: client connected from 6200[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client 6200[0:0] has disconnected
Feb  1 20:04:36 joe acpid: client connected from 6211[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6212[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6205[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6195[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6196[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6216[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6202[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6217[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6219[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6221[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6271[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6223[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6220[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6215[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6269[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6230[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6267[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6268[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6198[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6225[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6203[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6193[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6224[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6226[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6227[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6231[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6233[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6228[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6232[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6222[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6243[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6239[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6236[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6241[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6244[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6229[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6214[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6242[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6238[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6246[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6250[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6251[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6249[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6252[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6253[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6255[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:36 joe acpid: client connected from 6247[0:0]
Feb  1 20:04:36 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client connected from 6256[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client 6205[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client 6196[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client 6216[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client connected from 6257[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client 6214[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client connected from 6260[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client 6267[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client connected from 6259[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client 6203[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client 6232[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client connected from 6263[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client 6243[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client connected from 6258[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client connected from 6261[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client 6271[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client connected from 6234[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client 6223[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client 6228[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client 6236[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client 6229[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client connected from 6245[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client 6202[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client 6268[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client 6227[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client connected from 6266[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client connected from 6254[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client connected from 6248[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client 6248[0:0] has disconnected
Feb  1 20:04:37 joe acpid: client connected from 6264[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client connected from 6262[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client connected from 6265[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client connected from 6273[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client connected from 6270[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client connected from 6240[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client connected from 6272[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:37 joe acpid: client connected from 6237[0:0]
Feb  1 20:04:37 joe acpid: 1 client rule loaded
Feb  1 20:04:41 joe acpid: client 6211[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6212[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6195[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6217[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6219[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6221[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6220[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6215[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6269[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6230[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6198[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6225[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6193[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6224[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6226[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6231[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6233[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6222[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6239[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6241[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6244[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6242[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6238[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6246[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6250[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6251[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6249[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6252[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6253[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6255[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6247[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6256[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6257[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6260[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6259[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6263[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6258[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6261[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6234[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6245[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6266[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6254[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6264[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6262[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6265[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6273[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6270[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6240[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6272[0:0] has disconnected
Feb  1 20:04:41 joe acpid: client 6237[0:0] has disconnected
Feb  1 20:04:41 joe pulseaudio[6472]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:41 joe pulseaudio[6473]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:46 joe pulseaudio[6562]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:46 joe pulseaudio[6563]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:51 joe pulseaudio[6657]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:51 joe pulseaudio[6658]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:55 joe gdm-simple-slave[5201]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5202]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5203]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5204]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5205]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5206]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5207]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5208]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5209]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5211]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5212]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5213]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5214]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5216]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5218]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5217]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5220]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5221]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5219]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5222]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5223]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5224]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5229]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5230]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5231]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5234]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5235]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5236]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5237]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5238]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5232]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5241]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5242]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5243]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5244]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5245]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5246]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5247]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5248]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5249]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5250]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5652]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5659]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5253]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5651]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5252]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5273]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5251]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5658]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5254]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5657]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5255]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5660]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5664]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5661]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5662]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5650]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5649]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5233]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5239]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5240]: WARNING: Failed to get value: 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. 
Feb  1 20:04:55 joe gdm-simple-slave[5663]: WARNING: Failed to get value: 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. 
Feb  1 20:04:56 joe pulseaudio[6762]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:04:56 joe pulseaudio[6761]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:01 joe pulseaudio[6979]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:01 joe pulseaudio[6978]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:06 joe pulseaudio[7071]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:06 joe pulseaudio[7070]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:11 joe pulseaudio[7166]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:11 joe pulseaudio[7165]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:16 joe pulseaudio[7258]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:16 joe pulseaudio[7260]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:21 joe pulseaudio[7352]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:21 joe pulseaudio[7353]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:26 joe pulseaudio[7442]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:26 joe pulseaudio[7443]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:31 joe pulseaudio[7539]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:31 joe pulseaudio[7538]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:36 joe pulseaudio[7632]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:36 joe pulseaudio[7633]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:41 joe pulseaudio[7729]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:41 joe pulseaudio[7727]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:46 joe pulseaudio[7822]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:46 joe pulseaudio[7820]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:47 joe gdm-simple-slave[6455]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6457]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6456]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6458]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6459]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6460]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6461]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6462]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6463]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6464]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6465]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6466]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6467]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6468]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6469]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6474]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6475]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6476]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6477]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6478]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6479]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6480]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6481]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6482]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6483]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[5175]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[5199]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[5200]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6235]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6355]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6356]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6357]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6358]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6359]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6360]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6361]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6362]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6363]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6364]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6365]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6370]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6371]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6372]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6404]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6405]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6406]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6416]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6418]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6424]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6425]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6426]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6427]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6428]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6429]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6430]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6431]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6432]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6433]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6434]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6435]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6436]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6437]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6438]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6439]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6440]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6441]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6442]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6443]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6484]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6485]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6486]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6487]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6488]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6489]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6490]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6741]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6748]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6749]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6755]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6901]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6902]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6903]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6904]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6905]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6906]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6907]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6908]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6909]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6913]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6927]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6928]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6929]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6930]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6931]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6932]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6933]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6934]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6941]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6942]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6943]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6944]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6945]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6946]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6947]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6948]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6952]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6953]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6954]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6955]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6956]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6957]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6958]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6959]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6960]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6961]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6962]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6963]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6964]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6966]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6967]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6968]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6969]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6970]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6971]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6972]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6973]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6974]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6975]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6980]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6981]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6982]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6984]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6985]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6986]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6987]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6988]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6989]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6990]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6991]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6992]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6993]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6445]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6447]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6448]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6449]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6450]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6452]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6453]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6454]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6444]: WARNING: Failed to get value: 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. 
Feb  1 20:05:47 joe gdm-simple-slave[6446]: WARNING: Failed to get value: 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. 
Feb  1 20:05:49 joe gdm-simple-slave[7879]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:05:50 joe acpid: client connected from 7915[0:0]
Feb  1 20:05:50 joe acpid: 1 client rule loaded
Feb  1 20:05:50 joe acpid: client connected from 7913[0:0]
Feb  1 20:05:50 joe acpid: 1 client rule loaded
Feb  1 20:05:50 joe acpid: client connected from 7912[0:0]
Feb  1 20:05:50 joe acpid: 1 client rule loaded
Feb  1 20:05:52 joe acpid: client 7915[0:0] has disconnected
Feb  1 20:05:52 joe acpid: client 7913[0:0] has disconnected
Feb  1 20:05:52 joe acpid: client 7912[0:0] has disconnected
Feb  1 20:05:52 joe pulseaudio[8057]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:52 joe pulseaudio[8056]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:57 joe pulseaudio[8155]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:05:57 joe pulseaudio[8156]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:03 joe pulseaudio[8249]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:03 joe pulseaudio[8250]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:08 joe pulseaudio[8341]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:08 joe pulseaudio[8343]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:14 joe gdm-simple-slave[6901]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6902]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6903]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6904]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6905]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6906]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6907]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6908]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6909]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6913]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6927]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6929]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6928]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6931]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6933]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6930]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6941]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6932]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6943]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6934]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6945]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6942]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6944]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6946]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6947]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6948]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6953]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6955]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6957]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6959]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6960]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6961]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6962]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6963]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6964]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6966]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6967]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6968]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6969]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6970]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6971]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6972]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6973]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6974]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6975]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6980]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6981]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6952]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6982]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6984]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6954]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6985]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6956]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6986]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6958]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6989]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6991]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe pulseaudio[8465]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:14 joe gdm-simple-slave[6993]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6987]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6988]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6990]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe gdm-simple-slave[6992]: WARNING: Failed to get value: 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. 
Feb  1 20:06:14 joe pulseaudio[8464]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:19 joe pulseaudio[8582]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:19 joe pulseaudio[8583]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:20 joe gdm-simple-slave[8123]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display56902: 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. 
Feb  1 20:06:20 joe gdm-simple-slave[8124]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display56903: 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. 
Feb  1 20:06:24 joe pulseaudio[8676]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:24 joe pulseaudio[8677]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:29 joe pulseaudio[8762]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:29 joe pulseaudio[8763]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:34 joe pulseaudio[8847]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:34 joe pulseaudio[8846]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:37 joe gdm-simple-slave[8431]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57031: 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. 
Feb  1 20:06:37 joe gdm-simple-slave[8467]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57032: 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. 
Feb  1 20:06:37 joe gdm-simple-slave[8468]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57033: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8469]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57034: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8470]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57035: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8471]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57036: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8472]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57037: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8473]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57038: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8474]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57039: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8475]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57040: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8476]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57041: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8477]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57042: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8478]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57043: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8479]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57044: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8480]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57045: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8026]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8030]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8032]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8034]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8036]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8039]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8028]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8027]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8029]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8031]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8033]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8035]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8037]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8038]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8040]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8041]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8044]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8042]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8058]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8066]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8073]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8075]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8077]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8065]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8092]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8067]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8094]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8068]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8071]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8074]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8076]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8078]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8079]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8080]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8081]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8082]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8083]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8084]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8085]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8086]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8087]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8088]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8089]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8090]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8091]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8096]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8100]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8098]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8093]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8095]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8099]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8101]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8102]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8103]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8104]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8105]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8106]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8107]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8108]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8109]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8110]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8111]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8112]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8113]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8114]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8115]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8116]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8117]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8118]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8120]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8121]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:39 joe gdm-simple-slave[8122]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:06:42 joe pulseaudio[9074]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:42 joe pulseaudio[9075]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:47 joe pulseaudio[9201]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:47 joe pulseaudio[9202]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:52 joe pulseaudio[9295]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:52 joe pulseaudio[9294]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:57 joe pulseaudio[9389]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:06:57 joe pulseaudio[9390]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:02 joe pulseaudio[9483]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:02 joe pulseaudio[9484]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:07 joe pulseaudio[9577]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:07 joe pulseaudio[9576]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:12 joe gdm-simple-slave[8897]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8909]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8911]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8916]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8933]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8930]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8944]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8947]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8957]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8954]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8963]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8026]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9068]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8035]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8027]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8034]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8033]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8028]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8032]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8029]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8036]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8030]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8031]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8037]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8038]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8058]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8044]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8039]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8041]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8040]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8071]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8042]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8068]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8065]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8073]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8066]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8067]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8075]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8078]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8077]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8074]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8080]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8076]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8098]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8079]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8096]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8081]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8095]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8082]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8083]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8084]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8093]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8092]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8094]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8091]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8085]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8090]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8086]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8089]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8087]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8100]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8088]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8099]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8101]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8115]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8102]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8103]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8104]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8105]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8106]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8116]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9083]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9082]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9081]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9080]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9079]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9078]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9076]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9069]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8122]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8121]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8120]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8118]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8117]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9085]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9095]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9090]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9088]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9096]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9098]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9099]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9104]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9106]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9107]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9108]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9110]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9114]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9121]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9122]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9123]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9124]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9125]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9126]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9127]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9128]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8114]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9163]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57268: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8113]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8112]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8111]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8107]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8110]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8109]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9164]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57269: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[8108]: WARNING: Failed to get value: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9067]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9165]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57270: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9166]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57271: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9167]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57272: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9168]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57273: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9169]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57274: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9171]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57275: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9172]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57276: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9173]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57277: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9174]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57278: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9175]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57279: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9176]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57280: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9177]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57281: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9178]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57282: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9179]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57283: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9180]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57284: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9181]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57285: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9182]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57286: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9183]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57287: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9184]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57288: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9185]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57289: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9186]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57290: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9187]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57291: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9188]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57292: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9189]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57293: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9190]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57294: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9191]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57295: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9192]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57296: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9193]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57297: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9194]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57298: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9195]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57299: 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. 
Feb  1 20:07:12 joe gdm-simple-slave[9197]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57300: 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. 
Feb  1 20:07:12 joe pulseaudio[9664]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:12 joe gdm-simple-slave[9198]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57301: 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. 
Feb  1 20:07:12 joe pulseaudio[9665]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:12 joe gdm-simple-slave[9685]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:07:17 joe pulseaudio[9819]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:17 joe pulseaudio[9821]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:22 joe pulseaudio[9913]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:22 joe pulseaudio[9914]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:27 joe pulseaudio[10005]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:27 joe pulseaudio[10006]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:32 joe pulseaudio[10098]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:32 joe pulseaudio[10099]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:37 joe gdm-simple-slave[9080]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9081]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9082]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9069]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9083]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9076]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9078]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9079]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9095]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9096]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9098]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9121]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9108]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9107]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9085]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9090]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9114]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9110]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9104]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9088]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9106]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9099]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9122]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9123]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9128]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9124]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9126]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9125]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9127]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[9067]: WARNING: Failed to get value: 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. 
Feb  1 20:07:37 joe gdm-simple-slave[10235]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:07:37 joe gdm-simple-slave[10249]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:07:37 joe gdm-simple-slave[10219]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:07:37 joe pulseaudio[10330]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:38 joe pulseaudio[10329]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:38 joe gdm-simple-slave[8933]: WARNING: Failed to get value: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[8930]: WARNING: Failed to get value: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[8957]: WARNING: Failed to get value: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[8954]: WARNING: Failed to get value: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[8963]: WARNING: Failed to get value: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9068]: WARNING: Failed to get value: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9671]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57503: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9736]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57507: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9737]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57508: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9738]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57509: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9734]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57505: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9205]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9735]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57506: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[8916]: WARNING: Failed to get value: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[8911]: WARNING: Failed to get value: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[8944]: WARNING: Failed to get value: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[8909]: WARNING: Failed to get value: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9203]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9739]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57510: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[8897]: WARNING: Failed to get value: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9204]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9733]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57504: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9740]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57511: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[8947]: WARNING: Failed to get value: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9741]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57512: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9742]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57513: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9743]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57514: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9744]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57515: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9745]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57516: 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. 
Feb  1 20:07:38 joe gdm-simple-slave[9747]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57517: 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. 
Feb  1 20:07:39 joe gdm-simple-slave[9748]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57518: 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. 
Feb  1 20:07:39 joe gdm-simple-slave[9750]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57519: 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. 
Feb  1 20:07:39 joe gdm-simple-slave[9751]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57520: 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. 
Feb  1 20:07:39 joe gdm-simple-slave[9752]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57521: 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. 
Feb  1 20:07:39 joe gdm-simple-slave[9753]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57522: 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. 
Feb  1 20:07:39 joe gdm-simple-slave[9754]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57523: 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. 
Feb  1 20:07:39 joe gdm-simple-slave[9755]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57524: 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. 
Feb  1 20:07:39 joe gdm-simple-slave[9756]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57525: 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. 
Feb  1 20:07:39 joe gdm-simple-slave[9757]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57526: 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. 
Feb  1 20:07:39 joe gdm-simple-slave[9775]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57527: 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. 
Feb  1 20:07:40 joe gdm-simple-slave[10406]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:07:42 joe pulseaudio[10542]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:42 joe pulseaudio[10541]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:47 joe pulseaudio[10637]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:47 joe pulseaudio[10636]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:52 joe pulseaudio[10728]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:52 joe pulseaudio[10727]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:57 joe pulseaudio[10822]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:07:57 joe pulseaudio[10824]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:02 joe pulseaudio[10916]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:02 joe pulseaudio[10917]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:04 joe gdm-simple-slave[9781]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:04 joe gdm-simple-slave[9783]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:04 joe gdm-simple-slave[9784]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:04 joe gdm-simple-slave[9785]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[9786]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[9787]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[9788]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[9789]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10182]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[9205]: WARNING: Failed to get value: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[9203]: WARNING: Failed to get value: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[9204]: WARNING: Failed to get value: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10325]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10335]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10337]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10336]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10334]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10338]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10339]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10340]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10341]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10344]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10343]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10342]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10345]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10347]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10348]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10349]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10485]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57722: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10489]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57723: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10494]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57724: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10495]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57725: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10505]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57726: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10512]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57727: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10513]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57728: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10514]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57729: 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. 
Feb  1 20:08:05 joe gdm-simple-slave[10515]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57730: 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. 
Feb  1 20:08:06 joe gdm-simple-slave[10516]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57731: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10517]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57732: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10518]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57733: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10519]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57734: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10520]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57735: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10521]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57736: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10523]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57737: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10524]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57738: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10525]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57739: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10526]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57740: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10527]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57741: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10529]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57743: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10531]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57745: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10532]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57746: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10528]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57742: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10530]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57744: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10535]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57747: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10536]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57748: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10538]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57750: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10537]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57749: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10543]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57751: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10544]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57752: 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. 
Feb  1 20:08:08 joe pulseaudio[11007]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:08 joe gdm-simple-slave[10547]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57755: 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. 
Feb  1 20:08:08 joe pulseaudio[11009]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:08 joe gdm-simple-slave[10545]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57753: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10546]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57754: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[10548]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57756: 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. 
Feb  1 20:08:08 joe gdm-simple-slave[11036]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:08:13 joe pulseaudio[11150]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:13 joe pulseaudio[11149]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:18 joe pulseaudio[11241]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:18 joe pulseaudio[11242]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:23 joe pulseaudio[11334]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:23 joe pulseaudio[11335]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:28 joe pulseaudio[11425]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:28 joe pulseaudio[11427]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:33 joe gdm-simple-slave[10578]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10577]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10580]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10579]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10582]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10581]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10584]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10583]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10601]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10608]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10609]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10611]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10610]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10613]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10612]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10614]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10615]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10616]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10617]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10618]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10619]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10621]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10622]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10623]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10624]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10625]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10626]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10627]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10628]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10629]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10630]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10631]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10633]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10632]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10638]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10640]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10642]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10658]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10656]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10655]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10654]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10653]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10652]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10651]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10650]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10649]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10339]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10338]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10337]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10336]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10335]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10334]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10325]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10182]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[9789]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[9788]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[9787]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10644]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[9783]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10645]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[9784]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10646]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[9786]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10647]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[9785]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10643]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10648]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10641]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10659]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10660]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10661]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10662]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10663]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10664]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[9781]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10341]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10340]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10639]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10342]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10343]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10344]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10345]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10347]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10348]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10349]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10549]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10551]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10550]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10553]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10552]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10554]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10556]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10557]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10558]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10560]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10555]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10559]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10561]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10563]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10562]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10564]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10565]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10566]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10567]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10568]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10576]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10569]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10575]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10570]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10574]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10573]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10572]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[10571]: WARNING: Failed to get value: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[11054]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57990: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[11055]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57991: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[11056]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57992: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[11057]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57993: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[11058]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57994: 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. 
Feb  1 20:08:33 joe pulseaudio[11535]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:33 joe pulseaudio[11536]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:33 joe gdm-simple-slave[11061]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57995: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[11062]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57996: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[11063]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57997: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[11064]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57998: 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. 
Feb  1 20:08:33 joe gdm-simple-slave[11065]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display57999: 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. 
Feb  1 20:08:39 joe pulseaudio[11668]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:39 joe pulseaudio[11667]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:43 joe pulseaudio[11757]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:43 joe pulseaudio[11756]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:50 joe pulseaudio[11853]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:50 joe pulseaudio[11854]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:56 joe pulseaudio[11934]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:56 joe pulseaudio[11933]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:58 joe gdm-simple-slave[10661]: WARNING: Failed to get value: 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. 
Feb  1 20:08:58 joe gdm-simple-slave[10662]: WARNING: Failed to get value: 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. 
Feb  1 20:08:58 joe gdm-simple-slave[10663]: WARNING: Failed to get value: 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. 
Feb  1 20:08:58 joe gdm-simple-slave[10664]: WARNING: Failed to get value: 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. 
Feb  1 20:08:58 joe gdm-simple-slave[10639]: WARNING: Failed to get value: 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. 
Feb  1 20:08:58 joe gdm-simple-slave[11510]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58195: 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. 
Feb  1 20:08:58 joe gdm-simple-slave[11529]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58197: 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. 
Feb  1 20:08:58 joe pulseaudio[12083]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:08:58 joe gdm-simple-slave[11532]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58198: 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. 
Feb  1 20:08:58 joe gdm-simple-slave[11555]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58199: 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. 
Feb  1 20:08:58 joe gdm-simple-slave[11556]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58200: 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. 
Feb  1 20:08:58 joe gdm-simple-slave[11557]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58201: 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. 
Feb  1 20:08:58 joe gdm-simple-slave[11558]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58202: 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. 
Feb  1 20:08:59 joe gdm-simple-slave[11559]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58203: 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. 
Feb  1 20:08:59 joe gdm-simple-slave[11560]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58204: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11561]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58205: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11562]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58206: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11563]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58207: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11564]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58208: 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. 
Feb  1 20:09:02 joe pulseaudio[12133]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:09:02 joe gdm-simple-slave[11084]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11085]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11086]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10577]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11087]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11088]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11094]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11089]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11093]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11090]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11091]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10579]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10580]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10581]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10582]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10583]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10616]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10584]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10615]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10601]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10614]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11092]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10613]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10578]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10618]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10608]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10617]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10612]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10609]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10610]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10611]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10649]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10619]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10642]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10621]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10622]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10640]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10623]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10638]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10633]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10624]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10632]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10625]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10631]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10626]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10630]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10627]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10628]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10629]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10658]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10651]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10655]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10650]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10653]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10656]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10652]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10654]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10641]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10643]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10644]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10645]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10646]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10647]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10648]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10659]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[10660]: WARNING: Failed to get value: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11573]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58209: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11598]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58210: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11599]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58211: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11600]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58212: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11601]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58213: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11602]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58214: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11603]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58215: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11604]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58216: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11605]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58217: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11606]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58218: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11607]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58219: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11608]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58220: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11609]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58221: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11610]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58222: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11611]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58223: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11613]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58225: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11616]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58228: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11614]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58226: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11615]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58227: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[11612]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58224: 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. 
Feb  1 20:09:02 joe gdm-simple-slave[12169]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:09:03 joe pulseaudio[12213]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:09:03 joe /USR/SBIN/CRON[12215]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \; -delete)
Feb  1 20:09:06 joe pulseaudio[12251]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:09:08 joe pulseaudio[12316]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:09:13 joe pulseaudio[12343]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:09:13 joe pulseaudio[12404]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:09:16 joe pulseaudio[12431]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:09:18 joe pulseaudio[12492]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:09:22 joe pulseaudio[12522]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:09:22 joe gnome-session[26373]: WARNING: Unable to load desktop file '/usr/bin/hp-systray.desktop': Datei oder Verzeichnis nicht gefunden 
Feb  1 20:09:22 joe gnome-session[26373]: WARNING: Unable to find desktop file 'hp-systray.desktop': Es wurde keine gültige Schlüsselwertedatei in den Suchordnern gefunden 
Feb  1 20:09:22 joe gnome-session[26373]: WARNING: Unable to find desktop file 'gnome-/usr/bin/hp-systray.desktop': Es wurde keine gültige Schlüsselwertedatei in den Suchordnern gefunden 
Feb  1 20:09:23 joe pulseaudio[12562]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:09:31 joe gdm-simple-slave[12202]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58442: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12201]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58441: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[11091]: WARNING: Failed to get value: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[11090]: WARNING: Failed to get value: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[11093]: WARNING: Failed to get value: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12199]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58440: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[11092]: WARNING: Failed to get value: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12206]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58446: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12198]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58439: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12204]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58444: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12195]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58436: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12205]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58445: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12203]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58443: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12140]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[11094]: WARNING: Failed to get value: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12197]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58438: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12193]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58434: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[11089]: WARNING: Failed to get value: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12191]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58432: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12196]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58437: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12152]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12194]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58435: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[11085]: WARNING: Failed to get value: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[11088]: WARNING: Failed to get value: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[11087]: WARNING: Failed to get value: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12151]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12146]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12192]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58433: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12139]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12138]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12153]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12149]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12147]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12135]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12141]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12137]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12144]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12143]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[11084]: WARNING: Failed to get value: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12136]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12145]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12130]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[11086]: WARNING: Failed to get value: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12134]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12128]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12131]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12117]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12129]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12089]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12092]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12087]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12122]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12078]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12073]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12070]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12103]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12096]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12207]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58447: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12208]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58448: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12645]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:09:31 joe gdm-simple-slave[12209]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58449: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12210]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58450: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12211]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58451: 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. 
Feb  1 20:09:31 joe pulseaudio[12723]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:09:31 joe gdm-simple-slave[12214]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58452: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12216]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58453: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12217]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58454: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12218]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58455: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12219]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58456: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12220]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58457: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12221]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58458: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12225]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58459: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12239]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58460: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12244]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58461: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12249]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58462: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12252]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58463: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12253]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58464: 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. 
Feb  1 20:09:31 joe gdm-simple-slave[12254]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58465: 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. 
Feb  1 20:09:34 joe pulseaudio[3668]: [pulseaudio] module-console-kit.c: GetUnixUser() call failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetUnixUser" with signature "" on interface "org.freedesktop.ConsoleKit.Session" doesn't exist
Feb  1 20:09:34 joe NetworkManager[2210]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.9715': no such name
Feb  1 20:09:34 joe NetworkManager[2210]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.9715': no such name
Feb  1 20:09:34 joe NetworkManager[2210]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-network: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.9763': no such name
Feb  1 20:09:34 joe NetworkManager[2210]: <warn> error requesting auth for org.freedesktop.NetworkManager.sleep-wake: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.9763': no such name
Feb  1 20:09:34 joe NetworkManager[2210]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-wifi: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.9763': no such name
Feb  1 20:09:34 joe NetworkManager[2210]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-wwan: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.9763': no such name
Feb  1 20:09:34 joe NetworkManager[2210]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-wimax: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.9763': no such name
Feb  1 20:09:34 joe NetworkManager[2210]: <warn> error requesting auth for org.freedesktop.NetworkManager.network-control: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.9763': no such name
Feb  1 20:09:34 joe NetworkManager[2210]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.9763': no such name
Feb  1 20:09:34 joe NetworkManager[2210]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.9763': no such name
Feb  1 20:09:34 joe NetworkManager[2210]: <warn> error requesting auth for org.freedesktop.NetworkManager.settings.modify.system: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.9763': no such name
Feb  1 20:09:34 joe NetworkManager[2210]: <warn> error requesting auth for org.freedesktop.NetworkManager.settings.modify.own: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.9763': no such name
Feb  1 20:09:34 joe NetworkManager[2210]: <warn> error requesting auth for org.freedesktop.NetworkManager.settings.modify.hostname: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.9763': no such name
Feb  1 20:09:45 joe acpid: client 18924[0:0] has disconnected
Feb  1 20:09:59 joe gdm-simple-slave[12560]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12724]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12725]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12726]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12731]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12732]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12733]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12734]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12737]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12738]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12739]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12740]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12741]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12742]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12743]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12744]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12745]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12746]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12748]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12763]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12761]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12764]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12765]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12766]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12767]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12768]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12769]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12070]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12073]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12130]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12129]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12128]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12122]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12117]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12103]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12078]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12087]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12089]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12092]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12096]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12131]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12134]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12135]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12136]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12137]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12138]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12143]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12139]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12140]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12141]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12144]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12145]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12146]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12147]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12153]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12149]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12152]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12151]: WARNING: Failed to get value: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12775]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12776]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12790]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12777]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12778]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12779]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12780]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12792]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12799]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12798]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12800]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12802]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12807]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12808]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12803]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12804]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12805]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12806]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12809]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12810]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12812]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12814]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12816]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12819]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12820]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12811]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12813]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12815]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12817]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12818]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12821]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12822]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:09:59 joe gdm-simple-slave[12823]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:00 joe gdm-simple-slave[12915]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58667: 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. 
Feb  1 20:10:00 joe gdm-simple-slave[12916]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58668: 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. 
Feb  1 20:10:00 joe gdm-simple-slave[12917]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58669: 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. 
Feb  1 20:10:00 joe gdm-simple-slave[12918]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58670: 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. 
Feb  1 20:10:00 joe gdm-simple-slave[12919]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58671: 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. 
Feb  1 20:10:00 joe gdm-simple-slave[12920]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58672: 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. 
Feb  1 20:10:00 joe gdm-simple-slave[12921]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58673: 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. 
Feb  1 20:10:00 joe gdm-simple-slave[12922]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58674: 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. 
Feb  1 20:10:00 joe gdm-simple-slave[12923]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58675: 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. 
Feb  1 20:10:00 joe gdm-simple-slave[12924]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58676: 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. 
Feb  1 20:10:00 joe gdm-simple-slave[12925]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58677: 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. 
Feb  1 20:10:00 joe gdm-simple-slave[12926]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58678: 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. 
Feb  1 20:10:00 joe gdm-simple-slave[12927]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58679: 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. 
Feb  1 20:10:00 joe gdm-simple-slave[12928]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58680: 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. 
Feb  1 20:10:00 joe gdm-simple-slave[12929]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58681: 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. 
Feb  1 20:10:01 joe gdm-simple-slave[12930]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58682: 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. 
Feb  1 20:10:01 joe gdm-simple-slave[12932]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58683: 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. 
Feb  1 20:10:01 joe gdm-simple-slave[12933]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58684: 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. 
Feb  1 20:10:01 joe gdm-simple-slave[12934]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58685: 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. 
Feb  1 20:10:01 joe gdm-simple-slave[12935]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58686: 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. 
Feb  1 20:10:01 joe gdm-simple-slave[12936]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58687: 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. 
Feb  1 20:10:01 joe gdm-simple-slave[12937]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58688: 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. 
Feb  1 20:10:01 joe gdm-simple-slave[12938]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58689: 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. 
Feb  1 20:10:25 joe gdm-simple-slave[12818]: WARNING: Failed to get value: 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. 
Feb  1 20:10:25 joe gdm-simple-slave[12821]: WARNING: Failed to get value: 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. 
Feb  1 20:10:25 joe gdm-simple-slave[12822]: WARNING: Failed to get value: 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. 
Feb  1 20:10:25 joe gdm-simple-slave[12823]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12939]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12943]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12942]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12941]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12945]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12958]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12962]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12969]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12970]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12971]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12972]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12974]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12973]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12975]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12977]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12976]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12979]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12978]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12981]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12980]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12983]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12982]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12984]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12985]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12986]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12987]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12991]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12993]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12995]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12997]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12989]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12999]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12998]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[13000]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12996]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12560]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[13001]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12724]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12725]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12726]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12731]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12732]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12733]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12734]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12737]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12990]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12992]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12994]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12988]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12738]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12761]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12739]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12740]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12741]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12742]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12743]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12744]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12745]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12746]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12748]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12763]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12764]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12765]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12767]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12768]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12769]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12766]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12775]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12776]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12777]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12778]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12790]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12779]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12780]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12792]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12798]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12799]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12800]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12802]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12803]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12807]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12808]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12804]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12805]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12806]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12809]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12810]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12820]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12814]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12819]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12812]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12816]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12811]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12813]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12815]: WARNING: Failed to get value: 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. 
Feb  1 20:10:26 joe gdm-simple-slave[12817]: WARNING: Failed to get value: 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. 
Feb  1 20:10:27 joe gdm-simple-slave[13448]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58901: 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. 
Feb  1 20:10:27 joe gdm-simple-slave[13449]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58902: 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. 
Feb  1 20:10:27 joe gdm-simple-slave[13450]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58903: 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. 
Feb  1 20:10:27 joe gdm-simple-slave[13451]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58904: 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. 
Feb  1 20:10:27 joe gdm-simple-slave[13452]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58905: 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. 
Feb  1 20:10:27 joe gdm-simple-slave[13453]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58906: 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. 
Feb  1 20:10:27 joe gdm-simple-slave[13454]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58907: 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. 
Feb  1 20:10:27 joe gdm-simple-slave[13455]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58908: 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. 
Feb  1 20:10:27 joe gdm-simple-slave[13456]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58909: 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. 
Feb  1 20:10:31 joe gdm-simple-slave[13464]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display58910: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13860]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13881]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13872]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13887]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13890]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13891]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13894]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13897]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13898]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13903]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13915]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12976]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12977]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12978]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12979]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12980]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12981]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12982]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12983]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12984]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12985]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12986]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12987]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12988]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12989]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12990]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12991]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12992]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12993]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12994]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12995]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12996]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12997]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12998]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12999]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13000]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13001]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13919]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13920]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13921]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13922]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13923]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13924]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13925]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13926]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13927]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13928]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14108]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14109]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14110]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14111]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14112]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14113]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14114]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14115]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14116]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14117]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14118]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14119]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14120]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14121]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14122]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14123]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14124]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14125]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14126]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14127]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14128]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14129]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14130]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14134]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14135]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14136]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14137]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14138]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14139]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14140]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14141]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14142]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14143]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14144]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14145]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14146]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14147]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14148]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14149]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14150]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14151]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14153]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14152]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14154]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14155]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14156]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14157]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14158]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14159]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14160]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14161]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14163]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14164]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14165]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14166]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14167]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14168]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14169]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14170]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14171]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14175]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14176]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14177]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14178]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14179]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14180]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14184]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14198]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14205]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[14206]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13480]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13481]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13482]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13483]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13484]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13485]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13486]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13487]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[13488]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12939]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12941]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12942]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12943]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12945]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12958]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12962]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12969]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12970]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12971]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12972]: WARNING: Failed to get value: 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. 
Feb  1 20:11:18 joe gdm-simple-slave[12973]: WARNING: Failed to get value: 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. 
Feb  1 20:11:19 joe gdm-simple-slave[13498]: WARNING: Failed to get value: 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. 
Feb  1 20:11:19 joe gdm-simple-slave[13497]: WARNING: Failed to get value: 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. 
Feb  1 20:11:19 joe gdm-simple-slave[13496]: WARNING: Failed to get value: 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. 
Feb  1 20:11:19 joe gdm-simple-slave[13495]: WARNING: Failed to get value: 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. 
Feb  1 20:11:19 joe gdm-simple-slave[13494]: WARNING: Failed to get value: 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. 
Feb  1 20:11:19 joe gdm-simple-slave[13493]: WARNING: Failed to get value: 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. 
Feb  1 20:11:19 joe gdm-simple-slave[13492]: WARNING: Failed to get value: 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. 
Feb  1 20:11:19 joe gdm-simple-slave[13858]: WARNING: Failed to get value: 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. 
Feb  1 20:11:19 joe gdm-simple-slave[13848]: WARNING: Failed to get value: 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. 
Feb  1 20:11:19 joe gdm-simple-slave[13500]: WARNING: Failed to get value: 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. 
Feb  1 20:11:19 joe gdm-simple-slave[13499]: WARNING: Failed to get value: 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. 
Feb  1 20:11:19 joe gdm-simple-slave[13491]: WARNING: Failed to get value: 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. 
Feb  1 20:11:19 joe gdm-simple-slave[13490]: WARNING: Failed to get value: 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. 
Feb  1 20:11:19 joe gdm-simple-slave[12974]: WARNING: Failed to get value: 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. 
Feb  1 20:11:19 joe gdm-simple-slave[13489]: WARNING: Failed to get value: 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. 
Feb  1 20:11:19 joe gdm-simple-slave[12975]: WARNING: Failed to get value: 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. 
Feb  1 20:11:26 joe acpid: client connected from 15033[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15051[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15034[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15030[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client 15033[0:0] has disconnected
Feb  1 20:11:26 joe acpid: client 15051[0:0] has disconnected
Feb  1 20:11:26 joe acpid: client 15034[0:0] has disconnected
Feb  1 20:11:26 joe acpid: client 15030[0:0] has disconnected
Feb  1 20:11:26 joe acpid: client connected from 15035[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client 15035[0:0] has disconnected
Feb  1 20:11:26 joe acpid: client connected from 15036[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client 15036[0:0] has disconnected
Feb  1 20:11:26 joe acpid: client connected from 15037[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client 15037[0:0] has disconnected
Feb  1 20:11:26 joe acpid: client connected from 15044[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client 15044[0:0] has disconnected
Feb  1 20:11:26 joe acpid: client connected from 15048[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client 15048[0:0] has disconnected
Feb  1 20:11:26 joe acpid: client connected from 15039[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client 15039[0:0] has disconnected
Feb  1 20:11:26 joe acpid: client connected from 15038[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client 15038[0:0] has disconnected
Feb  1 20:11:26 joe acpid: client connected from 15042[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client 15042[0:0] has disconnected
Feb  1 20:11:26 joe acpid: client connected from 15047[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client 15047[0:0] has disconnected
Feb  1 20:11:26 joe acpid: client connected from 15043[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client 15043[0:0] has disconnected
Feb  1 20:11:26 joe acpid: client connected from 15064[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client 15064[0:0] has disconnected
Feb  1 20:11:26 joe acpid: client connected from 15045[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15059[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15063[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15065[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15060[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15068[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15094[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15062[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15061[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15067[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15066[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15092[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15093[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15098[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15099[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15101[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15103[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15096[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15104[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15100[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15041[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15102[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:26 joe acpid: client connected from 15097[0:0]
Feb  1 20:11:26 joe acpid: 1 client rule loaded
Feb  1 20:11:44 joe acpid: client 15045[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15059[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15063[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15065[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15060[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15068[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15094[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15062[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15061[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15067[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15066[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15092[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15093[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15098[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15099[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15101[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15103[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15096[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15104[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15100[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15041[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15102[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client 15097[0:0] has disconnected
Feb  1 20:11:44 joe acpid: client connected from 15529[0:0]
Feb  1 20:11:44 joe acpid: 1 client rule loaded
Feb  1 20:11:44 joe acpid: client connected from 15531[0:0]
Feb  1 20:11:44 joe acpid: 1 client rule loaded
Feb  1 20:11:47 joe gdm-simple-slave[14108]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14109]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14121]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14120]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14119]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14118]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14117]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14116]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14115]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14110]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14111]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14112]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14113]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14114]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14122]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14123]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14124]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14125]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14126]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14127]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14128]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14129]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14149]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14150]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14135]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14142]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14137]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14136]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14134]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14144]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14145]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14138]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14139]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14141]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14143]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14151]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14146]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14147]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14152]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14148]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14153]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14140]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14130]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14154]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14155]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14156]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14170]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14157]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14169]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14158]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14168]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14159]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14167]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14160]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14166]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14161]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14164]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14163]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14165]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14205]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14198]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14184]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14180]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14179]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14178]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14177]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14176]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14175]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14171]: WARNING: Failed to get value: 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. 
Feb  1 20:11:47 joe gdm-simple-slave[14206]: WARNING: Failed to get value: 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. 
Feb  1 20:11:49 joe gdm-simple-slave[15702]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:12:12 joe gdm-simple-slave[15105]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15164]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15165]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15166]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15167]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15168]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15169]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15170]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15171]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15172]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15173]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15174]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15175]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15176]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15177]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15178]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15179]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15180]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15181]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15182]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15183]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15184]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15185]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15186]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15187]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15188]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15189]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15190]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15191]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15192]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15194]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15195]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15196]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15197]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15198]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15199]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15200]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15201]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15202]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15203]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15205]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15214]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15219]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15220]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15221]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15222]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15223]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15224]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15225]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15226]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15227]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15228]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15237]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15248]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15251]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15253]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15252]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15247]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15249]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15254]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15244]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15245]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15250]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15246]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15216]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15217]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15218]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15215]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15514]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15549]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15550]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15551]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15552]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15553]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15554]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15555]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15556]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15557]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15558]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15559]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15560]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15561]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15562]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:12 joe gdm-simple-slave[15577]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:13 joe gdm-simple-slave[15748]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display59769: 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. 
Feb  1 20:12:13 joe gdm-simple-slave[15750]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display59770: 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. 
Feb  1 20:12:13 joe gdm-simple-slave[15757]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display59771: 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. 
Feb  1 20:12:13 joe gdm-simple-slave[15762]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display59772: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15822]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15823]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15824]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15825]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15826]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15827]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15828]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15829]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15830]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15831]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15832]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15833]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15834]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15843]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15105]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15164]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15165]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15166]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15167]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15168]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15169]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15170]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15171]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15172]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15173]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15174]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15176]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15175]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15178]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15177]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15852]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15179]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15180]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15181]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15182]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15183]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15184]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15185]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15186]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15187]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15188]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15189]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15190]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15191]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15192]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15194]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15195]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15196]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15197]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15198]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15199]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15200]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15201]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15202]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15203]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15205]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15214]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15215]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15216]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15217]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15218]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15219]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15220]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15221]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15222]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15223]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15224]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15225]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15226]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15227]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15228]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15237]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15244]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15245]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15246]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15247]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15248]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15249]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15250]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15251]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15252]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15253]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15254]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15514]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15549]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15550]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15551]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15552]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15553]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15554]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15555]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15556]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15557]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15558]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15559]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15560]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15561]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15562]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15577]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15768]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15769]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15770]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15771]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15772]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15773]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15774]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15775]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15776]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15782]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15777]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15778]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15779]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15780]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15781]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15783]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15784]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15785]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15789]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15790]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15791]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15793]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15795]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15797]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15792]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15794]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15796]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15798]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15799]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15800]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15801]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15802]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15803]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15804]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15805]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15806]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15807]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15808]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15809]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15810]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15821]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15816]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15819]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15818]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15817]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15814]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15813]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15820]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15815]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15812]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[15811]: WARNING: Failed to get value: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[16194]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display59986: 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. 
Feb  1 20:12:38 joe gdm-simple-slave[16195]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display59987: 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. 
Feb  1 20:12:39 joe gdm-simple-slave[16197]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display59988: 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. 
Feb  1 20:12:39 joe gdm-simple-slave[16220]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display59996: 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. 
Feb  1 20:12:42 joe gdm-simple-slave[16695]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:12:42 joe gdm-simple-slave[16698]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:12:42 joe gdm-simple-slave[16700]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:12:42 joe gdm-simple-slave[16801]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:12:42 joe gdm-simple-slave[16805]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:13:30 joe gdm-simple-slave[15822]: WARNING: Failed to get value: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[15824]: WARNING: Failed to get value: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[15823]: WARNING: Failed to get value: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[15825]: WARNING: Failed to get value: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[15826]: WARNING: Failed to get value: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[15827]: WARNING: Failed to get value: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[15828]: WARNING: Failed to get value: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[15829]: WARNING: Failed to get value: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[15830]: WARNING: Failed to get value: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[15831]: WARNING: Failed to get value: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[15832]: WARNING: Failed to get value: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[15833]: WARNING: Failed to get value: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[15834]: WARNING: Failed to get value: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[15843]: WARNING: Failed to get value: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[15852]: WARNING: Failed to get value: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16829]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16830]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16831]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16832]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16833]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16834]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16835]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16836]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16837]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16838]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16839]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16840]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16841]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16842]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16843]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16844]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16845]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16846]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16847]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16848]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16849]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16850]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16851]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16852]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16853]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16855]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16856]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16857]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16858]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16859]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16860]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16861]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16862]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16863]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16864]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16865]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16866]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16867]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16868]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16869]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16870]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16871]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16872]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16873]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16874]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16875]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16876]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16877]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16878]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16881]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16882]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16883]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16884]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16885]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16886]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16887]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16888]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16893]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16906]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16913]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16914]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16915]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16916]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16917]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16918]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16919]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16920]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16921]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16922]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16923]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16924]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16925]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16926]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[16927]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17218]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17350]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17351]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17352]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17353]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17354]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17355]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17356]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17359]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17360]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17361]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17362]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17363]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17364]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17365]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17366]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17367]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17370]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17369]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17368]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:30 joe gdm-simple-slave[17371]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60420: 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. 
Feb  1 20:13:31 joe gdm-simple-slave[17374]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60421: 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. 
Feb  1 20:13:31 joe gdm-simple-slave[17375]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60422: 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. 
Feb  1 20:13:31 joe gdm-simple-slave[17376]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60423: 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. 
Feb  1 20:13:31 joe gdm-simple-slave[17377]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60424: 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. 
Feb  1 20:13:31 joe gdm-simple-slave[17378]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60425: 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. 
Feb  1 20:13:31 joe gdm-simple-slave[17379]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60426: 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. 
Feb  1 20:13:31 joe gdm-simple-slave[17380]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60427: 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. 
Feb  1 20:13:31 joe gdm-simple-slave[17381]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60428: 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. 
Feb  1 20:13:31 joe gdm-simple-slave[17382]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60429: 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. 
Feb  1 20:13:31 joe gdm-simple-slave[17383]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60430: 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. 
Feb  1 20:13:31 joe gdm-simple-slave[17389]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60431: 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. 
Feb  1 20:13:31 joe gdm-simple-slave[17401]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60432: 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. 
Feb  1 20:13:31 joe gdm-simple-slave[17402]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60433: 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. 
Feb  1 20:13:32 joe gdm-simple-slave[17403]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60434: 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. 
Feb  1 20:13:32 joe gdm-simple-slave[17410]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60435: 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. 
Feb  1 20:13:32 joe gdm-simple-slave[17411]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60436: 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. 
Feb  1 20:13:32 joe gdm-simple-slave[17412]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60437: 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. 
Feb  1 20:13:35 joe gdm-simple-slave[17413]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60438: 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. 
Feb  1 20:13:35 joe gdm-simple-slave[17414]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60439: 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. 
Feb  1 20:13:35 joe gdm-simple-slave[17415]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60440: 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. 
Feb  1 20:13:35 joe gdm-simple-slave[17416]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60441: 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. 
Feb  1 20:13:35 joe gdm-simple-slave[17417]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60442: 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. 
Feb  1 20:13:35 joe gdm-simple-slave[17418]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60443: 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. 
Feb  1 20:13:35 joe gdm-simple-slave[17419]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60444: 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. 
Feb  1 20:13:35 joe acpid: client 15529[0:0] has disconnected
Feb  1 20:13:35 joe acpid: client 15531[0:0] has disconnected
Feb  1 20:13:35 joe acpid: client connected from 17853[0:0]
Feb  1 20:13:35 joe acpid: 1 client rule loaded
Feb  1 20:13:35 joe acpid: client 17853[0:0] has disconnected
Feb  1 20:13:35 joe acpid: client connected from 17844[0:0]
Feb  1 20:13:35 joe acpid: 1 client rule loaded
Feb  1 20:13:35 joe acpid: client 17844[0:0] has disconnected
Feb  1 20:13:35 joe acpid: client connected from 17852[0:0]
Feb  1 20:13:35 joe acpid: 1 client rule loaded
Feb  1 20:13:35 joe acpid: client 17852[0:0] has disconnected
Feb  1 20:13:35 joe acpid: client connected from 17846[0:0]
Feb  1 20:13:35 joe acpid: 1 client rule loaded
Feb  1 20:13:35 joe acpid: client 17846[0:0] has disconnected
Feb  1 20:13:35 joe acpid: client connected from 17845[0:0]
Feb  1 20:13:35 joe acpid: 1 client rule loaded
Feb  1 20:13:35 joe acpid: client 17845[0:0] has disconnected
Feb  1 20:13:35 joe acpid: client connected from 17849[0:0]
Feb  1 20:13:35 joe acpid: 1 client rule loaded
Feb  1 20:13:35 joe acpid: client 17849[0:0] has disconnected
Feb  1 20:13:35 joe acpid: client connected from 17851[0:0]
Feb  1 20:13:35 joe acpid: 1 client rule loaded
Feb  1 20:13:35 joe acpid: client 17851[0:0] has disconnected
Feb  1 20:13:35 joe acpid: client connected from 17850[0:0]
Feb  1 20:13:35 joe acpid: 1 client rule loaded
Feb  1 20:13:35 joe acpid: client 17850[0:0] has disconnected
Feb  1 20:13:35 joe acpid: client connected from 17847[0:0]
Feb  1 20:13:35 joe acpid: 1 client rule loaded
Feb  1 20:13:57 joe gdm-simple-slave[16829]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16830]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16831]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16832]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16833]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16834]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16835]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16836]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16837]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16838]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16839]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16840]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16841]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16842]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16843]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16844]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16845]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16846]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16847]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16848]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16849]: WARNING: Failed to get value: 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. 
Feb  1 20:13:57 joe gdm-simple-slave[16850]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16851]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16852]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16853]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16855]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16856]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16857]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16858]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16859]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16860]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16861]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16862]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16863]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16864]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16865]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16866]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16867]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16868]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16869]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16870]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16871]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16872]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16873]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16874]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16875]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16876]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16877]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16878]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16881]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16882]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16883]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16884]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16885]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16886]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16914]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16887]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16888]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16893]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16906]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16913]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16915]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16916]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16917]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16918]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16919]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16920]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16921]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16922]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16923]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16924]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16925]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16926]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[16927]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17218]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17350]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17351]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17352]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17353]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17354]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe acpid: client 17847[0:0] has disconnected
Feb  1 20:13:58 joe gdm-simple-slave[17355]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17356]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17359]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17360]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17361]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17362]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17363]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17364]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17365]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17366]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17367]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17370]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17368]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17369]: WARNING: Failed to get value: 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. 
Feb  1 20:13:58 joe acpid: client connected from 18236[0:0]
Feb  1 20:13:58 joe acpid: 1 client rule loaded
Feb  1 20:13:58 joe acpid: client 18236[0:0] has disconnected
Feb  1 20:13:58 joe acpid: client connected from 18237[0:0]
Feb  1 20:13:58 joe acpid: 1 client rule loaded
Feb  1 20:13:58 joe acpid: client 18237[0:0] has disconnected
Feb  1 20:13:58 joe acpid: client connected from 18242[0:0]
Feb  1 20:13:58 joe acpid: 1 client rule loaded
Feb  1 20:13:58 joe acpid: client 18242[0:0] has disconnected
Feb  1 20:13:58 joe acpid: client connected from 18241[0:0]
Feb  1 20:13:58 joe acpid: 1 client rule loaded
Feb  1 20:13:58 joe acpid: client 18241[0:0] has disconnected
Feb  1 20:13:58 joe acpid: client connected from 18240[0:0]
Feb  1 20:13:58 joe acpid: 1 client rule loaded
Feb  1 20:13:58 joe acpid: client 18240[0:0] has disconnected
Feb  1 20:13:58 joe acpid: client connected from 18239[0:0]
Feb  1 20:13:58 joe acpid: 1 client rule loaded
Feb  1 20:13:58 joe gdm-simple-slave[17420]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17421]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17422]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17423]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17424]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17425]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17426]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17427]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17428]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17429]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17430]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17431]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17432]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17433]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17434]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17435]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17436]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17437]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17438]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17439]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17855]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60642: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17863]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60643: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17864]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60644: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17865]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60645: 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. 
Feb  1 20:13:58 joe gdm-simple-slave[17866]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60646: 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. 
Feb  1 20:13:59 joe gdm-simple-slave[17867]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60647: 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. 
Feb  1 20:13:59 joe gdm-simple-slave[17868]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60648: 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. 
Feb  1 20:13:59 joe gdm-simple-slave[17869]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60649: 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. 
Feb  1 20:13:59 joe gdm-simple-slave[17870]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display60650: 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. 
Feb  1 20:13:59 joe gdm-simple-slave[18408]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:14:48 joe gdm-simple-slave[18286]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18315]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18312]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18309]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18306]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18303]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18299]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18598]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18596]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18595]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18594]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18593]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18592]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18591]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18590]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18589]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18588]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18581]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18296]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18559]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18294]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18321]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18609]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18562]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18561]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18608]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18325]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18292]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18560]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18293]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18331]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18607]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18295]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18332]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18563]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18328]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18564]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18333]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18334]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18335]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18336]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18558]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18599]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18600]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18601]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18603]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18606]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18610]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18611]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18612]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18613]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18614]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18615]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18616]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18617]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18618]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18619]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18620]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18621]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18622]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18623]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18624]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18625]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18626]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18627]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18628]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18630]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18631]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18632]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18633]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18634]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18635]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18636]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18637]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18638]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18639]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18640]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18289]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18641]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18642]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18643]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18644]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18645]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18646]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18647]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18648]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18649]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18650]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18651]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18652]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18653]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18654]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18655]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18656]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18665]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18674]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18681]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18682]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18683]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18684]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18685]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18686]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18687]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18688]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18689]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18690]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18691]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18692]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18693]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18694]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18695]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18696]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18697]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18698]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18699]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18700]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18701]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18702]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18703]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18704]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18705]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18706]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18707]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18708]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18709]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18251]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18252]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18254]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18257]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18262]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18265]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18268]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18280]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[18283]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17420]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17421]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17422]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17423]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17424]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17425]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17426]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17427]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17428]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17429]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17430]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17431]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17432]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17433]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17434]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17435]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17436]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17437]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17438]: WARNING: Failed to get value: 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. 
Feb  1 20:14:48 joe gdm-simple-slave[17439]: WARNING: Failed to get value: 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. 
Feb  1 20:14:55 joe acpid: client 18239[0:0] has disconnected
Feb  1 20:14:55 joe acpid: client connected from 19529[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client connected from 19527[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client connected from 19530[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client 19529[0:0] has disconnected
Feb  1 20:14:55 joe acpid: client 19527[0:0] has disconnected
Feb  1 20:14:55 joe acpid: client 19530[0:0] has disconnected
Feb  1 20:14:55 joe acpid: client connected from 19540[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client 19540[0:0] has disconnected
Feb  1 20:14:55 joe acpid: client connected from 19532[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client 19532[0:0] has disconnected
Feb  1 20:14:55 joe acpid: client connected from 19538[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client 19538[0:0] has disconnected
Feb  1 20:14:55 joe acpid: client connected from 19528[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client 19528[0:0] has disconnected
Feb  1 20:14:55 joe acpid: client connected from 19533[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client 19533[0:0] has disconnected
Feb  1 20:14:55 joe acpid: client connected from 19541[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client 19541[0:0] has disconnected
Feb  1 20:14:55 joe acpid: client connected from 19537[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client 19537[0:0] has disconnected
Feb  1 20:14:55 joe acpid: client connected from 19535[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client 19535[0:0] has disconnected
Feb  1 20:14:55 joe acpid: client connected from 19534[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client 19534[0:0] has disconnected
Feb  1 20:14:55 joe acpid: client connected from 19563[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client 19563[0:0] has disconnected
Feb  1 20:14:55 joe acpid: client connected from 19566[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client 19566[0:0] has disconnected
Feb  1 20:14:55 joe acpid: client connected from 19561[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client 19561[0:0] has disconnected
Feb  1 20:14:55 joe acpid: client connected from 19564[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client connected from 19562[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client connected from 19567[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client connected from 19565[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:14:55 joe acpid: client connected from 19536[0:0]
Feb  1 20:14:55 joe acpid: 1 client rule loaded
Feb  1 20:15:17 joe gdm-simple-slave[18559]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18560]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18561]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18562]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18563]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18564]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18581]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18588]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18589]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18590]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18591]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18592]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18593]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18594]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18595]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18596]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18598]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18607]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18608]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18609]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18558]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18599]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18600]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18601]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18610]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18606]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18603]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18611]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18613]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18612]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18614]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18615]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18616]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18617]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18618]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18619]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18620]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18621]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18622]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18623]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18624]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18625]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18626]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18627]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18628]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18630]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18631]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18632]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18633]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18634]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18635]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18636]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18637]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18638]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18639]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18640]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18641]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18642]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18643]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18644]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18645]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18646]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18647]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18648]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18649]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18650]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18651]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18652]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18653]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18654]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18655]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18656]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18665]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18674]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18681]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18682]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18683]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18684]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18685]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18686]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18687]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18688]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18689]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18690]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18691]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18692]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18693]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18694]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18695]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18696]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18697]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18698]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18699]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18700]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18701]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18702]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18703]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18704]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18705]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18706]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18707]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18708]: WARNING: Failed to get value: 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. 
Feb  1 20:15:17 joe gdm-simple-slave[18709]: WARNING: Failed to get value: 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. 
Feb  1 20:15:20 joe gdm-simple-slave[19577]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61289: 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. 
Feb  1 20:15:20 joe gdm-simple-slave[19578]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61290: 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. 
Feb  1 20:15:20 joe gdm-simple-slave[19579]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61291: 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. 
Feb  1 20:15:20 joe gdm-simple-slave[19580]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61292: 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. 
Feb  1 20:15:20 joe gdm-simple-slave[19581]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61293: 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. 
Feb  1 20:15:20 joe gdm-simple-slave[19582]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61294: 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. 
Feb  1 20:15:20 joe gdm-simple-slave[19583]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61295: 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. 
Feb  1 20:15:20 joe gdm-simple-slave[19584]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61296: 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. 
Feb  1 20:15:20 joe gdm-simple-slave[19585]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61297: 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. 
Feb  1 20:15:20 joe gdm-simple-slave[19586]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61298: 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. 
Feb  1 20:15:20 joe gdm-simple-slave[19587]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61299: 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. 
Feb  1 20:15:20 joe gdm-simple-slave[19588]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61300: 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. 
Feb  1 20:15:20 joe gdm-simple-slave[19589]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61301: 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. 
Feb  1 20:15:20 joe gdm-simple-slave[19590]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61302: 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. 
Feb  1 20:15:20 joe gdm-simple-slave[19591]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61303: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[19608]: WARNING: Failed to get value: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[19609]: WARNING: Failed to get value: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[19610]: WARNING: Failed to get value: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[19611]: WARNING: Failed to get value: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20230]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20231]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20232]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20233]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20234]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20235]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20236]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20237]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20238]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20239]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20240]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20241]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20242]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20243]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20244]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20245]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20246]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20247]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20248]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20249]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:07 joe gdm-simple-slave[20250]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20254]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20256]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20257]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20258]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20259]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20260]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20261]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20262]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20263]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20264]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20265]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20266]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20267]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20268]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20269]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20270]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20271]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20272]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20273]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20274]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20293]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20285]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20275]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20307]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20302]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20304]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20305]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20306]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20303]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20301]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20300]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20308]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20309]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20310]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20311]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20312]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20313]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20314]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20315]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20316]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20317]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20318]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20322]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20323]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20324]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20325]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20326]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20327]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20328]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20329]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20330]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20331]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20332]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20337]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20339]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20340]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20334]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20338]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20342]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20336]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20343]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20333]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20341]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20335]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20348]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20347]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20344]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20345]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20346]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20321]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20319]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20320]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20349]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20350]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20351]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20352]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20353]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20354]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20355]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20356]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20357]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20358]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20359]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20360]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20361]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20362]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20363]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20364]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19613]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19621]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19620]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19623]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19622]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19619]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19624]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19614]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19615]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19618]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19612]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19616]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19627]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19595]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19629]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19594]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19596]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19628]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19593]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19626]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19592]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19597]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19625]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19607]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19606]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19598]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19603]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19604]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19605]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19602]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19600]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[19599]: WARNING: Failed to get value: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20629]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61723: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20630]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61724: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20631]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61725: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20632]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61726: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20633]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61727: 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. 
Feb  1 20:16:08 joe gdm-simple-slave[20634]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61728: 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. 
Feb  1 20:16:11 joe gdm-simple-slave[20668]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61740: 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. 
Feb  1 20:16:11 joe gdm-simple-slave[20669]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61741: 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. 
Feb  1 20:16:11 joe gdm-simple-slave[20670]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61742: 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. 
Feb  1 20:16:12 joe acpid: client 19564[0:0] has disconnected
Feb  1 20:16:12 joe acpid: client 19562[0:0] has disconnected
Feb  1 20:16:12 joe acpid: client 19567[0:0] has disconnected
Feb  1 20:16:12 joe acpid: client 19565[0:0] has disconnected
Feb  1 20:16:12 joe acpid: client 19536[0:0] has disconnected
Feb  1 20:16:12 joe acpid: client connected from 21137[0:0]
Feb  1 20:16:12 joe acpid: 1 client rule loaded
Feb  1 20:16:12 joe acpid: client connected from 21138[0:0]
Feb  1 20:16:12 joe acpid: 1 client rule loaded
Feb  1 20:16:12 joe acpid: client connected from 21143[0:0]
Feb  1 20:16:12 joe acpid: 1 client rule loaded
Feb  1 20:16:12 joe acpid: client connected from 21144[0:0]
Feb  1 20:16:12 joe acpid: 1 client rule loaded
Feb  1 20:16:12 joe acpid: client connected from 21146[0:0]
Feb  1 20:16:12 joe acpid: 1 client rule loaded
Feb  1 20:16:12 joe acpid: client connected from 21142[0:0]
Feb  1 20:16:12 joe acpid: 1 client rule loaded
Feb  1 20:16:12 joe acpid: client connected from 21147[0:0]
Feb  1 20:16:12 joe acpid: 1 client rule loaded
Feb  1 20:16:12 joe acpid: client connected from 21148[0:0]
Feb  1 20:16:12 joe acpid: 1 client rule loaded
Feb  1 20:16:12 joe acpid: client connected from 21152[0:0]
Feb  1 20:16:12 joe acpid: 1 client rule loaded
Feb  1 20:16:12 joe acpid: client connected from 21139[0:0]
Feb  1 20:16:12 joe acpid: 1 client rule loaded
Feb  1 20:16:12 joe acpid: client connected from 21141[0:0]
Feb  1 20:16:12 joe acpid: 1 client rule loaded
Feb  1 20:16:12 joe acpid: client connected from 21150[0:0]
Feb  1 20:16:12 joe acpid: 1 client rule loaded
Feb  1 20:16:12 joe acpid: client connected from 21151[0:0]
Feb  1 20:16:12 joe acpid: 1 client rule loaded
Feb  1 20:16:12 joe acpid: client connected from 21153[0:0]
Feb  1 20:16:12 joe acpid: 1 client rule loaded
Feb  1 20:16:12 joe acpid: client connected from 21149[0:0]
Feb  1 20:16:12 joe acpid: 1 client rule loaded
Feb  1 20:16:37 joe gdm-simple-slave[20230]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20231]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20232]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20233]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20234]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20235]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20236]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20237]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20238]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20239]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20240]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20241]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20242]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20243]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20244]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20245]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20246]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20247]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20248]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20249]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20250]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20254]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20256]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20257]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20258]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20259]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20260]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20261]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20262]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20263]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20264]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20265]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20266]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20267]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20268]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20271]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20272]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20273]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20274]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20275]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20285]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20293]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20300]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20301]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20302]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20303]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20310]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20311]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20312]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20313]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20314]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20315]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20316]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20317]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20318]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20319]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20320]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20327]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20328]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20329]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20330]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20331]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20332]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20333]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20334]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20335]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20336]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20337]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20304]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20307]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20309]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20323]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20326]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20324]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20322]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20321]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20325]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20269]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20270]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20308]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20306]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20305]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20338]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20339]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20340]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20341]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20342]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20343]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20344]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20345]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20346]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20347]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20348]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20349]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20350]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20351]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20352]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20353]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20354]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20355]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20356]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20357]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20358]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20359]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20360]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20361]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20362]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20363]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[20364]: WARNING: Failed to get value: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[21220]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61946: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[21221]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61947: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[21222]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61948: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[21223]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61949: 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. 
Feb  1 20:16:37 joe gdm-simple-slave[21224]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61950: 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. 
Feb  1 20:16:38 joe gdm-simple-slave[21225]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61951: 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. 
Feb  1 20:16:38 joe gdm-simple-slave[21226]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61952: 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. 
Feb  1 20:16:38 joe gdm-simple-slave[21227]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61953: 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. 
Feb  1 20:16:38 joe gdm-simple-slave[21228]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61954: 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. 
Feb  1 20:16:38 joe gdm-simple-slave[21229]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61955: 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. 
Feb  1 20:16:38 joe gdm-simple-slave[21230]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61956: 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. 
Feb  1 20:16:38 joe gdm-simple-slave[21231]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61957: 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. 
Feb  1 20:16:38 joe gdm-simple-slave[21232]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61958: 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. 
Feb  1 20:16:38 joe gdm-simple-slave[21233]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61959: 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. 
Feb  1 20:16:38 joe gdm-simple-slave[21234]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61960: 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. 
Feb  1 20:16:38 joe gdm-simple-slave[21235]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61961: 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. 
Feb  1 20:16:38 joe gdm-simple-slave[21236]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61962: 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. 
Feb  1 20:16:38 joe gdm-simple-slave[21237]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61963: 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. 
Feb  1 20:16:39 joe gdm-simple-slave[21238]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61964: 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. 
Feb  1 20:16:39 joe gdm-simple-slave[21239]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61965: 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. 
Feb  1 20:16:39 joe gdm-simple-slave[21240]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61966: 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. 
Feb  1 20:16:39 joe gdm-simple-slave[21241]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61967: 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. 
Feb  1 20:16:39 joe gdm-simple-slave[21242]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61968: 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. 
Feb  1 20:16:39 joe gdm-simple-slave[21243]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61969: 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. 
Feb  1 20:16:39 joe gdm-simple-slave[21244]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display61970: 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. 
Feb  1 20:16:39 joe gdm-simple-slave[21684]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:16:39 joe gdm-simple-slave[21675]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:16:39 joe gdm-simple-slave[21726]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:16:39 joe gdm-simple-slave[21767]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:17:02 joe /USR/SBIN/CRON[22338]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb  1 20:17:26 joe gdm-simple-slave[21996]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22007]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22006]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22008]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22009]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22011]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22013]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22014]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22012]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22015]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22016]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22017]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22018]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22019]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22020]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22021]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22022]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22023]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22024]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22025]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22035]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22034]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22032]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22026]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22031]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22027]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22030]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22036]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22037]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22038]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22039]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22040]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22041]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22042]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22043]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22044]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22061]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22045]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22060]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22046]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22059]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22047]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22058]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22048]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22057]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22054]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22053]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22050]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22049]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22052]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22056]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22062]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22063]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22064]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22065]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22066]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22067]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22068]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22069]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22070]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22071]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22072]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22073]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22074]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22082]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22092]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22099]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22100]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22101]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22102]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22103]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22104]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22105]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22106]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22114]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22109]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22115]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22108]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22112]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22113]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22116]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22111]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22107]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22110]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22117]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22118]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22119]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22120]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22121]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22122]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22123]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22125]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22126]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22127]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22128]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22129]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22130]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22131]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22132]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22133]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22134]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22135]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22136]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22137]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22138]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22139]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22140]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22141]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22142]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22143]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[22144]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[21245]: WARNING: Failed to get value: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[21246]: WARNING: Failed to get value: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[21247]: WARNING: Failed to get value: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[21248]: WARNING: Failed to get value: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[21249]: WARNING: Failed to get value: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[21250]: WARNING: Failed to get value: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[21251]: WARNING: Failed to get value: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[21256]: WARNING: Failed to get value: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[21269]: WARNING: Failed to get value: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[21270]: WARNING: Failed to get value: 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. 
Feb  1 20:17:26 joe gdm-simple-slave[21271]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21955]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21297]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21298]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21299]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21296]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21295]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21277]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21274]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21273]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21954]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21272]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21965]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21962]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21966]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21960]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21968]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21963]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21961]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21967]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21964]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21957]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21956]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21969]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21991]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21990]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21992]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21993]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21989]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21995]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21981]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21970]: WARNING: Failed to get value: 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. 
Feb  1 20:17:27 joe gdm-simple-slave[21994]: WARNING: Failed to get value: 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. 
Feb  1 20:17:51 joe gdm-simple-slave[22125]: WARNING: Failed to get value: 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. 
Feb  1 20:17:51 joe gdm-simple-slave[22126]: WARNING: Failed to get value: 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. 
Feb  1 20:17:51 joe gdm-simple-slave[22127]: WARNING: Failed to get value: 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. 
Feb  1 20:17:51 joe gdm-simple-slave[22128]: WARNING: Failed to get value: 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. 
Feb  1 20:17:51 joe gdm-simple-slave[22129]: WARNING: Failed to get value: 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. 
Feb  1 20:17:51 joe gdm-simple-slave[22130]: WARNING: Failed to get value: 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. 
Feb  1 20:17:51 joe gdm-simple-slave[22131]: WARNING: Failed to get value: 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. 
Feb  1 20:17:51 joe gdm-simple-slave[22132]: WARNING: Failed to get value: 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. 
Feb  1 20:17:51 joe gdm-simple-slave[22133]: WARNING: Failed to get value: 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. 
Feb  1 20:17:51 joe gdm-simple-slave[22134]: WARNING: Failed to get value: 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. 
Feb  1 20:17:51 joe gdm-simple-slave[22135]: WARNING: Failed to get value: 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. 
Feb  1 20:17:52 joe gdm-simple-slave[22143]: WARNING: Failed to get value: 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. 
Feb  1 20:17:52 joe gdm-simple-slave[22142]: WARNING: Failed to get value: 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. 
Feb  1 20:17:52 joe gdm-simple-slave[22141]: WARNING: Failed to get value: 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. 
Feb  1 20:17:52 joe gdm-simple-slave[22140]: WARNING: Failed to get value: 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. 
Feb  1 20:17:52 joe gdm-simple-slave[22139]: WARNING: Failed to get value: 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. 
Feb  1 20:17:52 joe gdm-simple-slave[22136]: WARNING: Failed to get value: 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. 
Feb  1 20:17:52 joe gdm-simple-slave[22137]: WARNING: Failed to get value: 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. 
Feb  1 20:17:52 joe gdm-simple-slave[22138]: WARNING: Failed to get value: 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. 
Feb  1 20:17:52 joe gdm-simple-slave[22144]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[21996]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22006]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22007]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22008]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22009]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22011]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22012]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22013]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22014]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22015]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22016]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22017]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22027]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22030]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22024]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22023]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22025]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22020]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22021]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22018]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22026]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22019]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22022]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22035]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22036]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22037]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22038]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22039]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22040]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22041]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22042]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22043]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22044]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22045]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22053]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22057]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22048]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22052]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22049]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22071]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22072]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22073]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22074]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22082]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22092]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22069]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22066]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22065]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22067]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22068]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22064]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22062]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22063]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22060]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22061]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22059]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22099]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22070]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22032]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22031]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22034]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22100]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22101]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22102]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22103]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22104]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22105]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22106]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22107]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22108]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22109]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22054]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22058]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22046]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22056]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22050]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22047]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22110]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22111]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22112]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22113]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22114]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22115]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22116]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22117]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22118]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22119]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22120]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22121]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22122]: WARNING: Failed to get value: 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. 
Feb  1 20:17:56 joe gdm-simple-slave[22123]: WARNING: Failed to get value: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23356]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23483]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23484]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23485]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23486]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23487]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23488]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23489]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23528]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23527]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23526]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23525]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23491]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23490]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23523]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23529]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23530]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23531]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23532]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23533]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23534]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23535]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23536]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23538]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23537]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23539]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23540]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23541]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23542]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23543]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23544]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23545]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23546]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23547]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:23 joe gdm-simple-slave[23548]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:24 joe gdm-simple-slave[23549]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:24 joe gdm-simple-slave[23552]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:24 joe gdm-simple-slave[23551]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:24 joe gdm-simple-slave[23553]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:24 joe gdm-simple-slave[23555]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:24 joe gdm-simple-slave[23556]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:24 joe gdm-simple-slave[23557]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:24 joe gdm-simple-slave[23558]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23817]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62814: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23818]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62815: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23819]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62816: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23820]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62817: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23821]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62818: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23822]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62819: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23823]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62820: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23824]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62821: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23825]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62822: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23826]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62823: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23827]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62824: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23828]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62825: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23831]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62828: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23829]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62826: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23832]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62829: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23834]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62831: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23830]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62827: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23836]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62833: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23833]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62830: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23835]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62832: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23837]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62834: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23839]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62835: 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. 
Feb  1 20:18:25 joe gdm-simple-slave[23840]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62836: 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. 
Feb  1 20:18:26 joe gdm-simple-slave[23841]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62837: 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. 
Feb  1 20:18:26 joe gdm-simple-slave[23844]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62838: 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. 
Feb  1 20:18:26 joe gdm-simple-slave[23845]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62839: 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. 
Feb  1 20:18:26 joe gdm-simple-slave[23846]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62840: 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. 
Feb  1 20:18:26 joe gdm-simple-slave[23847]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62841: 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. 
Feb  1 20:18:26 joe gdm-simple-slave[23848]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62842: 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. 
Feb  1 20:18:26 joe gdm-simple-slave[23849]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62843: 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. 
Feb  1 20:18:26 joe gdm-simple-slave[23850]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62844: 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. 
Feb  1 20:18:26 joe gdm-simple-slave[23851]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62845: 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. 
Feb  1 20:18:26 joe gdm-simple-slave[23853]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62846: 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. 
Feb  1 20:18:26 joe gdm-simple-slave[23854]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62847: 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. 
Feb  1 20:18:27 joe gdm-simple-slave[23855]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62848: 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. 
Feb  1 20:18:27 joe gdm-simple-slave[23856]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62849: 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. 
Feb  1 20:18:27 joe gdm-simple-slave[23857]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62850: 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. 
Feb  1 20:18:27 joe gdm-simple-slave[23858]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62851: 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. 
Feb  1 20:18:27 joe gdm-simple-slave[23859]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62852: 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. 
Feb  1 20:18:27 joe gdm-simple-slave[23860]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62853: 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. 
Feb  1 20:18:27 joe gdm-simple-slave[23861]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62854: 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. 
Feb  1 20:18:27 joe gdm-simple-slave[23862]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62855: 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. 
Feb  1 20:18:27 joe gdm-simple-slave[23863]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62856: 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. 
Feb  1 20:18:27 joe gdm-simple-slave[23864]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62857: 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. 
Feb  1 20:18:27 joe gdm-simple-slave[23865]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62858: 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. 
Feb  1 20:18:27 joe gdm-simple-slave[23866]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62859: 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. 
Feb  1 20:18:27 joe gdm-simple-slave[23867]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62860: 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. 
Feb  1 20:18:27 joe gdm-simple-slave[23868]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62861: 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. 
Feb  1 20:18:28 joe gdm-simple-slave[23869]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62862: 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. 
Feb  1 20:18:28 joe gdm-simple-slave[23871]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62863: 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. 
Feb  1 20:18:28 joe gdm-simple-slave[23872]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62864: 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. 
Feb  1 20:18:28 joe gdm-simple-slave[23873]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62865: 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. 
Feb  1 20:18:28 joe gdm-simple-slave[23874]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62866: 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. 
Feb  1 20:18:28 joe gdm-simple-slave[23875]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62867: 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. 
Feb  1 20:18:28 joe gdm-simple-slave[23876]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62868: 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. 
Feb  1 20:18:28 joe gdm-simple-slave[23877]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62869: 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. 
Feb  1 20:18:28 joe gdm-simple-slave[23879]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62870: 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. 
Feb  1 20:18:28 joe gdm-simple-slave[23892]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62871: 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. 
Feb  1 20:18:28 joe gdm-simple-slave[23902]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62872: 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. 
Feb  1 20:18:28 joe gdm-simple-slave[23903]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62873: 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. 
Feb  1 20:18:29 joe gdm-simple-slave[23904]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62874: 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. 
Feb  1 20:18:29 joe gdm-simple-slave[23905]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62875: 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. 
Feb  1 20:18:29 joe gdm-simple-slave[23906]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62876: 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. 
Feb  1 20:18:29 joe gdm-simple-slave[23907]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62877: 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. 
Feb  1 20:18:30 joe gdm-simple-slave[23908]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62878: 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. 
Feb  1 20:18:30 joe gdm-simple-slave[23909]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62879: 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. 
Feb  1 20:18:30 joe gdm-simple-slave[23910]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62880: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23911]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62881: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23912]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62882: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23913]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62883: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23914]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62884: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23915]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62885: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23916]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62886: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23917]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62887: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23919]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62889: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23918]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62888: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23920]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62890: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23921]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62891: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23923]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62893: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23926]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62896: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23922]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62892: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23928]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62898: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23924]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62894: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23930]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62900: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23925]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62895: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23927]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62897: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23929]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62899: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23931]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62901: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23932]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62902: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23934]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62904: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23933]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62903: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23935]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62905: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23936]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62906: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23937]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62907: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23938]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62908: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23939]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62909: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23940]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62910: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23941]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62911: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23942]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62912: 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. 
Feb  1 20:18:31 joe gdm-simple-slave[23943]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62913: 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. 
Feb  1 20:18:32 joe gdm-simple-slave[23944]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62914: 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. 
Feb  1 20:18:32 joe gdm-simple-slave[23945]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62915: 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. 
Feb  1 20:18:32 joe gdm-simple-slave[23946]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62916: 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. 
Feb  1 20:18:32 joe gdm-simple-slave[23947]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62917: 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. 
Feb  1 20:18:32 joe gdm-simple-slave[23948]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62918: 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. 
Feb  1 20:18:32 joe gdm-simple-slave[23949]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62919: 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. 
Feb  1 20:18:32 joe gdm-simple-slave[23950]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62920: 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. 
Feb  1 20:18:32 joe gdm-simple-slave[23951]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62921: 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. 
Feb  1 20:18:32 joe gdm-simple-slave[23952]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62922: 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. 
Feb  1 20:18:32 joe gdm-simple-slave[23953]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62923: 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. 
Feb  1 20:18:32 joe gdm-simple-slave[23954]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display62924: 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. 
Feb  1 20:18:33 joe gdm-simple-slave[24402]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:18:33 joe gdm-simple-slave[24419]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:18:33 joe gdm-simple-slave[24567]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:18:33 joe gdm-simple-slave[24565]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:18:33 joe gdm-simple-slave[24577]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:18:34 joe acpid: client 21137[0:0] has disconnected
Feb  1 20:18:34 joe acpid: client 21138[0:0] has disconnected
Feb  1 20:18:34 joe acpid: client 21143[0:0] has disconnected
Feb  1 20:18:34 joe acpid: client 21144[0:0] has disconnected
Feb  1 20:18:34 joe acpid: client 21146[0:0] has disconnected
Feb  1 20:18:34 joe acpid: client 21142[0:0] has disconnected
Feb  1 20:18:34 joe acpid: client 21147[0:0] has disconnected
Feb  1 20:18:34 joe acpid: client 21148[0:0] has disconnected
Feb  1 20:18:34 joe acpid: client 21152[0:0] has disconnected
Feb  1 20:18:34 joe acpid: client 21139[0:0] has disconnected
Feb  1 20:18:34 joe acpid: client 21141[0:0] has disconnected
Feb  1 20:18:34 joe acpid: client 21150[0:0] has disconnected
Feb  1 20:18:34 joe acpid: client 21151[0:0] has disconnected
Feb  1 20:18:34 joe acpid: client 21153[0:0] has disconnected
Feb  1 20:18:34 joe acpid: client 21149[0:0] has disconnected
Feb  1 20:19:22 joe gdm-simple-slave[23540]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23541]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23542]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23543]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23544]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23545]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23546]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23547]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23548]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23549]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23551]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23552]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23553]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23555]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23556]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23557]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23558]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24594]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24595]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24596]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24597]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24598]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24599]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24600]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24601]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24602]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24603]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24604]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24605]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24606]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24612]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24624]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24631]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24632]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24633]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24634]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24635]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24636]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24638]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24639]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24641]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24642]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24643]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24644]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24645]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24646]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24647]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24648]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24649]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24650]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24651]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24652]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24653]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24654]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24655]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24656]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24657]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24658]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24659]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24660]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24661]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24662]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24663]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24665]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24667]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24668]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24669]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24670]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24671]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24672]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24673]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24674]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24675]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24676]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24677]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24678]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24679]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24680]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24681]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24682]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24683]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24684]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24685]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24686]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24687]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24688]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24689]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24690]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24691]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24692]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24693]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24694]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24695]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24696]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24713]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24720]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24721]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24722]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24723]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24724]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24725]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24726]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24727]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24728]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24729]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24730]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24731]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24732]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24733]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24734]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24735]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24736]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24737]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24738]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24739]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24740]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24741]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24742]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24743]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24744]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24745]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24746]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24747]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24748]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24749]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24750]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24751]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[24752]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23356]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23483]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23484]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23485]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23486]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23487]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23488]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23489]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23490]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23491]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23523]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23525]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23526]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23527]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23528]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23529]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23530]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23531]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23532]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23533]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23534]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23535]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23536]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23537]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23538]: WARNING: Failed to get value: 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. 
Feb  1 20:19:22 joe gdm-simple-slave[23539]: WARNING: Failed to get value: 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. 
Feb  1 20:19:29 joe acpid: client connected from 25494[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:29 joe acpid: client connected from 25483[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:29 joe acpid: client connected from 25492[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:29 joe acpid: client 25494[0:0] has disconnected
Feb  1 20:19:29 joe acpid: client 25483[0:0] has disconnected
Feb  1 20:19:29 joe acpid: client 25492[0:0] has disconnected
Feb  1 20:19:29 joe acpid: client connected from 25498[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:29 joe acpid: client 25498[0:0] has disconnected
Feb  1 20:19:29 joe acpid: client connected from 25490[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:29 joe acpid: client 25490[0:0] has disconnected
Feb  1 20:19:29 joe acpid: client connected from 25499[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:29 joe acpid: client 25499[0:0] has disconnected
Feb  1 20:19:29 joe acpid: client connected from 25493[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:29 joe acpid: client 25493[0:0] has disconnected
Feb  1 20:19:29 joe acpid: client connected from 25500[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:29 joe acpid: client 25500[0:0] has disconnected
Feb  1 20:19:29 joe acpid: client connected from 25488[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:29 joe acpid: client 25488[0:0] has disconnected
Feb  1 20:19:29 joe acpid: client connected from 25485[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:29 joe acpid: client 25485[0:0] has disconnected
Feb  1 20:19:29 joe acpid: client connected from 25491[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:29 joe acpid: client 25491[0:0] has disconnected
Feb  1 20:19:29 joe acpid: client connected from 25487[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:29 joe acpid: client 25487[0:0] has disconnected
Feb  1 20:19:29 joe acpid: client connected from 25489[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:29 joe acpid: client 25489[0:0] has disconnected
Feb  1 20:19:29 joe acpid: client connected from 25502[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:29 joe acpid: client 25502[0:0] has disconnected
Feb  1 20:19:29 joe acpid: client connected from 25484[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:29 joe acpid: client 25484[0:0] has disconnected
Feb  1 20:19:29 joe acpid: client connected from 25497[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:29 joe acpid: client connected from 25503[0:0]
Feb  1 20:19:29 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe gdm-simple-slave[24681]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24682]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24683]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24684]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24685]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24686]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24687]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24688]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24689]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24690]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24691]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24692]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24693]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24694]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24695]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24724]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24696]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24725]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24713]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24726]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24720]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24727]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24721]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24728]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24722]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24729]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24723]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24730]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24731]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24732]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24733]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24734]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24735]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24736]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24737]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24738]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24739]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24740]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24741]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24742]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24743]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24744]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24745]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24746]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24747]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24748]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24749]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24750]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24751]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe gdm-simple-slave[24752]: WARNING: Failed to get value: 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. 
Feb  1 20:19:50 joe acpid: client 25497[0:0] has disconnected
Feb  1 20:19:50 joe acpid: client 25503[0:0] has disconnected
Feb  1 20:19:50 joe acpid: client connected from 25828[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client 25828[0:0] has disconnected
Feb  1 20:19:50 joe acpid: client connected from 25829[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client 25829[0:0] has disconnected
Feb  1 20:19:50 joe acpid: client connected from 25847[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client 25847[0:0] has disconnected
Feb  1 20:19:50 joe acpid: client connected from 25833[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client 25833[0:0] has disconnected
Feb  1 20:19:50 joe acpid: client connected from 25838[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client 25838[0:0] has disconnected
Feb  1 20:19:50 joe acpid: client connected from 25848[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client 25848[0:0] has disconnected
Feb  1 20:19:50 joe acpid: client connected from 25840[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client 25840[0:0] has disconnected
Feb  1 20:19:50 joe acpid: client connected from 25846[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client 25846[0:0] has disconnected
Feb  1 20:19:50 joe acpid: client connected from 25844[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client 25844[0:0] has disconnected
Feb  1 20:19:50 joe acpid: client connected from 25831[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client 25831[0:0] has disconnected
Feb  1 20:19:50 joe acpid: client connected from 25843[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client 25843[0:0] has disconnected
Feb  1 20:19:50 joe acpid: client connected from 25845[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client connected from 25849[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client connected from 25839[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client connected from 25837[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client connected from 25852[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client connected from 25842[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client connected from 25835[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client connected from 25853[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client connected from 25836[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client connected from 25851[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client connected from 25854[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client connected from 25832[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client connected from 25841[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client connected from 25850[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:50 joe acpid: client connected from 25834[0:0]
Feb  1 20:19:50 joe acpid: 1 client rule loaded
Feb  1 20:19:51 joe gdm-simple-slave[24594]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24595]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24596]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24597]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24598]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24599]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24600]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24601]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24603]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24602]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24604]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24605]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24606]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24612]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24624]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24631]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24632]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24653]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24633]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24652]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24634]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24651]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24635]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24650]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24636]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24649]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24638]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24641]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24645]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24642]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24644]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24643]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24647]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24646]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24648]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24654]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24639]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24655]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24656]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24657]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24675]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24658]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24674]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24659]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24673]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24660]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24672]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24661]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24671]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24662]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24668]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24667]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24663]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24665]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24670]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24669]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24676]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24677]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24678]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24679]: WARNING: Failed to get value: 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. 
Feb  1 20:19:51 joe gdm-simple-slave[24680]: WARNING: Failed to get value: 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. 
Feb  1 20:19:54 joe gdm-simple-slave[25501]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63544: 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. 
Feb  1 20:19:54 joe gdm-simple-slave[25519]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63545: 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. 
Feb  1 20:19:54 joe gdm-simple-slave[25520]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63546: 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. 
Feb  1 20:19:54 joe gdm-simple-slave[25521]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63547: 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. 
Feb  1 20:19:54 joe gdm-simple-slave[25522]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63548: 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. 
Feb  1 20:19:54 joe gdm-simple-slave[25523]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63549: 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. 
Feb  1 20:19:54 joe gdm-simple-slave[25524]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63550: 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. 
Feb  1 20:19:54 joe gdm-simple-slave[25525]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63551: 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. 
Feb  1 20:19:54 joe gdm-simple-slave[25526]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63552: 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. 
Feb  1 20:19:54 joe gdm-simple-slave[25530]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63555: 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. 
Feb  1 20:19:54 joe gdm-simple-slave[25527]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63553: 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. 
Feb  1 20:19:54 joe gdm-simple-slave[25531]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63556: 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. 
Feb  1 20:19:54 joe gdm-simple-slave[25528]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63554: 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. 
Feb  1 20:20:19 joe gdm-simple-slave[25918]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25922]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25923]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25925]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25926]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25929]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25932]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25930]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25924]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25920]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25921]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25928]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25919]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25931]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25532]: WARNING: Failed to get value: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25535]: WARNING: Failed to get value: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25881]: WARNING: Failed to get value: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25882]: WARNING: Failed to get value: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25883]: WARNING: Failed to get value: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25884]: WARNING: Failed to get value: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25886]: WARNING: Failed to get value: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25887]: WARNING: Failed to get value: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25894]: WARNING: Failed to get value: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25897]: WARNING: Failed to get value: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25899]: WARNING: Failed to get value: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25534]: WARNING: Failed to get value: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25533]: WARNING: Failed to get value: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[26228]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63755: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[26226]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63753: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[26229]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63756: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[26227]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63754: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25927]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25898]: WARNING: Failed to get value: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[25896]: WARNING: Failed to get value: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[26230]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63757: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[26231]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63758: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[26232]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63759: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[26233]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63760: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[26234]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63761: 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. 
Feb  1 20:20:20 joe gdm-simple-slave[26235]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63762: 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. 
Feb  1 20:20:21 joe gdm-simple-slave[26236]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63763: 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. 
Feb  1 20:20:21 joe gdm-simple-slave[26237]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63764: 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. 
Feb  1 20:20:21 joe gdm-simple-slave[26238]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63765: 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. 
Feb  1 20:20:21 joe gdm-simple-slave[26239]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63766: 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. 
Feb  1 20:20:21 joe gdm-simple-slave[26240]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63767: 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. 
Feb  1 20:20:21 joe gdm-simple-slave[26241]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63768: 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. 
Feb  1 20:20:21 joe gdm-simple-slave[26242]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63769: 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. 
Feb  1 20:20:21 joe gdm-simple-slave[26243]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63770: 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. 
Feb  1 20:20:21 joe gdm-simple-slave[26245]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63771: 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. 
Feb  1 20:20:23 joe gdm-simple-slave[26246]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63772: 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. 
Feb  1 20:20:23 joe gdm-simple-slave[26251]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63773: 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. 
Feb  1 20:20:23 joe gdm-simple-slave[26252]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63774: 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. 
Feb  1 20:20:23 joe gdm-simple-slave[26253]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63775: 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. 
Feb  1 20:20:23 joe gdm-simple-slave[26254]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63776: 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. 
Feb  1 20:20:23 joe gdm-simple-slave[26258]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63777: 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. 
Feb  1 20:20:23 joe gdm-simple-slave[26259]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63778: 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. 
Feb  1 20:20:23 joe gdm-simple-slave[26260]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63779: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26297]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26299]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26300]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26301]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26303]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26304]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26305]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26306]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26307]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26308]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26309]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26310]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26311]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26312]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26313]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26314]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26315]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26316]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26317]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26318]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26319]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26320]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26322]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26323]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26324]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26325]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26326]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26327]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26328]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26329]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26330]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26332]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26334]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26335]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26336]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26337]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26338]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26339]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26342]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26343]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26345]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26346]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26347]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26348]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26349]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26351]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26353]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26354]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26355]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26358]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26359]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26360]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26361]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26380]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26387]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26388]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26390]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26391]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26392]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26394]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26395]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26396]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26398]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26399]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26400]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26402]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26403]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26407]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26404]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26405]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26406]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26340]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26344]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26397]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26333]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26401]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26393]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26331]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26389]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[25920]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[25918]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[25922]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26261]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26266]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26264]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26265]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26262]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26263]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26267]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26285]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26296]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26294]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26295]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[25925]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26293]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26292]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[25927]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[25932]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[25923]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[25930]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[25926]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26272]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[25929]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[25924]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[25921]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[25928]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[25919]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[25931]: WARNING: Failed to get value: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26647]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63982: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26761]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63998: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26673]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63994: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26760]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63997: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26657]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63987: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26676]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63996: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26665]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63990: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26655]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63985: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26762]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63999: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26643]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63979: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26650]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63983: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26672]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63993: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26662]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63988: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26674]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63995: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26651]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63984: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26656]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63986: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26664]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63989: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26645]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63981: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26763]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64000: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26667]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63992: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26644]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63980: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26764]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64001: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26666]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display63991: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26769]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64002: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26771]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64004: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26778]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64005: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26770]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64003: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26779]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64006: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26781]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64007: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26782]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64008: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26798]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64015: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26783]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64009: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26799]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64016: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26802]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64018: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26801]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64017: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26803]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64019: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26804]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64020: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26805]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64021: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26806]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64022: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26807]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64023: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26808]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64024: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26809]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64025: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26810]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64026: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26811]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64027: 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. 
Feb  1 20:21:08 joe gdm-simple-slave[26812]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64028: 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. 
Feb  1 20:21:16 joe gdm-simple-slave[27162]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:21:16 joe gdm-simple-slave[26297]: WARNING: Failed to get value: 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. 
Feb  1 20:21:17 joe gdm-simple-slave[26299]: WARNING: Failed to get value: 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. 
Feb  1 20:21:17 joe gdm-simple-slave[26300]: WARNING: Failed to get value: 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. 
Feb  1 20:21:17 joe gdm-simple-slave[26301]: WARNING: Failed to get value: 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. 
Feb  1 20:21:17 joe gdm-simple-slave[26303]: WARNING: Failed to get value: 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. 
Feb  1 20:21:25 joe gdm-simple-slave[27523]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:21:30 joe pulseaudio[3668]: [pulseaudio] module-console-kit.c: GetUnixUser() call failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetUnixUser" with signature "" on interface "org.freedesktop.ConsoleKit.Session" doesn't exist
Feb  1 20:21:46 joe gdm-simple-slave[26306]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26322]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26338]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26354]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26402]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26307]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26323]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26339]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26355]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26387]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26403]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26312]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26324]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26388]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[27162]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26404]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26340]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26308]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26328]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26360]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26392]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26344]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26320]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26336]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26400]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26304]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26309]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26325]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26405]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26335]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26351]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26399]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26319]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26310]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26326]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26342]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26358]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26390]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26406]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26318]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26334]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26398]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26359]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26391]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26407]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26311]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26327]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26343]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26349]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26397]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26333]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26317]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26316]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26332]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26348]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26380]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26396]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26361]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26393]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26313]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26329]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26345]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26315]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26395]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26347]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26394]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26331]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26389]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26314]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26330]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26346]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26401]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26353]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26305]: WARNING: Failed to get value: 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. 
Feb  1 20:21:46 joe gdm-simple-slave[26337]: WARNING: Failed to get value: 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. 
Feb  1 20:21:56 joe gdm-simple-slave[27807]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64497: 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. 
Feb  1 20:21:56 joe gdm-simple-slave[27808]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64498: 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. 
Feb  1 20:21:56 joe gdm-simple-slave[27809]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64499: 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. 
Feb  1 20:21:56 joe gdm-simple-slave[27810]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64500: 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. 
Feb  1 20:21:56 joe gdm-simple-slave[27811]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64501: 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. 
Feb  1 20:21:57 joe gdm-simple-slave[27812]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64502: 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. 
Feb  1 20:21:57 joe gdm-simple-slave[27813]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64503: 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. 
Feb  1 20:21:57 joe gdm-simple-slave[27814]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64504: 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. 
Feb  1 20:21:57 joe gdm-simple-slave[27815]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64505: 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. 
Feb  1 20:21:57 joe gdm-simple-slave[27816]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64506: 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. 
Feb  1 20:21:57 joe gdm-simple-slave[27817]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64507: 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. 
Feb  1 20:21:57 joe gdm-simple-slave[27818]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64508: 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. 
Feb  1 20:21:57 joe gdm-simple-slave[27819]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64509: 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. 
Feb  1 20:21:57 joe gdm-simple-slave[27820]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64510: 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. 
Feb  1 20:22:12 joe acpid: client 25845[0:0] has disconnected
Feb  1 20:22:12 joe acpid: client 25849[0:0] has disconnected
Feb  1 20:22:12 joe acpid: client 25839[0:0] has disconnected
Feb  1 20:22:12 joe acpid: client 25837[0:0] has disconnected
Feb  1 20:22:12 joe acpid: client 25852[0:0] has disconnected
Feb  1 20:22:12 joe acpid: client 25842[0:0] has disconnected
Feb  1 20:22:12 joe acpid: client 25835[0:0] has disconnected
Feb  1 20:22:12 joe acpid: client 25853[0:0] has disconnected
Feb  1 20:22:12 joe acpid: client 25836[0:0] has disconnected
Feb  1 20:22:12 joe acpid: client 25851[0:0] has disconnected
Feb  1 20:22:12 joe acpid: client 25854[0:0] has disconnected
Feb  1 20:22:12 joe acpid: client 25832[0:0] has disconnected
Feb  1 20:22:12 joe acpid: client 25841[0:0] has disconnected
Feb  1 20:22:12 joe acpid: client 25850[0:0] has disconnected
Feb  1 20:22:12 joe acpid: client 25834[0:0] has disconnected
Feb  1 20:22:12 joe acpid: client connected from 28585[0:0]
Feb  1 20:22:12 joe acpid: 1 client rule loaded
Feb  1 20:22:12 joe acpid: client connected from 28484[0:0]
Feb  1 20:22:12 joe acpid: 1 client rule loaded
Feb  1 20:22:15 joe gdm-simple-slave[27716]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27717]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27718]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27719]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27720]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27721]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27722]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27723]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27724]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27725]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27730]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27731]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27732]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27733]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27739]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27752]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27753]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27754]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27755]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27756]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27757]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27765]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27766]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27768]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27769]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27748]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27751]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27750]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27749]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27746]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27747]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27745]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27775]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27777]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27774]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27776]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27794]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27783]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27791]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27795]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27797]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27793]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27798]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27789]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27796]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27779]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27790]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27740]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27742]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27744]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27801]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27799]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27806]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27802]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27800]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27805]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27804]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27803]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27735]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27743]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27741]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27738]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27737]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27734]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:15 joe gdm-simple-slave[27736]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:38 joe gdm-simple-slave[28617]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64805: 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. 
Feb  1 20:22:38 joe gdm-simple-slave[28616]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64804: 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. 
Feb  1 20:22:38 joe gdm-simple-slave[28615]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64803: 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. 
Feb  1 20:22:38 joe gdm-simple-slave[28613]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64801: 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. 
Feb  1 20:22:38 joe gdm-simple-slave[28614]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64802: 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. 
Feb  1 20:22:38 joe gdm-simple-slave[28618]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64806: 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. 
Feb  1 20:22:38 joe gdm-simple-slave[28620]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64807: 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. 
Feb  1 20:22:39 joe gdm-simple-slave[28621]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64808: 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. 
Feb  1 20:22:39 joe gdm-simple-slave[28622]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64809: 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. 
Feb  1 20:22:39 joe gdm-simple-slave[28623]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64810: 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. 
Feb  1 20:22:39 joe gdm-simple-slave[28624]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64811: 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. 
Feb  1 20:22:39 joe gdm-simple-slave[28625]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64812: 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. 
Feb  1 20:22:39 joe gdm-simple-slave[28626]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64813: 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. 
Feb  1 20:22:39 joe gdm-simple-slave[28627]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64814: 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. 
Feb  1 20:22:39 joe gdm-simple-slave[28628]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64815: 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. 
Feb  1 20:22:39 joe gdm-simple-slave[28629]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64816: 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. 
Feb  1 20:22:39 joe gdm-simple-slave[28630]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64817: 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. 
Feb  1 20:22:39 joe gdm-simple-slave[28631]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64818: 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. 
Feb  1 20:22:39 joe gdm-simple-slave[28632]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64819: 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. 
Feb  1 20:22:39 joe gdm-simple-slave[28633]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64820: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[28634]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64821: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27717]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27718]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27716]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27719]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27721]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27722]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27720]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27723]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27724]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27725]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27730]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27731]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27732]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27733]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27752]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27739]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27753]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27754]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27755]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27756]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27765]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27766]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27757]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27768]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27769]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27748]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27749]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27746]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27751]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27750]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27747]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27777]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27745]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27774]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27775]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27791]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27783]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27776]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27793]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27789]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27797]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27794]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27790]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27798]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27779]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27795]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27796]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27742]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27801]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27802]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27740]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27799]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27806]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27803]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27744]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27800]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27804]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27805]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27743]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27737]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27741]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27738]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27735]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27736]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[27734]: WARNING: Failed to get value: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[28635]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64822: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[28636]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64823: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[28637]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64824: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[28638]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64825: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[28639]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64826: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[28640]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64827: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[28641]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64828: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[28642]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64829: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[28643]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64830: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[28644]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64831: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[28645]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64832: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[28646]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64833: 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. 
Feb  1 20:22:40 joe gdm-simple-slave[28647]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64834: 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. 
Feb  1 20:22:41 joe gdm-simple-slave[28648]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64835: 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. 
Feb  1 20:22:41 joe gdm-simple-slave[28649]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64836: 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. 
Feb  1 20:22:41 joe gdm-simple-slave[28650]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64837: 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. 
Feb  1 20:22:41 joe gdm-simple-slave[28651]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64838: 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. 
Feb  1 20:22:41 joe gdm-simple-slave[28652]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64839: 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. 
Feb  1 20:22:41 joe gdm-simple-slave[28653]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64840: 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. 
Feb  1 20:22:41 joe gdm-simple-slave[28654]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64841: 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. 
Feb  1 20:22:41 joe gdm-simple-slave[28663]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64842: 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. 
Feb  1 20:22:41 joe gdm-simple-slave[28672]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64843: 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. 
Feb  1 20:22:41 joe gdm-simple-slave[28673]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64844: 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. 
Feb  1 20:22:41 joe gdm-simple-slave[28674]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64845: 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. 
Feb  1 20:22:41 joe gdm-simple-slave[28675]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64846: 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. 
Feb  1 20:22:42 joe gdm-simple-slave[28676]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64847: 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. 
Feb  1 20:22:42 joe gdm-simple-slave[28682]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64848: 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. 
Feb  1 20:22:42 joe gdm-simple-slave[28684]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64849: 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. 
Feb  1 20:22:42 joe gdm-simple-slave[28685]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64850: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28610]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28596]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28593]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28597]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28598]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28599]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28600]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28601]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28602]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28603]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28604]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28606]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28609]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28717]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64853: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28605]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28607]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28611]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28608]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28686]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64851: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28687]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64852: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28718]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64854: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28719]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64855: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28720]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64856: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28721]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64857: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28722]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64858: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28723]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64859: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28725]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64861: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28727]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64863: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28724]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64860: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28734]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64870: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28726]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64862: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28735]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64871: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28728]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64864: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28736]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64872: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28729]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64865: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28730]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64866: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28731]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64867: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28732]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64868: 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. 
Feb  1 20:22:45 joe gdm-simple-slave[28733]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display64869: 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. 
Feb  1 20:23:07 joe gdm-simple-slave[28610]: WARNING: Failed to get value: 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. 
Feb  1 20:23:07 joe gdm-simple-slave[28596]: WARNING: Failed to get value: 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. 
Feb  1 20:23:07 joe gdm-simple-slave[28593]: WARNING: Failed to get value: 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. 
Feb  1 20:23:07 joe gdm-simple-slave[28597]: WARNING: Failed to get value: 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. 
Feb  1 20:23:07 joe gdm-simple-slave[28598]: WARNING: Failed to get value: 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. 
Feb  1 20:23:07 joe gdm-simple-slave[28599]: WARNING: Failed to get value: 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. 
Feb  1 20:23:07 joe gdm-simple-slave[28600]: WARNING: Failed to get value: 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. 
Feb  1 20:23:09 joe gdm-simple-slave[28601]: WARNING: Failed to get value: 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. 
Feb  1 20:23:09 joe gdm-simple-slave[28602]: WARNING: Failed to get value: 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. 
Feb  1 20:23:09 joe gdm-simple-slave[28603]: WARNING: Failed to get value: 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. 
Feb  1 20:23:10 joe gdm-simple-slave[28604]: WARNING: Failed to get value: 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. 
Feb  1 20:23:10 joe gdm-simple-slave[28609]: WARNING: Failed to get value: 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. 
Feb  1 20:23:10 joe gdm-simple-slave[28611]: WARNING: Failed to get value: 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. 
Feb  1 20:23:10 joe gdm-simple-slave[28605]: WARNING: Failed to get value: 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. 
Feb  1 20:23:10 joe gdm-simple-slave[28606]: WARNING: Failed to get value: 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. 
Feb  1 20:23:10 joe gdm-simple-slave[28607]: WARNING: Failed to get value: 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. 
Feb  1 20:23:10 joe gdm-simple-slave[28608]: WARNING: Failed to get value: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29418]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29428]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29427]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29429]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29430]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29431]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29432]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29433]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29434]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29435]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29436]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29437]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29438]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29439]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29441]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29442]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29443]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29444]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29445]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29446]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29447]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29448]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29449]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29450]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29451]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29452]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29453]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29454]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29455]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29456]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29457]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29458]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29459]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29460]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29461]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29462]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29463]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29464]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29465]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29466]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29467]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29468]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29469]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29470]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29471]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29472]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29473]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29474]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29475]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29476]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29477]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29478]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29479]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29480]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29481]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29482]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29483]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29484]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29485]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29486]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29487]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29488]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29489]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29490]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29518]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29497]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29508]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29515]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29516]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29517]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29519]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29521]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29522]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29523]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29524]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29525]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29661]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29664]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29667]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29670]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29673]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29676]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29679]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29682]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29685]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29688]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29691]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29694]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29697]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29707]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29721]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29737]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29738]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29750]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29754]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29751]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29753]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29752]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29755]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29757]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29756]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29834]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29806]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29836]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29833]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29838]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29835]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29840]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29837]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29842]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29839]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29844]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29841]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29843]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29368]: WARNING: Failed to get value: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29369]: WARNING: Failed to get value: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29370]: WARNING: Failed to get value: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29371]: WARNING: Failed to get value: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29372]: WARNING: Failed to get value: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29398]: WARNING: Failed to get value: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29400]: WARNING: Failed to get value: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29401]: WARNING: Failed to get value: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29402]: WARNING: Failed to get value: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29403]: WARNING: Failed to get value: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29404]: WARNING: Failed to get value: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29405]: WARNING: Failed to get value: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29406]: WARNING: Failed to get value: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29409]: WARNING: Failed to get value: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29897]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65293: 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. 
Feb  1 20:23:37 joe gdm-simple-slave[29898]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65294: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29899]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65295: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29900]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65296: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29901]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65297: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29902]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65298: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29903]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65299: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29904]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65300: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29905]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65301: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29906]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65302: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29907]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65303: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29908]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65304: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29909]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65305: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29911]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65307: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29910]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65306: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29914]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65310: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29919]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65315: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29913]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65309: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29915]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65311: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29912]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65308: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29916]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65312: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29917]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65313: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29918]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65314: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29920]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65316: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29921]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65317: 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. 
Feb  1 20:23:39 joe gdm-simple-slave[29924]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display65319: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29477]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29478]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29479]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29480]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29481]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29482]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29483]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29484]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29485]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29486]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29522]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29487]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29521]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29488]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29519]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29489]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29517]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29518]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29516]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29490]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29515]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29497]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29508]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29523]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29524]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29525]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29661]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29664]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29667]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29670]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29676]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29679]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29673]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29682]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29685]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29688]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29691]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29694]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29697]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29707]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29721]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29737]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29738]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29750]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29751]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29753]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29754]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29752]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29755]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29756]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29757]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29806]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29833]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29834]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29835]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29836]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29837]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29838]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29839]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29840]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29841]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29842]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29843]: WARNING: Failed to get value: 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. 
Feb  1 20:24:02 joe gdm-simple-slave[29844]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29418]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29427]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29428]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29429]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29430]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29431]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29432]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29433]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29434]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29435]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29436]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29437]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29438]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29439]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29441]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29442]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29443]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29444]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29445]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29446]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29447]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29448]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29449]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29450]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29451]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29452]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29453]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29454]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29455]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29456]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29457]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29458]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29459]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29460]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29461]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29462]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29463]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29464]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29465]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29466]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29467]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29468]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29469]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29470]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29471]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29472]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29473]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29474]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29475]: WARNING: Failed to get value: 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. 
Feb  1 20:24:07 joe gdm-simple-slave[29476]: WARNING: Failed to get value: 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. 
Feb  1 20:24:10 joe gdm-simple-slave[30891]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:24:41 joe dbus[1463]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Feb  1 20:24:43 joe kernel: [22110.984904] packagekitd[31607]: segfault at 8 ip 0000000008057124 sp 00000000ffe1a130 error 4 in packagekitd[8048000+49000]
Feb  1 20:24:44 joe dbus[1463]: [system] Activated service 'org.freedesktop.PackageKit' failed: Process /usr/lib/dbus-1.0/dbus-daemon-launch-helper received signal 11
Feb  1 20:25:00 joe gdm-simple-slave[30886]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31113]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31114]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31115]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31116]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31126]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31127]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31128]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31135]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31136]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31137]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31138]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31139]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31140]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31141]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31142]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31143]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31144]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31145]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31146]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31148]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31151]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31149]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31152]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31147]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31153]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31154]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31155]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31156]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31157]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31158]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31159]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31160]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31161]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31162]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31163]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31164]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31165]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31166]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31167]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31168]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31169]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31170]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31171]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31172]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31173]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31183]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31185]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31184]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31179]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31181]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31176]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31182]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31180]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31178]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31175]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31177]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31187]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31186]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31191]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31192]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31194]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31193]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31190]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31189]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31188]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31195]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31196]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31197]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31206]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31215]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31222]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31223]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31224]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31225]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31226]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31227]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31228]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31229]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31230]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31231]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31232]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31233]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31234]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31235]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31236]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31237]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31238]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31239]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31240]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31241]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31242]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31243]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31244]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31245]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31246]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31247]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31248]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31249]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31250]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31251]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31252]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31253]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31254]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31255]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31256]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31257]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31258]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31259]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31475]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31476]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31477]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31478]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[31479]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30705]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30716]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30721]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30724]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30677]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30713]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30726]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30731]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30733]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30735]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30737]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30734]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30738]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30739]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30740]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30736]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30741]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30742]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30732]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30758]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30747]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30761]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30757]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30745]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30751]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30746]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30764]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30748]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30785]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30793]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30794]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30795]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30796]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30797]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30805]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30812]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30816]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30823]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30824]: WARNING: Failed to get value: 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. 
Feb  1 20:25:00 joe gdm-simple-slave[30825]: WARNING: Failed to get value: 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. 
Feb  1 20:25:05 joe gdm-simple-slave[32000]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:25:25 joe gdm-simple-slave[31258]: WARNING: Failed to get value: 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. 
Feb  1 20:25:25 joe gdm-simple-slave[31259]: WARNING: Failed to get value: 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. 
Feb  1 20:25:25 joe gdm-simple-slave[31475]: WARNING: Failed to get value: 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. 
Feb  1 20:25:25 joe gdm-simple-slave[31476]: WARNING: Failed to get value: 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. 
Feb  1 20:25:25 joe gdm-simple-slave[31477]: WARNING: Failed to get value: 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. 
Feb  1 20:25:25 joe gdm-simple-slave[31478]: WARNING: Failed to get value: 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. 
Feb  1 20:25:25 joe gdm-simple-slave[31479]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[30886]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31113]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31114]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31115]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31116]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31126]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31127]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31128]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31135]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31136]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31137]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31138]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31139]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31140]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31141]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31142]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31143]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31144]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31145]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31146]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31147]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31148]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31149]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31151]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31152]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31153]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31154]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31155]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31156]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31157]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31158]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31159]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31160]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31161]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31162]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31163]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31164]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31165]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31166]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31167]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31168]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31169]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31170]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31171]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31172]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31173]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31175]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31176]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31177]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31178]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31179]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31180]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31181]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31182]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31183]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31184]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31185]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31186]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31187]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31188]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31189]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31190]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31191]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31192]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31193]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31194]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31196]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31195]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31197]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31206]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31215]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31222]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31223]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31224]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31225]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31226]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31227]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31228]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31229]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31230]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31231]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31232]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31233]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31234]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31235]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31236]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31237]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31238]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31239]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31240]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31241]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31242]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31243]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31244]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31245]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31246]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31247]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31248]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31249]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31250]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31251]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31252]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31253]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31254]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31255]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31256]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31257]: WARNING: Failed to get value: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[31992]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66161: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32043]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66162: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32044]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66163: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32045]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66164: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32046]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66165: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32051]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66170: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32052]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66171: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32050]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66169: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32047]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66166: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32048]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66167: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32049]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66168: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32053]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66172: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32054]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66173: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32055]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66174: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32056]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66175: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32057]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66176: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32058]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66177: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32059]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66178: 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. 
Feb  1 20:25:31 joe gdm-simple-slave[32060]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66179: 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. 
Feb  1 20:25:32 joe gdm-simple-slave[32069]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66184: 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. 
Feb  1 20:25:32 joe gdm-simple-slave[32070]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66185: 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. 
Feb  1 20:25:32 joe gdm-simple-slave[32071]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66186: 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. 
Feb  1 20:25:32 joe gdm-simple-slave[32072]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66187: 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. 
Feb  1 20:25:33 joe gdm-simple-slave[32073]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66188: 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. 
Feb  1 20:25:33 joe gdm-simple-slave[32074]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66189: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[375]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[372]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[374]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[376]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[377]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[378]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[379]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[382]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[380]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[385]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[381]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[383]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[384]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[386]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[387]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[388]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[389]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[392]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[391]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[395]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[394]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[396]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[397]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[398]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[399]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[400]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[390]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[406]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[418]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[425]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[426]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[427]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[428]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[429]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[430]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[431]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[432]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[433]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[434]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[436]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[435]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[438]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[437]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[440]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[439]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[442]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[441]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[444]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[443]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[446]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[448]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[450]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[452]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[454]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[456]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[459]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[461]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[463]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[466]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[468]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[470]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[472]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[474]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[477]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[478]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[476]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[475]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[473]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[471]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[469]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[467]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[465]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[464]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[480]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[447]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[484]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[449]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[486]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[451]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[505]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[453]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[455]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[458]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[460]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[462]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[479]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[481]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[482]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[483]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[485]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[487]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[495]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[514]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[512]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[513]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[445]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[515]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[517]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[519]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[521]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[523]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[525]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[526]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[527]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[528]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[529]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[530]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[532]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[516]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[534]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[518]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[536]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[520]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[538]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[522]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[32389]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[524]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[32390]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[533]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[535]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[531]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[537]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[32357]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[32391]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[32414]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[32416]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[32417]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[32418]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[32419]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[32420]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[32453]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[32454]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[32455]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[32475]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[355]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[353]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[349]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[351]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[356]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[352]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[357]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[350]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[348]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[354]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[32476]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[360]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[363]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[358]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[364]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[362]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[359]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[365]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[361]: WARNING: Failed to get value: 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. 
Feb  1 20:26:23 joe gdm-simple-slave[366]: WARNING: Failed to get value: 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. 
Feb  1 20:26:29 joe gdm-simple-slave[1247]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:26:54 joe gdm-simple-slave[372]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[374]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[375]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[376]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[377]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[378]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[379]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[380]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[381]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[382]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[385]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[383]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[384]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[386]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[387]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[388]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[389]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[390]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[391]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[392]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[394]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[395]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[396]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[418]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[425]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[426]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[427]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[428]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[429]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[430]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[431]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[432]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[433]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[434]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[472]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[440]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[470]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[441]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[468]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[442]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[400]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[466]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[399]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[463]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[398]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[439]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[438]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[436]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[435]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[437]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[406]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[397]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[461]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[474]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[450]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[477]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[452]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[454]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[451]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[453]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[447]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[455]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[449]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[464]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[444]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[448]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[465]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[443]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[467]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[446]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[456]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[473]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[475]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[471]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[476]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[469]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[459]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[478]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[480]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[484]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[486]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[505]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[458]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[460]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[462]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[479]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[481]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[482]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[483]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[485]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[487]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[495]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[512]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[513]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[514]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[445]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[515]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[517]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[519]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[521]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[523]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[525]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[526]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[527]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[528]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[529]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[516]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[518]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[520]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[522]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[524]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[530]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[531]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[532]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[533]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[534]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[535]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[536]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[537]: WARNING: Failed to get value: 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. 
Feb  1 20:26:54 joe gdm-simple-slave[538]: WARNING: Failed to get value: 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. 
Feb  1 20:26:55 joe gdm-simple-slave[1221]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66812: 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. 
Feb  1 20:26:55 joe gdm-simple-slave[1255]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66813: 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. 
Feb  1 20:26:55 joe gdm-simple-slave[1256]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66814: 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. 
Feb  1 20:26:55 joe gdm-simple-slave[1257]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66815: 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. 
Feb  1 20:26:55 joe gdm-simple-slave[1258]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66816: 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. 
Feb  1 20:26:55 joe gdm-simple-slave[1259]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66817: 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. 
Feb  1 20:26:55 joe gdm-simple-slave[1260]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66818: 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. 
Feb  1 20:26:55 joe gdm-simple-slave[1261]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66819: 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. 
Feb  1 20:26:55 joe gdm-simple-slave[1262]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66820: 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. 
Feb  1 20:26:55 joe gdm-simple-slave[1263]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66821: 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. 
Feb  1 20:26:55 joe gdm-simple-slave[1264]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66822: 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. 
Feb  1 20:26:55 joe gdm-simple-slave[1265]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66823: 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. 
Feb  1 20:26:55 joe gdm-simple-slave[1266]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66824: 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. 
Feb  1 20:26:56 joe gdm-simple-slave[1267]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66825: 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. 
Feb  1 20:26:59 joe gdm-simple-slave[1290]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66832: 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. 
Feb  1 20:26:59 joe gdm-simple-slave[1291]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display66833: 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. 
Feb  1 20:26:59 joe gdm-simple-slave[2012]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:27:47 joe gdm-simple-slave[2079]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2100]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2080]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2083]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2081]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2082]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2124]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2123]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2122]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2120]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2119]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2118]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2117]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2116]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2115]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2107]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2108]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2110]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2111]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2112]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2113]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2114]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2125]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2126]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2127]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2128]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2129]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2130]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2131]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2132]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2133]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2134]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2135]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2136]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2137]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2138]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2139]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2142]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2143]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2144]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2145]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2146]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2147]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2148]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2149]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2151]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2152]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2153]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2154]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2155]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2157]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2158]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2159]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2160]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2161]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2162]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2163]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2164]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2165]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2166]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2167]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2170]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2171]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2172]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2173]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2174]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2175]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2176]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2178]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2196]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2203]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2204]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2205]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2206]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2207]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2208]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2209]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2211]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2212]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2213]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2214]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2215]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2216]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2217]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2218]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2219]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2221]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2223]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2225]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2227]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2228]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2229]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2230]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2231]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2246]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2248]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2249]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2250]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2251]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2252]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1619]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1621]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1622]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1623]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1624]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1631]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1629]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1630]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1620]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1625]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1628]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1627]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2247]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2244]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1618]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1626]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2245]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1632]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1643]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1644]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[1645]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2041]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2042]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2043]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2044]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2045]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2046]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2047]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2048]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2049]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2050]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2051]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2052]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2053]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2077]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2066]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2076]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2067]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2075]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2068]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2074]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2069]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2073]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2057]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2059]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2072]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2071]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2058]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2056]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2070]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2055]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2065]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2062]: WARNING: Failed to get value: 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. 
Feb  1 20:27:47 joe gdm-simple-slave[2054]: WARNING: Failed to get value: 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. 
Feb  1 20:28:12 joe gdm-simple-slave[2229]: WARNING: Failed to get value: 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. 
Feb  1 20:28:12 joe gdm-simple-slave[2230]: WARNING: Failed to get value: 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. 
Feb  1 20:28:12 joe gdm-simple-slave[2231]: WARNING: Failed to get value: 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. 
Feb  1 20:28:12 joe gdm-simple-slave[2246]: WARNING: Failed to get value: 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. 
Feb  1 20:28:12 joe gdm-simple-slave[2248]: WARNING: Failed to get value: 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. 
Feb  1 20:28:12 joe gdm-simple-slave[2250]: WARNING: Failed to get value: 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. 
Feb  1 20:28:12 joe gdm-simple-slave[2249]: WARNING: Failed to get value: 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. 
Feb  1 20:28:12 joe gdm-simple-slave[2251]: WARNING: Failed to get value: 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. 
Feb  1 20:28:12 joe gdm-simple-slave[2252]: WARNING: Failed to get value: 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. 
Feb  1 20:28:12 joe gdm-simple-slave[2247]: WARNING: Failed to get value: 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. 
Feb  1 20:28:13 joe gdm-simple-slave[2244]: WARNING: Failed to get value: 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. 
Feb  1 20:28:13 joe gdm-simple-slave[2245]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2079]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2080]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2082]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2081]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2083]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2123]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2100]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2122]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2115]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2120]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2116]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2119]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2118]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2117]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2124]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2107]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2108]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2110]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2111]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2112]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2113]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2114]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2125]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2126]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2127]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2134]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2133]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2135]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2136]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2153]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2137]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2152]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2138]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2151]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2139]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2149]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2148]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2128]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2147]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2130]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2146]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2131]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2129]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2145]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2144]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2143]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2142]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2132]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2154]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2155]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2174]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2157]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2173]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2158]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2172]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2159]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2171]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2160]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2170]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2161]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2165]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2164]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2167]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2163]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2162]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2166]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2175]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2176]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2178]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2196]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2203]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2204]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2205]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2206]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2207]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2208]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2209]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2211]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2212]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2213]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2214]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2215]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2216]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2217]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2218]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2219]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2221]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2223]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2225]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2227]: WARNING: Failed to get value: 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. 
Feb  1 20:28:19 joe gdm-simple-slave[2228]: WARNING: Failed to get value: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3294]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3400]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3401]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3402]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3403]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3404]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3405]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3406]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3407]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3408]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3409]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3434]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3437]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3438]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3439]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3443]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3440]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3444]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3445]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3446]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3447]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3448]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3449]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3450]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3451]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3452]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3453]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3454]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3455]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3456]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3457]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3458]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3459]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3460]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3461]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3465]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3466]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3467]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3468]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3469]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3470]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3471]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3472]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3473]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3474]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3475]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3476]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3477]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3478]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3479]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:47 joe gdm-simple-slave[3480]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:28:48 joe gdm-simple-slave[3806]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display67680: 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. 
Feb  1 20:28:48 joe gdm-simple-slave[3809]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display67682: 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. 
Feb  1 20:28:48 joe gdm-simple-slave[3807]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display67681: 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. 
Feb  1 20:28:48 joe gdm-simple-slave[3810]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display67683: 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. 
Feb  1 20:28:48 joe gdm-simple-slave[3811]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display67684: 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. 
Feb  1 20:28:48 joe gdm-simple-slave[3812]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display67685: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3813]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3814]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3815]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3816]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3817]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3818]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3819]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3820]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3821]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3822]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3823]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3824]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3825]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3826]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3827]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3828]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3831]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3832]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3833]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3835]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3837]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3839]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3840]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3841]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3842]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3845]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3856]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3867]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3868]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3869]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3870]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3871]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3872]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3873]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3874]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3875]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3876]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3877]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3878]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3879]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3880]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3881]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3882]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3883]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3884]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3885]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3886]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3887]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3888]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3889]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3890]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3891]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3892]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3893]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3894]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3895]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3896]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3897]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3898]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3899]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3900]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3901]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3902]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3903]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3904]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3905]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3906]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3907]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3951]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3908]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3937]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3909]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3929]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3910]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3928]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3911]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3927]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3912]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3959]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3960]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3921]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3925]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3915]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3961]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3923]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3924]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3916]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3962]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3922]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3920]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3294]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3400]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3958]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3919]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3918]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3401]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3914]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3926]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3917]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3402]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3913]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3403]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3404]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3405]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3406]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3407]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3408]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3409]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3434]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3437]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3438]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3439]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3440]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3443]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3444]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3445]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3446]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3447]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3448]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3449]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3450]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3451]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3452]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3453]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3454]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3455]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3456]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3457]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3458]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3459]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3460]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3461]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3465]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3466]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3467]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3468]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3469]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3470]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3471]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3472]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3473]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3474]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3475]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3476]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3477]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3478]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3479]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[3480]: WARNING: Failed to get value: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[4237]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display67897: 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. 
Feb  1 20:29:13 joe gdm-simple-slave[4250]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display67898: 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. 
Feb  1 20:29:15 joe gdm-simple-slave[4277]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display67912: 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. 
Feb  1 20:29:15 joe gdm-simple-slave[4278]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display67913: 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. 
Feb  1 20:29:15 joe gdm-simple-slave[4279]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display67914: 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. 
Feb  1 20:29:15 joe gdm-simple-slave[4280]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display67915: 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. 
Feb  1 20:29:19 joe gdm-simple-slave[4771]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:29:44 joe gdm-simple-slave[3813]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3814]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3815]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3816]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3817]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3818]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3819]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3820]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3821]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3822]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3823]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3825]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3827]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3824]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3831]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3826]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3833]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3828]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3837]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3832]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3835]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3841]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3840]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3839]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3856]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3868]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3867]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3871]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3869]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3913]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3908]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3916]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3909]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3918]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3910]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3920]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3925]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3927]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3877]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3929]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3878]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3879]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3951]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3883]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3959]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3880]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3960]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3895]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3885]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3886]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3887]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3888]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3889]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3892]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3961]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3891]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3890]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3962]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3906]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3898]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3893]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3899]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3904]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3901]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3900]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3905]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3902]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3903]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3911]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3912]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3922]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3914]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3924]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3915]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3926]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3917]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3928]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3919]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3921]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3937]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3923]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3958]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3842]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3870]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3872]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3873]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3874]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3875]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3845]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3881]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3882]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3884]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3876]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3896]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3894]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3907]: WARNING: Failed to get value: 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. 
Feb  1 20:29:44 joe gdm-simple-slave[3897]: WARNING: Failed to get value: 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. 
Feb  1 20:29:45 joe gdm-simple-slave[4793]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68114: 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. 
Feb  1 20:29:45 joe gdm-simple-slave[4794]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68115: 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. 
Feb  1 20:29:45 joe gdm-simple-slave[4795]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68116: 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. 
Feb  1 20:29:45 joe gdm-simple-slave[4796]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68117: 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. 
Feb  1 20:29:45 joe gdm-simple-slave[4797]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68118: 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. 
Feb  1 20:29:45 joe gdm-simple-slave[4798]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68119: 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. 
Feb  1 20:29:45 joe gdm-simple-slave[4799]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68120: 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. 
Feb  1 20:29:45 joe gdm-simple-slave[4800]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68121: 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. 
Feb  1 20:29:45 joe gdm-simple-slave[4801]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68122: 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. 
Feb  1 20:29:45 joe gdm-simple-slave[4802]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68123: 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. 
Feb  1 20:29:45 joe gdm-simple-slave[4803]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68124: 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. 
Feb  1 20:29:45 joe gdm-simple-slave[4804]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68125: 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. 
Feb  1 20:29:46 joe gdm-simple-slave[4805]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68126: 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. 
Feb  1 20:29:46 joe gdm-simple-slave[4806]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68127: 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. 
Feb  1 20:29:46 joe gdm-simple-slave[4807]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68128: 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. 
Feb  1 20:29:46 joe gdm-simple-slave[4808]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68129: 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. 
Feb  1 20:29:46 joe gdm-simple-slave[4809]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68130: 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. 
Feb  1 20:29:46 joe gdm-simple-slave[4810]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68131: 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. 
Feb  1 20:29:46 joe gdm-simple-slave[4811]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68132: 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. 
Feb  1 20:29:46 joe gdm-simple-slave[4812]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68133: 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. 
Feb  1 20:29:46 joe gdm-simple-slave[4813]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68134: 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. 
Feb  1 20:29:46 joe gdm-simple-slave[4815]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68135: 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. 
Feb  1 20:29:46 joe gdm-simple-slave[4816]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68136: 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. 
Feb  1 20:29:46 joe gdm-simple-slave[4817]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68137: 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. 
Feb  1 20:29:47 joe gdm-simple-slave[4818]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68138: 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. 
Feb  1 20:29:47 joe gdm-simple-slave[4819]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68139: 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. 
Feb  1 20:29:47 joe gdm-simple-slave[4820]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68140: 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. 
Feb  1 20:29:47 joe gdm-simple-slave[4821]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68141: 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. 
Feb  1 20:29:47 joe gdm-simple-slave[4822]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68142: 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. 
Feb  1 20:29:47 joe gdm-simple-slave[4823]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68143: 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. 
Feb  1 20:29:47 joe gdm-simple-slave[4824]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68144: 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. 
Feb  1 20:29:47 joe gdm-simple-slave[4825]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68145: 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. 
Feb  1 20:29:47 joe gdm-simple-slave[4826]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68146: 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. 
Feb  1 20:29:47 joe gdm-simple-slave[4827]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68147: 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. 
Feb  1 20:29:48 joe gdm-simple-slave[5275]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:30:14 joe acpid: client 28585[0:0] has disconnected
Feb  1 20:30:14 joe acpid: client 28484[0:0] has disconnected
Feb  1 20:30:38 joe gdm-simple-slave[5609]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5611]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5613]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5615]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5616]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5614]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5612]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5621]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5643]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5646]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5648]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5650]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5652]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5654]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5656]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5663]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5665]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5667]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5670]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5672]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5661]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5659]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5610]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5626]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5641]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5642]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5644]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5645]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5647]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5649]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5651]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5653]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5655]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5657]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5658]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5660]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5662]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5664]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5666]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5668]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5671]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5673]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5675]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5674]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5677]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5676]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5678]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5679]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5681]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5680]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5683]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5682]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5684]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5689]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5687]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5688]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5686]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5685]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5690]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5691]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5692]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5693]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5694]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5695]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5696]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5697]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5698]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5699]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5700]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5701]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5710]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5702]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5720]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5727]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5728]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5729]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5730]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5731]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5119]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5732]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5122]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5123]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5124]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5125]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5126]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5127]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5128]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5147]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5152]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5155]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5131]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5132]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5157]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5159]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5160]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5162]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5161]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5183]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5182]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5557]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5558]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5559]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5563]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5549]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5561]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5574]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5562]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5577]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5564]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5560]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5539]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5566]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5145]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5569]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5565]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5537]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5129]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5571]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5538]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5573]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5575]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5576]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5556]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5579]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5578]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5582]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5580]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5584]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5581]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5583]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5585]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5130]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5587]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5586]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5589]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5588]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5591]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5590]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5594]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5592]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5595]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5596]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5597]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5599]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5608]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5607]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5601]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5606]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5603]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5604]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5605]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5602]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5600]: WARNING: Failed to get value: 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. 
Feb  1 20:30:38 joe gdm-simple-slave[5598]: WARNING: Failed to get value: 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. 
Feb  1 20:30:45 joe gdm-simple-slave[6418]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:31:03 joe gdm-simple-slave[5731]: WARNING: Failed to get value: 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. 
Feb  1 20:31:03 joe gdm-simple-slave[5730]: WARNING: Failed to get value: 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. 
Feb  1 20:31:03 joe gdm-simple-slave[5732]: WARNING: Failed to get value: 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. 
Feb  1 20:31:03 joe gdm-simple-slave[6784]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:31:10 joe gdm-simple-slave[5609]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5611]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5613]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5615]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5612]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5614]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5616]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5621]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5643]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5646]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5648]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5650]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5652]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5654]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5656]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5659]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5661]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5663]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5665]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5667]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5670]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5672]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5610]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5626]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5641]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5642]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5644]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5645]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5647]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5649]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5651]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5653]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5655]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5657]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5658]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5660]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5662]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5664]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5666]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5668]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5671]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5673]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5674]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5675]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5676]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5677]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5678]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5679]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5680]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5681]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5682]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5683]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5684]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5687]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5689]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5685]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5701]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5686]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5702]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5688]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5710]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5690]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5720]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5691]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5727]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5692]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5693]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5728]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5729]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5694]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5700]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5697]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5696]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5699]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5698]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[5695]: WARNING: Failed to get value: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[6447]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68765: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[6448]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68766: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[6449]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68767: 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. 
Feb  1 20:31:10 joe gdm-simple-slave[6450]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68768: 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. 
Feb  1 20:31:11 joe gdm-simple-slave[6451]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68769: 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. 
Feb  1 20:31:11 joe gdm-simple-slave[6452]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68770: 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. 
Feb  1 20:31:11 joe gdm-simple-slave[6453]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68771: 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. 
Feb  1 20:31:11 joe gdm-simple-slave[6454]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68772: 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. 
Feb  1 20:31:11 joe gdm-simple-slave[6455]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68773: 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. 
Feb  1 20:31:11 joe gdm-simple-slave[6456]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68774: 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. 
Feb  1 20:31:11 joe gdm-simple-slave[6457]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68775: 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. 
Feb  1 20:31:11 joe gdm-simple-slave[6458]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68776: 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. 
Feb  1 20:31:12 joe gdm-simple-slave[6484]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68784: 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. 
Feb  1 20:31:12 joe gdm-simple-slave[6485]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68785: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6486]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6487]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6488]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6489]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6490]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6745]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6859]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6860]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6861]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6862]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6863]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6864]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6865]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6866]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6867]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6868]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6869]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6870]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6871]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6872]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6873]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6874]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6875]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6877]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6876]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6878]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6880]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6881]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6883]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6879]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6884]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6885]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6886]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6887]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6888]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6889]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6890]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6891]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6892]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6898]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6905]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6914]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6923]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6924]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6925]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6926]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6927]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6928]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6896]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6897]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6895]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6894]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6893]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6929]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6930]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6931]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6932]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6933]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6934]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6935]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:37 joe gdm-simple-slave[6936]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:31:40 joe gdm-simple-slave[7186]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68986: 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. 
Feb  1 20:31:40 joe gdm-simple-slave[7187]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68987: 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. 
Feb  1 20:31:40 joe gdm-simple-slave[7188]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68988: 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. 
Feb  1 20:31:40 joe gdm-simple-slave[7189]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68989: 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. 
Feb  1 20:31:40 joe gdm-simple-slave[7190]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68990: 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. 
Feb  1 20:31:40 joe gdm-simple-slave[7191]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68991: 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. 
Feb  1 20:31:40 joe gdm-simple-slave[7192]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display68992: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7203]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7204]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7205]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7206]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7207]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7208]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7209]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7210]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7211]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7212]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7213]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7215]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7217]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7219]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7221]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7214]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7223]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7224]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7216]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7226]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7218]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7227]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7220]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7222]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7225]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7228]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7253]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7255]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7257]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7258]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7260]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7236]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7261]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7242]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7254]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7263]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7256]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7264]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7259]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7262]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7265]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7270]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7269]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7268]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7267]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7266]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7280]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7271]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7279]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7272]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7278]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7273]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7277]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7276]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7275]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7274]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7290]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7281]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7289]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7282]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7288]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7283]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7287]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7284]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7286]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7291]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7285]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7292]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7295]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7293]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7294]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7296]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7297]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7298]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7299]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7300]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7301]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6486]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6487]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6488]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6489]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6490]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6745]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6859]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6860]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6861]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6862]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6863]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6864]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6865]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6866]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6867]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6868]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6869]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6870]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6871]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6872]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6873]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6874]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6875]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6876]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6877]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6878]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6879]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6880]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6881]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6883]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6884]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6885]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6886]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6887]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6888]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6889]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6890]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6891]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6892]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6893]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6894]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6895]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6896]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6897]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6898]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6905]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6914]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6923]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6924]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6925]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6926]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6927]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6928]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6929]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6930]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6931]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6932]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6933]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6934]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6935]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[6936]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7193]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7194]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7195]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7197]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7198]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7199]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7200]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7201]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7202]: WARNING: Failed to get value: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7579]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69199: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7592]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69200: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7593]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69201: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7594]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69202: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7595]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69203: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7596]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69204: 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. 
Feb  1 20:32:08 joe gdm-simple-slave[7597]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69205: 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. 
Feb  1 20:32:33 joe gdm-simple-slave[8436]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:32:36 joe gdm-simple-slave[7203]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7204]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7205]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7206]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7207]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7208]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7209]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7210]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7211]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7212]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7213]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7214]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7220]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7219]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7221]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7226]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7217]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7223]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7224]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7218]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7222]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7216]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7227]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7215]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7228]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7236]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7225]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7242]: WARNING: Failed to get value: 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. 
Feb  1 20:32:36 joe gdm-simple-slave[7253]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7254]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7255]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7256]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7257]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7258]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7259]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7260]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7261]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7262]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7263]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7264]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7265]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7266]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7267]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7268]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7269]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7270]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7271]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7272]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7273]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7274]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7275]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7276]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7277]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7278]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7279]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7280]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7281]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7282]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7283]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7284]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7285]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7286]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7287]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7288]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7289]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7290]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7291]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7292]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7293]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7294]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7295]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7296]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7297]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7298]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7299]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7300]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[7301]: WARNING: Failed to get value: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[8089]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69416: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[8090]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69417: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[8091]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69418: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[8092]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69419: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[8093]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69420: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[8094]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69421: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[8095]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69422: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[8096]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69423: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[8097]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69424: 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. 
Feb  1 20:32:37 joe gdm-simple-slave[8098]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69425: 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. 
Feb  1 20:32:40 joe gdm-simple-slave[8662]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:32:40 joe gdm-simple-slave[8722]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:33:01 joe /USR/SBIN/CRON[9144]: (Debian-exim) CMD ([ -x /usr/share/sa-exim/greylistclean ] && /usr/share/sa-exim/greylistclean)
Feb  1 20:33:03 joe sa-exim[9149]: Removed 0 of 0 greylist tuplets in 1 seconds 
Feb  1 20:33:03 joe sa-exim[9149]: Removed 0 of 0 greylist directories in 0 seconds 
Feb  1 20:33:05 joe gdm-simple-slave[8542]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8541]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8543]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8544]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8545]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8546]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8548]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8551]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8547]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8549]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8550]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8552]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8553]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8554]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8555]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8556]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8557]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8558]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8559]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8560]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8561]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8562]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8563]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8564]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8568]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8570]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8585]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8586]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8569]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8566]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8577]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8567]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8587]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8588]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8589]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8602]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8593]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8604]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8600]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8601]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8603]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8605]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8606]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8607]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8608]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8609]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8610]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8611]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8612]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8613]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8614]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8622]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8615]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8616]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8624]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8617]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8627]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8618]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8619]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8621]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8623]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8625]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8626]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8628]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8629]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8620]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:05 joe gdm-simple-slave[8630]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:06 joe gdm-simple-slave[8818]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69633: 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. 
Feb  1 20:33:06 joe gdm-simple-slave[8819]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69634: 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. 
Feb  1 20:33:06 joe gdm-simple-slave[8820]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69635: 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. 
Feb  1 20:33:06 joe gdm-simple-slave[8821]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69636: 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. 
Feb  1 20:33:06 joe gdm-simple-slave[8822]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69637: 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. 
Feb  1 20:33:06 joe gdm-simple-slave[8823]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69638: 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. 
Feb  1 20:33:06 joe gdm-simple-slave[8824]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69639: 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. 
Feb  1 20:33:06 joe gdm-simple-slave[8829]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69640: 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. 
Feb  1 20:33:06 joe gdm-simple-slave[8842]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69641: 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. 
Feb  1 20:33:06 joe gdm-simple-slave[8849]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69642: 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. 
Feb  1 20:33:06 joe gdm-simple-slave[8850]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69643: 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. 
Feb  1 20:33:06 joe gdm-simple-slave[8851]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69644: 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. 
Feb  1 20:33:06 joe gdm-simple-slave[8852]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69645: 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. 
Feb  1 20:33:07 joe gdm-simple-slave[8853]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69646: 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. 
Feb  1 20:33:08 joe gdm-simple-slave[8854]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69647: 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. 
Feb  1 20:33:09 joe gdm-simple-slave[8855]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69648: 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. 
Feb  1 20:33:09 joe gdm-simple-slave[8856]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69649: 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. 
Feb  1 20:33:09 joe gdm-simple-slave[8857]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69650: 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. 
Feb  1 20:33:09 joe gdm-simple-slave[8858]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69651: 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. 
Feb  1 20:33:09 joe gdm-simple-slave[8859]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69652: 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. 
Feb  1 20:33:09 joe gdm-simple-slave[8860]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69653: 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. 
Feb  1 20:33:09 joe gdm-simple-slave[8862]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69654: 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. 
Feb  1 20:33:09 joe gdm-simple-slave[8863]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69655: 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. 
Feb  1 20:33:09 joe gdm-simple-slave[8864]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69656: 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. 
Feb  1 20:33:09 joe gdm-simple-slave[8865]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69657: 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. 
Feb  1 20:33:09 joe gdm-simple-slave[8866]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69658: 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. 
Feb  1 20:33:09 joe gdm-simple-slave[8867]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69659: 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. 
Feb  1 20:33:09 joe gdm-simple-slave[8868]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69660: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8947]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8893]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8904]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8925]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8886]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8542]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8932]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8600]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8567]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8560]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8561]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8898]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8589]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8622]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8602]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8563]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8541]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8543]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8562]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8550]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8890]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8617]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8554]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8869]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8908]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8553]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8551]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8604]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8548]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8546]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8616]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8552]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8618]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8569]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8887]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8577]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8606]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8896]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8630]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8623]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8938]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8892]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8934]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8945]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8614]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8615]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8943]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8888]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8891]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8882]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8871]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8889]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8613]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8937]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8601]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8626]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8936]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8593]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8906]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8940]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8941]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8944]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8629]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8876]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8627]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8568]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8608]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8895]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8948]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8899]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8588]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8907]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8619]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8872]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8946]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8883]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8586]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8625]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8587]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8570]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8873]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8610]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8949]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8878]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8884]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8900]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8621]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8612]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8903]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8875]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8902]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8870]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8874]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8897]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8880]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8885]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8881]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8905]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8942]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8609]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8558]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8545]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8547]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8556]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8939]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8559]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8611]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8605]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8564]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8585]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8877]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8624]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8557]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8566]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8620]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8607]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8603]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8549]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8933]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8628]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8935]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8901]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8879]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8555]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8544]: WARNING: Failed to get value: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[8894]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9267]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69850: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9297]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69851: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9298]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69852: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9299]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69853: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9300]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69854: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9301]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69855: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9302]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69856: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9303]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69857: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9304]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69858: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9305]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69859: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9306]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69860: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9307]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69861: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9308]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69862: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9309]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69863: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9310]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69864: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9311]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69865: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9312]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69866: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9313]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69867: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9314]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69868: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9321]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69872: 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. 
Feb  1 20:33:35 joe gdm-simple-slave[9322]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display69873: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8898]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8890]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8869]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8908]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8871]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8887]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8896]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8938]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8945]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8934]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8892]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8943]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8888]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8937]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8882]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8870]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8889]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8891]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8906]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8941]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8936]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8944]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8940]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8876]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8895]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8899]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8948]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8907]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8883]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8946]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8872]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8873]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8884]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8900]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8949]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8878]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8902]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8903]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8875]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8881]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8897]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8905]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8885]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8942]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8874]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8880]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8939]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8877]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8901]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8879]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8933]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8935]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[8894]: WARNING: Failed to get value: 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. 
Feb  1 20:34:00 joe gdm-simple-slave[10200]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:34:05 joe gdm-simple-slave[8893]: WARNING: Failed to get value: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[8947]: WARNING: Failed to get value: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[8904]: WARNING: Failed to get value: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[8925]: WARNING: Failed to get value: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[8932]: WARNING: Failed to get value: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[8886]: WARNING: Failed to get value: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9676]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9858]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70072: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9694]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9695]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9696]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9697]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9698]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9854]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70068: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9853]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70067: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9857]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70071: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9689]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9855]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70069: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9859]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70073: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9856]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70070: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9861]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70075: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9860]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70074: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9863]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70077: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9862]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70076: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9864]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70078: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9865]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70079: 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. 
Feb  1 20:34:05 joe gdm-simple-slave[9866]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70080: 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. 
Feb  1 20:34:06 joe gdm-simple-slave[9867]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70081: 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. 
Feb  1 20:34:06 joe gdm-simple-slave[9868]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70082: 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. 
Feb  1 20:34:06 joe gdm-simple-slave[9869]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70083: 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. 
Feb  1 20:34:06 joe gdm-simple-slave[9870]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70084: 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. 
Feb  1 20:34:06 joe gdm-simple-slave[9871]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70085: 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. 
Feb  1 20:34:06 joe gdm-simple-slave[9872]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70086: 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. 
Feb  1 20:34:06 joe gdm-simple-slave[9873]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70087: 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. 
Feb  1 20:34:06 joe gdm-simple-slave[9874]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70088: 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. 
Feb  1 20:34:06 joe gdm-simple-slave[9875]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70089: 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. 
Feb  1 20:34:06 joe gdm-simple-slave[9876]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70090: 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. 
Feb  1 20:34:06 joe gdm-simple-slave[9877]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70091: 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. 
Feb  1 20:34:07 joe gdm-simple-slave[10419]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:34:15 joe pulseaudio[3668]: [pulseaudio] module-console-kit.c: GetUnixUser() call failed: org.freedesktop.DBus.Error.UnknownMethod: Method "GetUnixUser" with signature "" on interface "org.freedesktop.ConsoleKit.Session" doesn't exist
Feb  1 20:34:31 joe gdm-simple-slave[9880]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:31 joe gdm-simple-slave[9881]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:31 joe gdm-simple-slave[9882]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:31 joe gdm-simple-slave[9883]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:31 joe gdm-simple-slave[9886]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:31 joe gdm-simple-slave[9884]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:31 joe gdm-simple-slave[9885]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:31 joe gdm-simple-slave[9887]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:31 joe gdm-simple-slave[9888]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:31 joe gdm-simple-slave[9889]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:31 joe gdm-simple-slave[9910]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:31 joe gdm-simple-slave[9911]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:31 joe gdm-simple-slave[9912]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10262]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10263]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10264]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10265]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10266]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10267]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10268]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10269]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10270]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10271]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10272]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10273]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10274]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10275]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10276]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10277]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10278]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10279]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10280]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10281]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10284]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10282]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10286]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10283]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10289]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10285]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10288]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10290]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10291]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10292]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10293]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10294]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10295]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10296]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10297]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10298]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10299]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10300]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10309]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10310]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10311]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10320]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10327]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10328]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10329]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10330]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10331]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10332]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[9676]: WARNING: Failed to get value: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[9694]: WARNING: Failed to get value: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[9695]: WARNING: Failed to get value: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[9696]: WARNING: Failed to get value: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[9689]: WARNING: Failed to get value: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[9697]: WARNING: Failed to get value: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[9698]: WARNING: Failed to get value: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[9878]: WARNING: Failed to get value: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[9879]: WARNING: Failed to get value: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10527]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70284: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10528]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70285: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10529]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70286: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10530]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70287: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10531]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70288: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10532]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70289: 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. 
Feb  1 20:34:32 joe gdm-simple-slave[10533]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70290: 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. 
Feb  1 20:34:33 joe gdm-simple-slave[10534]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70291: 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. 
Feb  1 20:34:33 joe gdm-simple-slave[10535]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70292: 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. 
Feb  1 20:34:33 joe gdm-simple-slave[10536]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70293: 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. 
Feb  1 20:34:33 joe gdm-simple-slave[10537]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70294: 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. 
Feb  1 20:34:33 joe gdm-simple-slave[10538]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70295: 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. 
Feb  1 20:34:33 joe gdm-simple-slave[10539]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70296: 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. 
Feb  1 20:34:33 joe gdm-simple-slave[10540]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70297: 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. 
Feb  1 20:34:33 joe gdm-simple-slave[10541]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70298: 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. 
Feb  1 20:34:33 joe gdm-simple-slave[10542]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70299: 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. 
Feb  1 20:34:33 joe gdm-simple-slave[10543]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70300: 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. 
Feb  1 20:34:33 joe gdm-simple-slave[10544]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70301: 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. 
Feb  1 20:34:34 joe gdm-simple-slave[10545]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70302: 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. 
Feb  1 20:34:34 joe gdm-simple-slave[10554]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70303: 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. 
Feb  1 20:34:34 joe gdm-simple-slave[10566]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70304: 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. 
Feb  1 20:34:34 joe gdm-simple-slave[10573]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70305: 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. 
Feb  1 20:34:34 joe gdm-simple-slave[10574]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70306: 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. 
Feb  1 20:34:34 joe gdm-simple-slave[10575]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70307: 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. 
Feb  1 20:34:34 joe gdm-simple-slave[10576]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70308: 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. 
Feb  1 20:34:34 joe gdm-simple-slave[10577]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70309: 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. 
Feb  1 20:34:35 joe gdm-simple-slave[10578]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70310: 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. 
Feb  1 20:34:36 joe gdm-simple-slave[10579]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70311: 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. 
Feb  1 20:34:36 joe gdm-simple-slave[10580]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70312: 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. 
Feb  1 20:34:36 joe gdm-simple-slave[10581]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70313: 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. 
Feb  1 20:34:36 joe gdm-simple-slave[10582]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70314: 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. 
Feb  1 20:34:36 joe gdm-simple-slave[11008]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:35:00 joe gdm-simple-slave[10583]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10585]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10584]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10586]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10587]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10588]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10589]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10590]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10591]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10592]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10593]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10594]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10595]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10596]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10597]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10598]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10599]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10600]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10601]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10602]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10603]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10604]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10605]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10606]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10607]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10608]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10609]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10610]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10611]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10612]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10613]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10614]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10615]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10616]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10617]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10618]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10619]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10621]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10622]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10623]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10624]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10625]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10626]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10627]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10628]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10629]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10630]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10631]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10632]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10633]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10650]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10657]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10658]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[9880]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[9881]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[9882]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[9883]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[9884]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[9886]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[9885]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[9887]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[9888]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[9889]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[9910]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[9911]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[9912]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10262]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10263]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10264]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10265]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10266]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10267]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10268]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10269]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10270]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10271]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10272]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10273]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10274]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10275]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10276]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10277]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10278]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10279]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10280]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10281]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10282]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10283]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10284]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10285]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10286]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10289]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10288]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10290]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10291]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10292]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10293]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10294]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10295]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10296]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10297]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10298]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10299]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10300]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10309]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10310]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10311]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10320]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10327]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10328]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10329]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10330]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10331]: WARNING: Failed to get value: 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. 
Feb  1 20:35:00 joe gdm-simple-slave[10332]: WARNING: Failed to get value: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[10989]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70503: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11052]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70504: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11054]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70505: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11055]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70506: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11056]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70507: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11057]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70508: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11058]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70509: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11059]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70510: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11060]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70511: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11061]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70512: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11062]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70513: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11064]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70515: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11071]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70522: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11063]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70514: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11065]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70516: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11066]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70517: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11067]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70518: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11068]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70519: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11069]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70520: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11070]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70521: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11072]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70523: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11073]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70524: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11074]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70525: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11076]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70526: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11077]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70527: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11078]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70528: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11079]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70529: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11081]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70531: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11080]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70530: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11082]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70532: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11083]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70533: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11084]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70534: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11085]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70535: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11086]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70536: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11087]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70537: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11088]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70538: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11089]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70539: 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. 
Feb  1 20:35:03 joe gdm-simple-slave[11090]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70540: 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. 
Feb  1 20:35:04 joe gdm-simple-slave[11091]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70541: 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. 
Feb  1 20:35:04 joe gdm-simple-slave[11092]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70542: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10583]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10584]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10585]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10586]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10587]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10588]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10589]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10590]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10591]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10592]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10593]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10594]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10595]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10596]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10597]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10598]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10599]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10600]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10601]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10602]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10603]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10604]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10605]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10606]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10607]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10608]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10609]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10610]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10611]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10612]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10613]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10614]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10615]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10616]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10617]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10618]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10619]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10621]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10622]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10623]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10624]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10625]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10626]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10627]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10628]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10629]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10630]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10631]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10632]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10633]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10650]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10657]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[10658]: WARNING: Failed to get value: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[11477]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70715: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[11476]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70714: 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. 
Feb  1 20:35:30 joe gdm-simple-slave[11479]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70717: 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. 
Feb  1 20:35:33 joe gdm-simple-slave[12127]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:35:58 joe gdm-simple-slave[11788]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11913]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11905]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11916]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11919]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11922]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11925]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11926]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11927]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11928]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11929]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11930]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11931]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11932]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11933]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11934]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11935]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11936]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11939]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11940]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11941]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11942]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11943]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11946]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11947]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11950]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11951]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11954]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[11980]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12002]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12005]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12010]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12013]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12016]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12019]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12022]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12026]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12031]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12044]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12051]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12052]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12053]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12054]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12055]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12056]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12057]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12058]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12060]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12061]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12062]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12063]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12064]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12065]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12066]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12067]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12068]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12069]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12070]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12072]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12071]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12073]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12074]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12075]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12076]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12078]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12079]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12080]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12081]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12082]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12083]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12084]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12085]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12086]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12087]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12088]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12089]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12090]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12091]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12092]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12093]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12207]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70930: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12208]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70931: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12209]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70932: 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. 
Feb  1 20:35:58 joe gdm-simple-slave[12210]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70933: 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. 
Feb  1 20:35:59 joe gdm-simple-slave[12211]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70934: 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. 
Feb  1 20:35:59 joe gdm-simple-slave[12212]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70935: 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. 
Feb  1 20:35:59 joe gdm-simple-slave[12213]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70936: 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. 
Feb  1 20:35:59 joe gdm-simple-slave[12214]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70937: 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. 
Feb  1 20:35:59 joe gdm-simple-slave[12215]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70938: 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. 
Feb  1 20:35:59 joe gdm-simple-slave[12216]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70939: 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. 
Feb  1 20:35:59 joe gdm-simple-slave[12231]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70940: 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. 
Feb  1 20:35:59 joe gdm-simple-slave[12234]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70941: 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. 
Feb  1 20:35:59 joe gdm-simple-slave[12235]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70942: 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. 
Feb  1 20:35:59 joe gdm-simple-slave[12242]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70943: 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. 
Feb  1 20:35:59 joe gdm-simple-slave[12243]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70944: 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. 
Feb  1 20:35:59 joe gdm-simple-slave[12244]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70945: 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. 
Feb  1 20:36:00 joe gdm-simple-slave[12245]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70946: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12246]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70947: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12247]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70948: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12248]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70949: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12249]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70950: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12250]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70951: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12252]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70952: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12253]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70953: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12254]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70954: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12255]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70955: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12256]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70956: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12260]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70960: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12257]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70957: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12258]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70958: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12259]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70959: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12261]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70961: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12262]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70962: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12265]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70965: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12263]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70963: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12272]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70972: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12273]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70973: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12264]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70964: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12266]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70966: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12267]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70967: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12268]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70968: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12269]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70969: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12270]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70970: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12271]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70971: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12274]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70974: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12276]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70975: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12277]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70976: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12278]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70977: 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. 
Feb  1 20:36:02 joe gdm-simple-slave[12279]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70978: 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. 
Feb  1 20:36:03 joe gdm-simple-slave[12280]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70979: 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. 
Feb  1 20:36:03 joe gdm-simple-slave[12281]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70980: 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. 
Feb  1 20:36:03 joe gdm-simple-slave[12282]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70981: 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. 
Feb  1 20:36:03 joe gdm-simple-slave[12283]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70982: 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. 
Feb  1 20:36:03 joe gdm-simple-slave[12284]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70983: 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. 
Feb  1 20:36:03 joe gdm-simple-slave[12285]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70984: 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. 
Feb  1 20:36:03 joe gdm-simple-slave[12286]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70985: 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. 
Feb  1 20:36:03 joe gdm-simple-slave[12287]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70986: 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. 
Feb  1 20:36:03 joe gdm-simple-slave[12288]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70987: 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. 
Feb  1 20:36:03 joe gdm-simple-slave[12289]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70988: 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. 
Feb  1 20:36:03 joe gdm-simple-slave[12290]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70989: 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. 
Feb  1 20:36:03 joe gdm-simple-slave[12291]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70990: 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. 
Feb  1 20:36:04 joe gdm-simple-slave[12292]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70991: 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. 
Feb  1 20:36:04 joe gdm-simple-slave[12293]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70992: 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. 
Feb  1 20:36:04 joe gdm-simple-slave[12294]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70993: 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. 
Feb  1 20:36:04 joe gdm-simple-slave[12295]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70994: 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. 
Feb  1 20:36:04 joe gdm-simple-slave[12296]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70995: 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. 
Feb  1 20:36:04 joe gdm-simple-slave[12297]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70996: 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. 
Feb  1 20:36:04 joe gdm-simple-slave[12298]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display70997: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[11950]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[11954]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12022]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12019]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12016]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12013]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12010]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12057]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12056]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12055]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12053]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12054]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12052]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12051]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12044]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12031]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12026]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[11951]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12005]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[11980]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12002]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12058]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12060]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12061]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12062]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12064]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12063]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12065]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12066]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12067]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12068]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12069]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12070]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12071]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12072]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12073]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12074]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12075]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12076]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12078]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12079]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12080]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12082]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12081]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12083]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12084]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12085]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12086]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12087]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12088]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12089]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12090]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12091]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12092]: WARNING: Failed to get value: 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. 
Feb  1 20:36:23 joe gdm-simple-slave[12093]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[12299]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[12300]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[12302]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[12318]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[12325]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[12326]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11788]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11905]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11913]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11916]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11936]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11919]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11935]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11922]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11934]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11925]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11933]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11926]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11932]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11927]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11928]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11931]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11930]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11929]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11939]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11940]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11941]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11942]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11943]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11946]: WARNING: Failed to get value: 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. 
Feb  1 20:36:29 joe gdm-simple-slave[11947]: WARNING: Failed to get value: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[12982]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[12990]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[12985]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13031]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13027]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13024]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13021]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13018]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13015]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13012]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[12996]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[12998]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13001]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13003]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13006]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13009]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13042]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13035]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13043]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13044]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13045]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13046]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13061]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13069]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13076]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13075]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13079]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13093]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13122]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13131]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13096]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13099]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13137]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13140]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13143]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13147]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13144]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13150]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13153]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13156]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13159]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13162]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13165]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13168]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13171]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13174]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13177]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13180]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13185]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13188]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[12299]: WARNING: Failed to get value: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[12300]: WARNING: Failed to get value: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[12302]: WARNING: Failed to get value: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[12318]: WARNING: Failed to get value: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[12325]: WARNING: Failed to get value: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[12326]: WARNING: Failed to get value: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13196]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13191]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13198]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13192]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13193]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13194]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13195]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13197]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13199]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13200]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13201]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13202]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13203]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13204]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13205]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13206]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13207]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:58 joe gdm-simple-slave[13208]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:36:59 joe gdm-simple-slave[13409]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71382: 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. 
Feb  1 20:36:59 joe gdm-simple-slave[13410]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71383: 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. 
Feb  1 20:36:59 joe gdm-simple-slave[13411]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71384: 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. 
Feb  1 20:36:59 joe gdm-simple-slave[13412]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71385: 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. 
Feb  1 20:36:59 joe gdm-simple-slave[13413]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71386: 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. 
Feb  1 20:36:59 joe gdm-simple-slave[13414]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71387: 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. 
Feb  1 20:36:59 joe gdm-simple-slave[13415]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71388: 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. 
Feb  1 20:36:59 joe gdm-simple-slave[13416]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71389: 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. 
Feb  1 20:36:59 joe gdm-simple-slave[13417]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71390: 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. 
Feb  1 20:36:59 joe gdm-simple-slave[13418]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71391: 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. 
Feb  1 20:36:59 joe gdm-simple-slave[13419]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71392: 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. 
Feb  1 20:36:59 joe gdm-simple-slave[13420]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71393: 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. 
Feb  1 20:37:00 joe gdm-simple-slave[13421]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71394: 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. 
Feb  1 20:37:00 joe gdm-simple-slave[13422]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71395: 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. 
Feb  1 20:37:00 joe gdm-simple-slave[13423]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71396: 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. 
Feb  1 20:37:00 joe gdm-simple-slave[13424]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71397: 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. 
Feb  1 20:37:00 joe gdm-simple-slave[13425]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71398: 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. 
Feb  1 20:37:00 joe gdm-simple-slave[13426]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71399: 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. 
Feb  1 20:37:00 joe gdm-simple-slave[13427]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71400: 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. 
Feb  1 20:37:00 joe gdm-simple-slave[13428]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71401: 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. 
Feb  1 20:37:00 joe gdm-simple-slave[13429]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71402: 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. 
Feb  1 20:37:00 joe gdm-simple-slave[13431]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71403: 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. 
Feb  1 20:37:01 joe gdm-simple-slave[13433]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71404: 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. 
Feb  1 20:37:01 joe gdm-simple-slave[13434]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71405: 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. 
Feb  1 20:37:01 joe gdm-simple-slave[13435]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71406: 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. 
Feb  1 20:37:01 joe gdm-simple-slave[13436]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71407: 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. 
Feb  1 20:37:01 joe gdm-simple-slave[13437]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71408: 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. 
Feb  1 20:37:01 joe gdm-simple-slave[13438]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71409: 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. 
Feb  1 20:37:01 joe gdm-simple-slave[13439]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71410: 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. 
Feb  1 20:37:01 joe gdm-simple-slave[13440]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71411: 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. 
Feb  1 20:37:01 joe gdm-simple-slave[13446]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71412: 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. 
Feb  1 20:37:02 joe gdm-simple-slave[13458]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71413: 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. 
Feb  1 20:37:04 joe gdm-simple-slave[13465]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71414: 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. 
Feb  1 20:37:04 joe gdm-simple-slave[13466]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71415: 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. 
Feb  1 20:37:04 joe gdm-simple-slave[13467]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71416: 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. 
Feb  1 20:37:04 joe gdm-simple-slave[13468]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71417: 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. 
Feb  1 20:37:04 joe gdm-simple-slave[13469]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71418: 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. 
Feb  1 20:37:04 joe gdm-simple-slave[13878]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:37:27 joe gdm-simple-slave[13470]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13472]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13475]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13483]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13482]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13481]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13480]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13479]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13499]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13498]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13497]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13496]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13495]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13494]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13493]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13473]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13492]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13474]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13491]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13478]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13484]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13489]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13477]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13490]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13485]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13476]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13486]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13487]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13488]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13500]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13501]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13502]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13503]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13504]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13505]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13506]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13507]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13508]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13509]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13510]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13511]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13512]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13513]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[12982]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[12985]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[12990]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13012]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13015]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13018]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13021]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13024]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13027]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13031]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[12996]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[12998]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13001]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13003]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13006]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13009]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13035]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13042]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13043]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13044]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13045]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13046]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13061]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13069]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13075]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13076]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13079]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13093]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13096]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13099]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13122]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13131]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13137]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13140]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13143]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13144]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13147]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13150]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13153]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13156]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13159]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13162]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13165]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13168]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13171]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13174]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13177]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13180]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13185]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13188]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13191]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13192]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13196]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13198]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13193]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13194]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13195]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13197]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13199]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13200]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13201]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13202]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13203]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13204]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13205]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13206]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13207]: WARNING: Failed to get value: 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. 
Feb  1 20:37:27 joe gdm-simple-slave[13208]: WARNING: Failed to get value: 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. 
Feb  1 20:37:28 joe gdm-simple-slave[13934]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71601: 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. 
Feb  1 20:37:28 joe gdm-simple-slave[13937]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71602: 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. 
Feb  1 20:37:28 joe gdm-simple-slave[13939]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71603: 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. 
Feb  1 20:37:28 joe gdm-simple-slave[13940]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71604: 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. 
Feb  1 20:37:28 joe gdm-simple-slave[13941]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71605: 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. 
Feb  1 20:37:28 joe gdm-simple-slave[13942]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71606: 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. 
Feb  1 20:37:28 joe gdm-simple-slave[13943]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71607: 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. 
Feb  1 20:37:28 joe gdm-simple-slave[13944]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71608: 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. 
Feb  1 20:37:28 joe gdm-simple-slave[13945]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71609: 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. 
Feb  1 20:37:28 joe gdm-simple-slave[13946]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71610: 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. 
Feb  1 20:37:28 joe gdm-simple-slave[13947]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71611: 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. 
Feb  1 20:37:29 joe gdm-simple-slave[13948]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71612: 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. 
Feb  1 20:37:29 joe gdm-simple-slave[13949]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71613: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13950]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71614: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13951]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71615: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13952]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71616: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13953]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71617: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13954]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71618: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13955]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71619: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13956]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71620: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13957]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71621: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13959]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71622: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13960]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71623: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13963]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71626: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13961]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71624: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13966]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71629: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13967]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71630: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13970]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71633: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13962]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71625: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13971]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71634: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13964]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71627: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13965]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71628: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13968]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71631: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13969]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71632: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13973]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71636: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13972]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71635: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13975]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71638: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13977]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71640: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13979]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71642: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13974]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71637: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13976]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71639: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13978]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71641: 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. 
Feb  1 20:37:32 joe gdm-simple-slave[13980]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display71643: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13499]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13498]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13487]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13488]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13500]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13501]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13502]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13503]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13504]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13505]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13506]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[14676]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:37:53 joe gdm-simple-slave[13507]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13508]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13509]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13510]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13511]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13512]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[13513]: WARNING: Failed to get value: 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. 
Feb  1 20:37:53 joe gdm-simple-slave[14687]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:37:53 joe gdm-simple-slave[14700]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:37:57 joe gdm-simple-slave[13470]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13472]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13475]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13479]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13480]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13481]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13482]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13483]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13473]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13474]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13476]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13477]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13478]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13484]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13485]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13486]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13489]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13490]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13491]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13492]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13493]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13494]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13495]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13496]: WARNING: Failed to get value: 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. 
Feb  1 20:37:57 joe gdm-simple-slave[13497]: WARNING: Failed to get value: 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. 
Feb  1 20:38:01 joe gdm-simple-slave[15046]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:38:26 joe gdm-simple-slave[14803]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14804]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14805]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14816]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14813]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14819]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14822]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14825]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14828]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14831]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14864]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14861]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14858]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14855]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14852]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14839]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14842]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14848]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14851]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14867]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14868]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14870]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14871]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14872]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14873]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14874]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14875]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14876]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14877]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14881]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14882]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14883]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14884]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14885]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14888]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14889]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14890]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14891]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14892]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14895]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14896]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14897]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14944]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14899]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14943]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14923]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14945]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14946]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14947]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14948]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14949]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14951]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14952]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14953]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14954]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14955]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14956]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14957]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14958]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14987]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14988]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14989]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14961]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14965]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14986]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14979]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14960]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14959]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14990]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14991]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14993]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14992]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14994]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14996]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14997]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14995]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14998]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[14999]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[15000]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[15001]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[15002]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[15004]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[15003]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[15005]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[15006]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[15007]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[15103]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72032: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[15104]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72033: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[15105]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72034: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[15106]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72035: 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. 
Feb  1 20:38:26 joe gdm-simple-slave[15107]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72036: 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. 
Feb  1 20:38:27 joe gdm-simple-slave[15108]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72037: 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. 
Feb  1 20:38:27 joe gdm-simple-slave[15109]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72038: 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. 
Feb  1 20:38:27 joe gdm-simple-slave[15110]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72039: 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. 
Feb  1 20:38:27 joe gdm-simple-slave[15111]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72040: 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. 
Feb  1 20:38:27 joe gdm-simple-slave[15112]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72041: 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. 
Feb  1 20:38:27 joe gdm-simple-slave[15113]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72042: 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. 
Feb  1 20:38:27 joe gdm-simple-slave[15114]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72043: 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. 
Feb  1 20:38:27 joe gdm-simple-slave[15115]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72044: 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. 
Feb  1 20:38:27 joe gdm-simple-slave[15116]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72045: 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. 
Feb  1 20:38:27 joe gdm-simple-slave[15117]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72046: 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. 
Feb  1 20:38:27 joe gdm-simple-slave[15118]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72047: 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. 
Feb  1 20:38:27 joe gdm-simple-slave[15119]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72048: 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. 
Feb  1 20:38:28 joe gdm-simple-slave[15120]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72049: 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. 
Feb  1 20:38:28 joe gdm-simple-slave[15121]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72050: 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. 
Feb  1 20:38:28 joe gdm-simple-slave[15122]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72051: 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. 
Feb  1 20:38:28 joe gdm-simple-slave[15124]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72052: 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. 
Feb  1 20:38:28 joe gdm-simple-slave[15127]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72053: 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. 
Feb  1 20:38:28 joe gdm-simple-slave[15128]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72054: 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. 
Feb  1 20:38:28 joe gdm-simple-slave[15129]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72055: 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. 
Feb  1 20:38:28 joe gdm-simple-slave[15130]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72056: 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. 
Feb  1 20:38:28 joe gdm-simple-slave[15131]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72057: 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. 
Feb  1 20:38:28 joe gdm-simple-slave[15132]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72058: 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. 
Feb  1 20:38:29 joe gdm-simple-slave[15133]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72059: 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. 
Feb  1 20:38:29 joe gdm-simple-slave[15146]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72060: 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. 
Feb  1 20:38:29 joe gdm-simple-slave[15155]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72061: 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. 
Feb  1 20:38:29 joe gdm-simple-slave[15158]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72062: 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. 
Feb  1 20:38:29 joe gdm-simple-slave[15159]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72063: 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. 
Feb  1 20:38:29 joe gdm-simple-slave[15160]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72064: 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. 
Feb  1 20:38:29 joe gdm-simple-slave[15161]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72065: 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. 
Feb  1 20:38:29 joe gdm-simple-slave[15162]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72066: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15163]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72067: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15164]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72068: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15165]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72069: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15166]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72070: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15167]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72071: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15168]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72072: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15169]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72073: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15170]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72074: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15171]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72075: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15172]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72076: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15174]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72078: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15173]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72077: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15177]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72081: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15178]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72082: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15175]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72079: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15182]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72086: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15176]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72080: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15179]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72083: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15180]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72084: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15181]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72085: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15184]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72088: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15183]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72087: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15186]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72090: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15188]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72092: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15185]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72089: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15189]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72093: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15191]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72095: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15187]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72091: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15190]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72094: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15192]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72096: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15193]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72097: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15194]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72098: 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. 
Feb  1 20:38:32 joe gdm-simple-slave[15195]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72099: 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. 
Feb  1 20:38:33 joe gdm-simple-slave[15592]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:38:34 joe gdm-simple-slave[15701]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:38:58 joe gdm-simple-slave[14803]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14804]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14805]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14813]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14816]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14819]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14822]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14825]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14828]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14831]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14852]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14855]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14858]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14861]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14864]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14842]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14839]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14867]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14848]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14868]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14851]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14871]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14870]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14872]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14873]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14875]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14877]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14874]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14882]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14876]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14883]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14881]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14885]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14884]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14889]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14888]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14891]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14890]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14892]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14896]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14899]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14895]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14923]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14897]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14944]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14943]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14946]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14945]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14948]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14947]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14951]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14949]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14952]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14954]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14956]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14987]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14957]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14953]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14959]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14955]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14961]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14958]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14979]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14960]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14986]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14965]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14988]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14989]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14990]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14991]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14992]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14993]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14994]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14995]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14996]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14997]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14998]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[14999]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[15000]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[15001]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[15002]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[15003]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[15004]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[15005]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[15006]: WARNING: Failed to get value: 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. 
Feb  1 20:38:58 joe gdm-simple-slave[15007]: WARNING: Failed to get value: 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. 
Feb  1 20:38:59 joe gdm-simple-slave[15721]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72274: 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. 
Feb  1 20:38:59 joe gdm-simple-slave[15722]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72275: 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. 
Feb  1 20:38:59 joe gdm-simple-slave[15723]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72276: 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. 
Feb  1 20:38:59 joe gdm-simple-slave[15724]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72277: 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. 
Feb  1 20:38:59 joe gdm-simple-slave[15725]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72278: 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. 
Feb  1 20:38:59 joe gdm-simple-slave[15726]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72279: 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. 
Feb  1 20:38:59 joe gdm-simple-slave[15727]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72280: 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. 
Feb  1 20:38:59 joe gdm-simple-slave[15728]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72281: 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. 
Feb  1 20:38:59 joe gdm-simple-slave[15729]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72282: 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. 
Feb  1 20:39:00 joe gdm-simple-slave[15730]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72283: 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. 
Feb  1 20:39:00 joe gdm-simple-slave[15731]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72284: 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. 
Feb  1 20:39:00 joe gdm-simple-slave[15732]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72285: 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. 
Feb  1 20:39:00 joe gdm-simple-slave[15733]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72286: 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. 
Feb  1 20:39:00 joe gdm-simple-slave[15734]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72287: 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. 
Feb  1 20:39:00 joe gdm-simple-slave[15735]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72288: 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. 
Feb  1 20:39:00 joe gdm-simple-slave[15736]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72289: 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. 
Feb  1 20:39:00 joe gdm-simple-slave[15737]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72290: 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. 
Feb  1 20:39:00 joe gdm-simple-slave[15738]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72291: 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. 
Feb  1 20:39:00 joe gdm-simple-slave[15739]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72292: 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. 
Feb  1 20:39:00 joe gdm-simple-slave[15740]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72293: 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. 
Feb  1 20:39:00 joe gdm-simple-slave[15741]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72294: 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. 
Feb  1 20:39:02 joe /USR/SBIN/CRON[16123]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \; -delete)
Feb  1 20:39:02 joe gdm-simple-slave[15742]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72295: 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. 
Feb  1 20:39:02 joe gdm-simple-slave[15745]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72296: 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. 
Feb  1 20:39:02 joe gdm-simple-slave[15746]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72297: 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. 
Feb  1 20:39:02 joe gdm-simple-slave[15747]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72298: 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. 
Feb  1 20:39:02 joe gdm-simple-slave[15748]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72299: 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. 
Feb  1 20:39:02 joe gdm-simple-slave[15749]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72300: 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. 
Feb  1 20:39:02 joe gdm-simple-slave[15750]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72301: 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. 
Feb  1 20:39:02 joe gdm-simple-slave[15751]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72302: 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. 
Feb  1 20:39:02 joe gdm-simple-slave[15752]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72303: 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. 
Feb  1 20:39:02 joe gdm-simple-slave[15753]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72304: 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. 
Feb  1 20:39:02 joe gdm-simple-slave[15754]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72305: 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. 
Feb  1 20:39:02 joe gdm-simple-slave[15755]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72306: 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. 
Feb  1 20:39:02 joe gdm-simple-slave[15756]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72307: 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. 
Feb  1 20:39:02 joe gdm-simple-slave[15771]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72309: 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. 
Feb  1 20:39:02 joe gdm-simple-slave[15781]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72310: 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. 
Feb  1 20:39:02 joe gdm-simple-slave[15757]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72308: 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. 
Feb  1 20:39:03 joe gdm-simple-slave[15782]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72311: 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. 
Feb  1 20:39:03 joe gdm-simple-slave[15783]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72312: 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. 
Feb  1 20:39:03 joe gdm-simple-slave[16174]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:39:03 joe gdm-simple-slave[16248]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:39:27 joe gdm-simple-slave[15794]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15795]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15796]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15797]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15798]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15799]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15800]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15801]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15802]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15803]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15804]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15805]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15806]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15807]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15808]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15809]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15810]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15811]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:27 joe gdm-simple-slave[15812]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:28 joe gdm-simple-slave[15784]: WARNING: Failed to get value: 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. 
Feb  1 20:39:28 joe gdm-simple-slave[15785]: WARNING: Failed to get value: 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. 
Feb  1 20:39:28 joe gdm-simple-slave[15786]: WARNING: Failed to get value: 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. 
Feb  1 20:39:28 joe gdm-simple-slave[15787]: WARNING: Failed to get value: 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. 
Feb  1 20:39:28 joe gdm-simple-slave[15788]: WARNING: Failed to get value: 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. 
Feb  1 20:39:28 joe gdm-simple-slave[15789]: WARNING: Failed to get value: 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. 
Feb  1 20:39:28 joe gdm-simple-slave[15790]: WARNING: Failed to get value: 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. 
Feb  1 20:39:28 joe gdm-simple-slave[15791]: WARNING: Failed to get value: 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. 
Feb  1 20:39:28 joe gdm-simple-slave[15792]: WARNING: Failed to get value: 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. 
Feb  1 20:39:28 joe gdm-simple-slave[15793]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16442]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16444]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16443]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16446]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16447]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16448]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16449]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16452]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16450]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16453]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16451]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16454]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16455]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16456]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16457]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16458]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16459]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16460]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16469]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16461]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16468]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16462]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16467]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16463]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16466]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16465]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16464]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16470]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16471]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16472]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16473]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16474]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16475]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16476]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16477]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16478]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16479]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16480]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16483]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16486]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16521]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16494]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16520]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16504]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16519]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16511]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16518]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16512]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16517]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16513]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16514]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16485]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16484]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16482]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16515]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16481]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16516]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16522]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16523]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16524]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16525]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16526]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16527]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16528]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16529]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16530]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16531]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16532]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16533]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16534]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16535]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16536]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16537]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16538]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16539]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16540]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16541]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16543]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16544]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16545]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16546]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16547]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16548]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16549]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16550]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16551]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16552]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16553]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16554]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16555]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16556]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16557]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16558]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16559]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16560]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16561]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16562]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16563]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16564]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16565]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16566]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16567]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16568]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16569]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16586]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16593]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16594]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15794]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15795]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15796]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15797]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15798]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15799]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15800]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15801]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15802]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15803]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15804]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15805]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15806]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15807]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15808]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15809]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15810]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15811]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[15812]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16408]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16409]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16410]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16411]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16412]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16422]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16429]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16430]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16431]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16432]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16433]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16434]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16435]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16437]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16436]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16438]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16440]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16439]: WARNING: Failed to get value: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16807]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72708: 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. 
Feb  1 20:39:53 joe gdm-simple-slave[16819]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72709: 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. 
Feb  1 20:39:54 joe gdm-simple-slave[16820]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72710: 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. 
Feb  1 20:39:54 joe gdm-simple-slave[16821]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72711: 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. 
Feb  1 20:39:54 joe gdm-simple-slave[16822]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72712: 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. 
Feb  1 20:39:54 joe gdm-simple-slave[16823]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72713: 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. 
Feb  1 20:39:54 joe gdm-simple-slave[16824]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72714: 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. 
Feb  1 20:39:54 joe gdm-simple-slave[16841]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72715: 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. 
Feb  1 20:39:54 joe gdm-simple-slave[16848]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72716: 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. 
Feb  1 20:39:54 joe gdm-simple-slave[16849]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display72717: 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. 
Feb  1 20:40:18 joe gdm-simple-slave[16561]: WARNING: Failed to get value: 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. 
Feb  1 20:40:18 joe gdm-simple-slave[16562]: WARNING: Failed to get value: 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. 
Feb  1 20:40:18 joe gdm-simple-slave[16563]: WARNING: Failed to get value: 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. 
Feb  1 20:40:18 joe gdm-simple-slave[16564]: WARNING: Failed to get value: 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. 
Feb  1 20:40:18 joe gdm-simple-slave[16565]: WARNING: Failed to get value: 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. 
Feb  1 20:40:18 joe gdm-simple-slave[16566]: WARNING: Failed to get value: 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. 
Feb  1 20:40:18 joe gdm-simple-slave[16567]: WARNING: Failed to get value: 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. 
Feb  1 20:40:18 joe gdm-simple-slave[16568]: WARNING: Failed to get value: 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. 
Feb  1 20:40:18 joe gdm-simple-slave[16569]: WARNING: Failed to get value: 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. 
Feb  1 20:40:18 joe gdm-simple-slave[16586]: WARNING: Failed to get value: 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. 
Feb  1 20:40:18 joe gdm-simple-slave[16593]: WARNING: Failed to get value: 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. 
Feb  1 20:40:18 joe gdm-simple-slave[16594]: WARNING: Failed to get value: 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. 
Feb  1 20:40:18 joe gdm-simple-slave[17578]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:40:27 joe gdm-simple-slave[16442]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16443]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16444]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16448]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16446]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16447]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16449]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16450]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16451]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16452]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16453]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16454]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16455]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16456]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16457]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16458]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16459]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16460]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16461]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16462]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16463]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16464]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16465]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16466]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16467]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16468]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16469]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16470]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16471]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16472]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16473]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16474]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16475]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16476]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16477]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16478]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16479]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16480]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16481]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16482]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16483]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16484]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16485]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16486]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16494]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16504]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16511]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16512]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16513]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16514]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16515]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16516]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16517]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16518]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16519]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16520]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16521]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16522]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16523]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16524]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16525]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16526]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16527]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16528]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16529]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16530]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16531]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16532]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16533]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16534]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16535]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16536]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16537]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16538]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16539]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16540]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16541]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16543]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16544]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16545]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16546]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16547]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16548]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16549]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16550]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16551]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16552]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16553]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16554]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16555]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16556]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16557]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16558]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16559]: WARNING: Failed to get value: 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. 
Feb  1 20:40:27 joe gdm-simple-slave[16560]: WARNING: Failed to get value: 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. 
Feb  1 20:40:33 joe gdm-simple-slave[17922]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:40:33 joe gdm-simple-slave[17983]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:40:34 joe gdm-simple-slave[18049]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:40:58 joe gdm-simple-slave[17647]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17656]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17650]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17658]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17661]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17666]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17670]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17671]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17672]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17674]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17673]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17675]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17676]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17677]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17678]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17680]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17679]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17682]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17681]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17689]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17683]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17702]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17709]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17722]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17710]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17721]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17711]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17720]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17712]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17719]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17713]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17718]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17714]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17723]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17724]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17716]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17715]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17717]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17725]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17726]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17734]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17727]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17728]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17733]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17732]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17731]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:58 joe gdm-simple-slave[17730]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:40:59 joe gdm-simple-slave[18099]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73142: 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. 
Feb  1 20:40:59 joe gdm-simple-slave[18100]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73143: 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. 
Feb  1 20:40:59 joe gdm-simple-slave[18101]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73144: 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. 
Feb  1 20:40:59 joe gdm-simple-slave[18102]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73145: 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. 
Feb  1 20:40:59 joe gdm-simple-slave[18103]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73146: 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. 
Feb  1 20:40:59 joe gdm-simple-slave[18104]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73147: 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. 
Feb  1 20:40:59 joe gdm-simple-slave[18105]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73148: 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. 
Feb  1 20:40:59 joe gdm-simple-slave[18106]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73149: 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. 
Feb  1 20:40:59 joe gdm-simple-slave[18107]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73150: 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. 
Feb  1 20:40:59 joe gdm-simple-slave[18108]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73151: 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. 
Feb  1 20:41:00 joe gdm-simple-slave[18109]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73152: 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. 
Feb  1 20:41:00 joe gdm-simple-slave[18110]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73153: 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. 
Feb  1 20:41:00 joe gdm-simple-slave[18111]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73154: 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. 
Feb  1 20:41:00 joe gdm-simple-slave[18112]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73155: 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. 
Feb  1 20:41:00 joe gdm-simple-slave[18113]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73156: 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. 
Feb  1 20:41:00 joe gdm-simple-slave[18114]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73157: 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. 
Feb  1 20:41:00 joe gdm-simple-slave[18115]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73158: 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. 
Feb  1 20:41:00 joe gdm-simple-slave[18116]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73159: 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. 
Feb  1 20:41:00 joe gdm-simple-slave[18117]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73160: 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. 
Feb  1 20:41:00 joe gdm-simple-slave[18118]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73161: 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. 
Feb  1 20:41:01 joe gdm-simple-slave[18120]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73162: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18153]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18154]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18155]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18156]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18157]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18158]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18159]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18160]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18161]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18162]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18163]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18164]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18165]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18166]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18167]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18168]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18169]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18170]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18171]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18172]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18173]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18174]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18175]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18176]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18177]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18178]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18179]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18180]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18181]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18182]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18183]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18184]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18185]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18186]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18187]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18188]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18189]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18190]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18191]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18192]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18193]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18194]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18195]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18196]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18197]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18198]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18199]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18200]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18201]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18202]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18203]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18204]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18205]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18218]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18229]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18230]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18231]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18232]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18233]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18234]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18235]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18236]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18237]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18238]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18239]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18240]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18241]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18242]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18243]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18244]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18245]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18246]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18247]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18248]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18249]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18250]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17647]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17650]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17656]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17658]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17661]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17666]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17670]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17671]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17672]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17673]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17674]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17675]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17676]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17677]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17678]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17679]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17680]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17681]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17682]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17683]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17689]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17702]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17709]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17710]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17711]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17712]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17713]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17714]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17715]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17716]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17717]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17718]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17719]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17720]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17721]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17722]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17723]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17724]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17725]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17726]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17727]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17728]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17732]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17733]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17734]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17730]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[17731]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18121]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18122]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18123]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18124]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18141]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18148]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18149]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18150]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18151]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18152]: WARNING: Failed to get value: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18544]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73359: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18545]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73360: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18546]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73361: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18547]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73362: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18548]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73363: 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. 
Feb  1 20:41:26 joe gdm-simple-slave[18549]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73364: 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. 
Feb  1 20:41:27 joe gdm-simple-slave[18550]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73365: 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. 
Feb  1 20:41:27 joe gdm-simple-slave[18563]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73366: 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. 
Feb  1 20:41:27 joe gdm-simple-slave[18570]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73369: 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. 
Feb  1 20:41:30 joe gdm-simple-slave[18587]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73375: 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. 
Feb  1 20:41:30 joe gdm-simple-slave[18589]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73376: 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. 
Feb  1 20:41:30 joe gdm-simple-slave[18591]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73377: 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. 
Feb  1 20:41:30 joe gdm-simple-slave[18592]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73378: 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. 
Feb  1 20:41:30 joe gdm-simple-slave[18593]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73379: 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. 
Feb  1 20:41:30 joe gdm-simple-slave[18594]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73380: 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. 
Feb  1 20:41:30 joe gdm-simple-slave[18595]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73381: 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. 
Feb  1 20:41:30 joe gdm-simple-slave[18596]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73382: 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. 
Feb  1 20:41:30 joe gdm-simple-slave[18613]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73391: 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. 
Feb  1 20:41:30 joe gdm-simple-slave[18614]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73392: 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. 
Feb  1 20:41:30 joe gdm-simple-slave[18615]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73393: 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. 
Feb  1 20:41:30 joe gdm-simple-slave[18616]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73394: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18176]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18177]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18178]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18179]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18180]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18181]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18182]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18183]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18184]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18185]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18186]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18187]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18190]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18188]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18189]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18191]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18192]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18193]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18194]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18195]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18196]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18197]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18198]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18199]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18200]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18201]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18202]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18203]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18204]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18205]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18218]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18229]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18230]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18231]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18232]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18233]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18234]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18235]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18236]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18237]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18238]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18239]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18240]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18241]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18242]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18243]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18244]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18245]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18246]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18247]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18248]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18249]: WARNING: Failed to get value: 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. 
Feb  1 20:41:51 joe gdm-simple-slave[18250]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18153]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18155]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18154]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18156]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18157]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18158]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18159]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18160]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18161]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18162]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18163]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18164]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18165]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18166]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18167]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18168]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18169]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18170]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18171]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18172]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18173]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18174]: WARNING: Failed to get value: 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. 
Feb  1 20:41:59 joe gdm-simple-slave[18175]: WARNING: Failed to get value: 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. 
Feb  1 20:42:00 joe gdm-simple-slave[19086]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73576: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19087]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73577: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19088]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73578: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19089]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73579: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19090]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73580: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19091]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73581: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19092]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73582: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19093]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73583: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19094]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73584: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19095]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73585: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19096]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73586: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19097]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73587: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19098]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73588: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19110]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73594: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19111]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73595: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19112]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73596: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19113]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73597: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19114]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73598: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19115]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73599: 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. 
Feb  1 20:42:01 joe gdm-simple-slave[19116]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73600: 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. 
Feb  1 20:42:02 joe gdm-simple-slave[19117]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73601: 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. 
Feb  1 20:42:02 joe gdm-simple-slave[19118]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73602: 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. 
Feb  1 20:42:02 joe gdm-simple-slave[19119]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73603: 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. 
Feb  1 20:42:02 joe gdm-simple-slave[19120]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73604: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19398]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19395]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19404]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19422]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19424]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19405]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19428]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19431]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19408]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19433]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19411]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19416]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19419]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19423]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19427]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19429]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19430]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19432]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19434]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19436]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19435]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19440]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19441]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19444]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19447]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19450]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19453]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19454]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19455]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19456]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19457]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19474]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19475]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19476]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19483]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19487]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19488]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19489]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19493]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19496]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19497]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19498]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19511]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19512]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19513]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19514]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19515]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19516]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19517]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19518]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19519]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19520]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19522]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:29 joe gdm-simple-slave[19521]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:30 joe gdm-simple-slave[19838]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73793: 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. 
Feb  1 20:42:30 joe gdm-simple-slave[19839]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73794: 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. 
Feb  1 20:42:30 joe gdm-simple-slave[19840]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73795: 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. 
Feb  1 20:42:30 joe gdm-simple-slave[19850]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73796: 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. 
Feb  1 20:42:30 joe gdm-simple-slave[19857]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73797: 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. 
Feb  1 20:42:30 joe gdm-simple-slave[19858]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73798: 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. 
Feb  1 20:42:30 joe gdm-simple-slave[19859]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73799: 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. 
Feb  1 20:42:30 joe gdm-simple-slave[19860]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73800: 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. 
Feb  1 20:42:30 joe gdm-simple-slave[19861]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73801: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19862]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73802: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19863]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73803: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19864]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73804: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19865]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73805: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19866]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73806: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19867]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73807: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19868]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73808: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19869]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73809: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19870]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73810: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19872]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73811: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19873]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73812: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19878]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73816: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19879]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73817: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19875]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73813: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19876]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73814: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19877]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73815: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19880]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73818: 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. 
Feb  1 20:42:32 joe gdm-simple-slave[19881]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display73819: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19884]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19885]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19886]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19887]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19888]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19889]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19890]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19891]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19906]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19892]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19905]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19904]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19903]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19902]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19893]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19901]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19895]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19896]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19898]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19900]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19908]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19909]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19937]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19910]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19930]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19911]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19913]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19940]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19941]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19952]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19942]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19951]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19943]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19950]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19944]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19945]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19948]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19946]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19947]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19953]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19955]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19954]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19956]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19968]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19957]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19967]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19958]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19966]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19899]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19959]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19907]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19965]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19938]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19960]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19912]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19964]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19961]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19949]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19976]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19963]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19962]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19969]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19970]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19971]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19972]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19973]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19974]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19975]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19977]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19978]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19979]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19395]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19398]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19404]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19405]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19408]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19411]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19416]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19422]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19424]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19428]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19431]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19433]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19419]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19423]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19427]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19429]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19430]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19432]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19434]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19435]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19436]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19440]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19441]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19444]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19447]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19450]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19453]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19454]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19455]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19456]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19457]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19474]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19475]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19476]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19483]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19487]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19488]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19489]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19493]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19496]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19497]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19498]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19511]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19512]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19513]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19514]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19515]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19516]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19517]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19518]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19519]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19520]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19521]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19522]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19882]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[19883]: WARNING: Failed to get value: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[20283]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74010: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[20284]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74011: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[20285]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74012: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[20286]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74013: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[20287]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74014: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[20288]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74015: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[20289]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74016: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[20290]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74017: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[20291]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74018: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[20292]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74019: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[20293]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74020: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[20294]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74021: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[20308]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74028: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[20309]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74029: 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. 
Feb  1 20:42:59 joe gdm-simple-slave[20310]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74030: 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. 
Feb  1 20:43:00 joe gdm-simple-slave[20311]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74031: 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. 
Feb  1 20:43:00 joe gdm-simple-slave[20312]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74032: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19884]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19885]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19886]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19887]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19888]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19889]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[20663]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[20665]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[20668]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[20669]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[20670]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[20671]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[20673]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[20674]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[20675]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[20677]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19890]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19891]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19906]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19892]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19905]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19893]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19895]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19901]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19902]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19903]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19904]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19896]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19898]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19900]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19908]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19909]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19910]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19911]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19913]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19930]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19937]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19940]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19941]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19942]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19943]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19944]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19945]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19946]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19947]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19948]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19950]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19951]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19952]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19953]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19954]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19955]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19956]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19957]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19967]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19968]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19899]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19907]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19912]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19938]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19949]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19958]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19959]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19960]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19961]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19962]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19963]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19964]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19965]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19966]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19969]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19970]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19971]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19972]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19973]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19974]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19975]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19976]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19977]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19978]: WARNING: Failed to get value: 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. 
Feb  1 20:43:30 joe gdm-simple-slave[19979]: WARNING: Failed to get value: 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. 
Feb  1 20:43:31 joe gdm-simple-slave[20922]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74227: 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. 
Feb  1 20:43:31 joe gdm-simple-slave[20923]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74228: 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. 
Feb  1 20:43:31 joe gdm-simple-slave[20924]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74229: 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. 
Feb  1 20:43:31 joe gdm-simple-slave[20925]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74230: 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. 
Feb  1 20:43:31 joe gdm-simple-slave[20926]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74231: 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. 
Feb  1 20:43:31 joe gdm-simple-slave[20927]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74232: 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. 
Feb  1 20:43:31 joe gdm-simple-slave[20928]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74233: 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. 
Feb  1 20:43:31 joe gdm-simple-slave[20929]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74234: 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. 
Feb  1 20:43:31 joe gdm-simple-slave[20930]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74235: 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. 
Feb  1 20:43:31 joe gdm-simple-slave[20931]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74236: 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. 
Feb  1 20:43:31 joe gdm-simple-slave[20932]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74237: 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. 
Feb  1 20:43:31 joe gdm-simple-slave[20933]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74238: 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. 
Feb  1 20:43:32 joe gdm-simple-slave[20934]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74239: 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. 
Feb  1 20:43:32 joe gdm-simple-slave[20935]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74240: 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. 
Feb  1 20:43:32 joe gdm-simple-slave[20936]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74241: 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. 
Feb  1 20:43:32 joe gdm-simple-slave[20937]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74242: 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. 
Feb  1 20:43:32 joe gdm-simple-slave[20938]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74243: 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. 
Feb  1 20:43:32 joe gdm-simple-slave[20945]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74244: 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. 
Feb  1 20:43:32 joe gdm-simple-slave[20956]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74245: 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. 
Feb  1 20:43:32 joe gdm-simple-slave[20958]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74246: 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. 
Feb  1 20:43:33 joe gdm-simple-slave[20965]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74247: 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. 
Feb  1 20:43:33 joe gdm-simple-slave[20966]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74248: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20967]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74249: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20968]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74250: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20969]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74251: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20970]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74252: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20971]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74253: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20972]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74254: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20973]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74255: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20974]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74256: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20975]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74257: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20976]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74258: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20980]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74262: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20977]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74259: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20981]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74263: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20978]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74260: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20982]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74264: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20979]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74261: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20984]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74266: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20983]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74265: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20986]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74268: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20985]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74267: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20987]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74269: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20988]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74270: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20998]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74280: 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. 
Feb  1 20:43:35 joe gdm-simple-slave[20999]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74281: 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. 
Feb  1 20:43:36 joe gdm-simple-slave[21000]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74282: 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. 
Feb  1 20:43:36 joe gdm-simple-slave[21001]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74283: 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. 
Feb  1 20:43:36 joe gdm-simple-slave[21002]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74284: 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. 
Feb  1 20:43:36 joe gdm-simple-slave[21003]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74285: 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. 
Feb  1 20:43:36 joe gdm-simple-slave[21004]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74286: 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. 
Feb  1 20:43:36 joe gdm-simple-slave[21005]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74287: 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. 
Feb  1 20:43:36 joe gdm-simple-slave[21006]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74288: 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. 
Feb  1 20:43:36 joe gdm-simple-slave[21007]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74289: 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. 
Feb  1 20:43:36 joe gdm-simple-slave[21008]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74290: 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. 
Feb  1 20:43:36 joe gdm-simple-slave[21009]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74291: 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. 
Feb  1 20:43:36 joe gdm-simple-slave[21010]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74292: 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. 
Feb  1 20:43:37 joe gdm-simple-slave[21011]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74293: 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. 
Feb  1 20:43:37 joe gdm-simple-slave[21012]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74294: 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. 
Feb  1 20:43:37 joe gdm-simple-slave[21013]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74295: 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. 
Feb  1 20:43:37 joe gdm-simple-slave[21014]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74296: 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. 
Feb  1 20:43:37 joe gdm-simple-slave[21015]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74297: 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. 
Feb  1 20:43:37 joe gdm-simple-slave[21016]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74298: 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. 
Feb  1 20:43:37 joe gdm-simple-slave[21017]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74299: 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. 
Feb  1 20:43:55 joe gdm-simple-slave[20663]: WARNING: Failed to get value: 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. 
Feb  1 20:43:55 joe gdm-simple-slave[20665]: WARNING: Failed to get value: 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. 
Feb  1 20:43:55 joe gdm-simple-slave[20668]: WARNING: Failed to get value: 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. 
Feb  1 20:43:55 joe gdm-simple-slave[20669]: WARNING: Failed to get value: 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. 
Feb  1 20:43:55 joe gdm-simple-slave[20670]: WARNING: Failed to get value: 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. 
Feb  1 20:43:55 joe gdm-simple-slave[20671]: WARNING: Failed to get value: 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. 
Feb  1 20:43:55 joe gdm-simple-slave[20673]: WARNING: Failed to get value: 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. 
Feb  1 20:43:55 joe gdm-simple-slave[20674]: WARNING: Failed to get value: 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. 
Feb  1 20:43:55 joe gdm-simple-slave[20675]: WARNING: Failed to get value: 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. 
Feb  1 20:43:55 joe gdm-simple-slave[20677]: WARNING: Failed to get value: 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. 
Feb  1 20:44:00 joe gdm-simple-slave[20989]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:00 joe gdm-simple-slave[20990]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:00 joe gdm-simple-slave[20991]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:00 joe gdm-simple-slave[20992]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:00 joe gdm-simple-slave[20993]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:00 joe gdm-simple-slave[20994]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:00 joe gdm-simple-slave[20995]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:00 joe gdm-simple-slave[20996]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:00 joe gdm-simple-slave[20997]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21788]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21789]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21794]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21809]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21820]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21823]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21828]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21831]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21834]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21837]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21840]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21843]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21848]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21851]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21855]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21859]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21861]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21865]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21866]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21901]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21904]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21905]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21908]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21909]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21874]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21895]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21885]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21873]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21888]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21910]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21911]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21912]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21913]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21914]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21915]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21916]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21918]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21919]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21923]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21924]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[20989]: WARNING: Failed to get value: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[20990]: WARNING: Failed to get value: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[20991]: WARNING: Failed to get value: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[20992]: WARNING: Failed to get value: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[20993]: WARNING: Failed to get value: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[20994]: WARNING: Failed to get value: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[20995]: WARNING: Failed to get value: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21933]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21936]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21967]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21970]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21971]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21975]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21980]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22019]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22024]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22036]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22041]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22058]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22056]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22064]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22063]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22059]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22057]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22060]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22062]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22048]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22061]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22042]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[20997]: WARNING: Failed to get value: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[20996]: WARNING: Failed to get value: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21932]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22065]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21929]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22066]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21930]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22070]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22072]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22073]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22074]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22078]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22083]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22082]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22080]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22081]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22079]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22076]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22077]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21926]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22075]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[21925]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22084]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22086]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22085]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22069]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22071]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22067]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22108]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74661: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22109]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74662: 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. 
Feb  1 20:44:30 joe gdm-simple-slave[22110]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74663: 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. 
Feb  1 20:44:31 joe gdm-simple-slave[22111]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74664: 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. 
Feb  1 20:44:31 joe gdm-simple-slave[22112]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74665: 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. 
Feb  1 20:44:31 joe gdm-simple-slave[22113]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74666: 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. 
Feb  1 20:44:31 joe gdm-simple-slave[22114]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74667: 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. 
Feb  1 20:44:31 joe gdm-simple-slave[22115]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74668: 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. 
Feb  1 20:44:31 joe gdm-simple-slave[22116]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74669: 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. 
Feb  1 20:44:31 joe gdm-simple-slave[22117]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74670: 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. 
Feb  1 20:44:31 joe gdm-simple-slave[22118]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74671: 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. 
Feb  1 20:44:31 joe gdm-simple-slave[22127]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74672: 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. 
Feb  1 20:44:31 joe gdm-simple-slave[22138]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74673: 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. 
Feb  1 20:44:31 joe gdm-simple-slave[22144]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74674: 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. 
Feb  1 20:44:31 joe gdm-simple-slave[22145]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74675: 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. 
Feb  1 20:44:32 joe gdm-simple-slave[22146]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74676: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22147]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74677: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22148]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74678: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22149]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74679: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22150]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74680: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22151]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74681: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22152]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74682: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22154]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74683: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22155]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74684: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22156]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74685: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22158]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74687: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22157]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74686: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22161]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74690: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22159]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74688: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22162]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74691: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22160]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74689: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22163]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74692: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22164]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74693: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22165]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74694: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22166]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74695: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22168]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74697: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22169]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74698: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22172]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74701: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22173]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74702: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22171]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74700: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22170]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74699: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22167]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74696: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22174]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74703: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22175]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74704: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22176]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74705: 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. 
Feb  1 20:44:34 joe gdm-simple-slave[22177]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74706: 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. 
Feb  1 20:44:35 joe gdm-simple-slave[22178]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74707: 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. 
Feb  1 20:44:35 joe gdm-simple-slave[22179]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74708: 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. 
Feb  1 20:44:35 joe gdm-simple-slave[22180]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74709: 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. 
Feb  1 20:44:35 joe gdm-simple-slave[22181]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74710: 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. 
Feb  1 20:44:35 joe gdm-simple-slave[22182]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74711: 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. 
Feb  1 20:44:35 joe gdm-simple-slave[22183]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74712: 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. 
Feb  1 20:44:35 joe gdm-simple-slave[22184]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74713: 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. 
Feb  1 20:44:35 joe gdm-simple-slave[22185]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74714: 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. 
Feb  1 20:44:35 joe gdm-simple-slave[22186]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74715: 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. 
Feb  1 20:44:35 joe gdm-simple-slave[22187]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74716: 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. 
Feb  1 20:44:35 joe gdm-simple-slave[22188]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74717: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21788]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21794]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21789]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21809]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21820]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21823]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21828]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21831]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21834]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21837]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21840]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21843]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21848]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21851]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21855]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21859]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21861]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21865]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21866]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21873]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21874]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21885]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21888]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21895]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21901]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21904]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21905]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21908]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21909]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21910]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21911]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21912]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21913]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21914]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21915]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21916]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21918]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21923]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21919]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21924]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21925]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21926]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21929]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21930]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21932]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21933]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21936]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21967]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21970]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21971]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21975]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[21980]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22019]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22024]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22036]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22041]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22042]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22048]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22056]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22057]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22058]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22059]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22060]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22061]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22062]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22063]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22064]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22066]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22065]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22067]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22069]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22070]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22071]: WARNING: Failed to get value: 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. 
Feb  1 20:45:08 joe gdm-simple-slave[22072]: WARNING: Failed to get value: 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. 
Feb  1 20:45:09 joe gdm-simple-slave[22073]: WARNING: Failed to get value: 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. 
Feb  1 20:45:09 joe gdm-simple-slave[22074]: WARNING: Failed to get value: 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. 
Feb  1 20:45:09 joe gdm-simple-slave[22075]: WARNING: Failed to get value: 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. 
Feb  1 20:45:09 joe gdm-simple-slave[22076]: WARNING: Failed to get value: 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. 
Feb  1 20:45:09 joe gdm-simple-slave[22077]: WARNING: Failed to get value: 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. 
Feb  1 20:45:09 joe gdm-simple-slave[22078]: WARNING: Failed to get value: 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. 
Feb  1 20:45:09 joe gdm-simple-slave[22079]: WARNING: Failed to get value: 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. 
Feb  1 20:45:09 joe gdm-simple-slave[22080]: WARNING: Failed to get value: 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. 
Feb  1 20:45:09 joe gdm-simple-slave[22081]: WARNING: Failed to get value: 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. 
Feb  1 20:45:09 joe gdm-simple-slave[22082]: WARNING: Failed to get value: 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. 
Feb  1 20:45:09 joe gdm-simple-slave[22083]: WARNING: Failed to get value: 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. 
Feb  1 20:45:09 joe gdm-simple-slave[22084]: WARNING: Failed to get value: 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. 
Feb  1 20:45:09 joe gdm-simple-slave[22085]: WARNING: Failed to get value: 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. 
Feb  1 20:45:09 joe gdm-simple-slave[22086]: WARNING: Failed to get value: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22823]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74925: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22826]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74926: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22827]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74927: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22828]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74928: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22831]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74929: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22832]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74930: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22834]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74931: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22837]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74932: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22839]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74933: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22841]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74934: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22842]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74935: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22843]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74936: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22844]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74937: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22848]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74940: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22849]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74941: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22855]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74945: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22856]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74946: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22853]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74944: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22851]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74943: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22850]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74942: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22847]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74939: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22846]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74938: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22857]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74947: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22858]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74948: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22859]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74949: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22860]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74950: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22861]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74951: 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. 
Feb  1 20:45:11 joe gdm-simple-slave[22862]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74952: 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. 
Feb  1 20:45:12 joe gdm-simple-slave[22863]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74953: 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. 
Feb  1 20:45:12 joe gdm-simple-slave[22864]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74954: 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. 
Feb  1 20:45:12 joe gdm-simple-slave[22865]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74955: 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. 
Feb  1 20:45:12 joe gdm-simple-slave[22866]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74956: 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. 
Feb  1 20:45:12 joe gdm-simple-slave[22867]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74957: 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. 
Feb  1 20:45:12 joe gdm-simple-slave[22868]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74958: 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. 
Feb  1 20:45:12 joe gdm-simple-slave[22869]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74959: 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. 
Feb  1 20:45:12 joe gdm-simple-slave[22870]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74960: 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. 
Feb  1 20:45:12 joe gdm-simple-slave[22871]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74961: 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. 
Feb  1 20:45:12 joe gdm-simple-slave[22872]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74962: 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. 
Feb  1 20:45:12 joe gdm-simple-slave[22873]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74963: 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. 
Feb  1 20:45:13 joe gdm-simple-slave[22874]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74964: 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. 
Feb  1 20:45:13 joe gdm-simple-slave[22875]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74965: 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. 
Feb  1 20:45:13 joe gdm-simple-slave[22876]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74966: 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. 
Feb  1 20:45:13 joe gdm-simple-slave[22877]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74967: 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. 
Feb  1 20:45:13 joe gdm-simple-slave[22878]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74968: 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. 
Feb  1 20:45:13 joe gdm-simple-slave[22879]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74969: 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. 
Feb  1 20:45:13 joe gdm-simple-slave[22880]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74970: 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. 
Feb  1 20:45:13 joe gdm-simple-slave[22881]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74971: 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. 
Feb  1 20:45:13 joe gdm-simple-slave[22882]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74972: 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. 
Feb  1 20:45:13 joe gdm-simple-slave[22883]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74973: 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. 
Feb  1 20:45:13 joe gdm-simple-slave[22896]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74974: 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. 
Feb  1 20:45:14 joe gdm-simple-slave[22906]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74975: 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. 
Feb  1 20:45:14 joe gdm-simple-slave[22924]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74976: 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. 
Feb  1 20:45:14 joe gdm-simple-slave[22926]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74977: 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. 
Feb  1 20:45:14 joe gdm-simple-slave[22929]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74978: 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. 
Feb  1 20:45:14 joe gdm-simple-slave[22930]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74979: 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. 
Feb  1 20:45:15 joe gdm-simple-slave[22931]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74980: 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. 
Feb  1 20:45:15 joe gdm-simple-slave[22932]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74981: 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. 
Feb  1 20:45:15 joe gdm-simple-slave[22933]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74982: 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. 
Feb  1 20:45:15 joe gdm-simple-slave[22934]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74983: 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. 
Feb  1 20:45:15 joe gdm-simple-slave[22941]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display74990: 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. 
Feb  1 20:45:34 joe gdm-simple-slave[23811]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:45:34 joe gdm-simple-slave[23832]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:45:39 joe gdm-simple-slave[22935]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:45:39 joe gdm-simple-slave[22936]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:45:39 joe gdm-simple-slave[22937]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:45:39 joe gdm-simple-slave[22938]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:45:39 joe gdm-simple-slave[22939]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:45:39 joe gdm-simple-slave[22940]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23926]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23927]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23928]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23934]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23937]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23952]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23959]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23966]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23967]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23968]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23969]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23970]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23971]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23974]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23975]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23976]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23980]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23981]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23988]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23993]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[23995]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24042]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24046]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24070]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24061]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24035]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24038]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24023]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24032]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24029]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24020]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24026]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24074]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24077]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24080]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24083]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24086]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24095]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24098]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24101]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24104]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24108]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24110]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[22938]: WARNING: Failed to get value: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24162]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24163]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24164]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24165]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24166]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24167]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24168]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24169]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24170]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24171]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24161]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24155]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24156]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24137]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24160]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24129]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24173]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24151]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24154]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24172]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24128]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[22939]: WARNING: Failed to get value: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[22940]: WARNING: Failed to get value: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[22935]: WARNING: Failed to get value: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[22937]: WARNING: Failed to get value: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[22936]: WARNING: Failed to get value: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24116]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24174]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24125]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24122]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24113]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24119]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24175]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24176]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24177]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24178]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24179]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24180]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24181]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24182]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24183]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24184]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24185]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24186]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24187]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24188]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24189]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24190]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24191]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24192]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24193]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24194]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24195]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24196]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24197]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24198]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24199]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24200]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24201]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24202]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24203]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75359: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24204]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75360: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24205]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75361: 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. 
Feb  1 20:46:09 joe gdm-simple-slave[24206]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75362: 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. 
Feb  1 20:46:10 joe gdm-simple-slave[24207]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75363: 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. 
Feb  1 20:46:10 joe gdm-simple-slave[24208]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75364: 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. 
Feb  1 20:46:10 joe gdm-simple-slave[24225]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75365: 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. 
Feb  1 20:46:10 joe gdm-simple-slave[24232]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75366: 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. 
Feb  1 20:46:10 joe gdm-simple-slave[24233]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75367: 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. 
Feb  1 20:46:10 joe gdm-simple-slave[24234]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75368: 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. 
Feb  1 20:46:10 joe gdm-simple-slave[24235]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75369: 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. 
Feb  1 20:46:10 joe gdm-simple-slave[24236]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75370: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24237]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75371: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24238]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75372: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24239]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75373: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24240]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75374: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24241]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75375: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24242]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75376: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24243]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75377: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24244]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75378: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24245]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75379: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24246]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75380: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24247]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75381: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24250]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75384: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24248]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75382: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24249]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75383: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24251]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75385: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24252]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75386: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24253]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75387: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24254]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75388: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24256]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75390: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24255]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75389: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24257]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75391: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24260]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75394: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24258]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75392: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24259]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75393: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24261]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75395: 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. 
Feb  1 20:46:12 joe gdm-simple-slave[24262]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75396: 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. 
Feb  1 20:46:13 joe gdm-simple-slave[24263]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75397: 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. 
Feb  1 20:46:13 joe gdm-simple-slave[24264]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75398: 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. 
Feb  1 20:46:13 joe gdm-simple-slave[24265]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75399: 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. 
Feb  1 20:46:13 joe gdm-simple-slave[24266]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75400: 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. 
Feb  1 20:46:13 joe gdm-simple-slave[24267]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75401: 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. 
Feb  1 20:46:13 joe gdm-simple-slave[24268]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75402: 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. 
Feb  1 20:46:13 joe gdm-simple-slave[24269]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75403: 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. 
Feb  1 20:46:13 joe gdm-simple-slave[24270]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75404: 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. 
Feb  1 20:46:13 joe gdm-simple-slave[24271]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75405: 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. 
Feb  1 20:46:13 joe gdm-simple-slave[24272]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75406: 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. 
Feb  1 20:46:13 joe gdm-simple-slave[24273]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75407: 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. 
Feb  1 20:46:14 joe gdm-simple-slave[24274]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75408: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24180]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24182]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24181]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24189]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24190]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24183]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24184]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24191]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24185]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24192]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24186]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24193]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24187]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24194]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24188]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24195]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24196]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24197]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24199]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24198]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24201]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24200]: WARNING: Failed to get value: 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. 
Feb  1 20:46:34 joe gdm-simple-slave[24202]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23926]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23927]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23928]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23934]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23937]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23952]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23959]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23966]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23967]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23968]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23975]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23974]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23971]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23970]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23969]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23976]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23995]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23993]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24095]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24086]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24083]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24080]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23981]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24020]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24077]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24023]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24070]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24026]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24061]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24029]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24046]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24042]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24038]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24035]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24032]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24137]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24101]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24155]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24104]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24156]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24110]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24160]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24116]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24125]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24128]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24151]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24171]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24174]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24161]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24176]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24162]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24783]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75627: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24168]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24167]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24173]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24178]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24163]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24119]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24098]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24074]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23980]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24113]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24782]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75626: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24129]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24154]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24108]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24169]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24175]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24170]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[23988]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24166]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24165]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24179]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24164]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24122]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24177]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24172]: WARNING: Failed to get value: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24784]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75628: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24785]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75629: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24786]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75630: 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. 
Feb  1 20:46:50 joe gdm-simple-slave[24787]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75631: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24945]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24948]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24951]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24954]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24957]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24972]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24975]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24976]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24979]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24982]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24985]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24988]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24991]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24994]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24997]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24998]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[24999]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25000]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25001]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25010]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25014]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25033]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25053]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25093]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25097]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25094]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25090]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25066]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25105]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25106]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25109]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25112]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25119]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25113]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25121]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25114]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25125]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25115]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25127]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25117]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25116]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25118]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25120]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25122]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25123]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25124]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25126]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25128]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25129]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25130]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25498]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75843: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25551]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75844: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25552]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75845: 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. 
Feb  1 20:47:21 joe gdm-simple-slave[25553]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75846: 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. 
Feb  1 20:47:22 joe gdm-simple-slave[25554]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75847: 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. 
Feb  1 20:47:22 joe gdm-simple-slave[25555]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75848: 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. 
Feb  1 20:47:22 joe gdm-simple-slave[25556]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75849: 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. 
Feb  1 20:47:22 joe gdm-simple-slave[25557]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75850: 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. 
Feb  1 20:47:22 joe gdm-simple-slave[25558]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75851: 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. 
Feb  1 20:47:22 joe gdm-simple-slave[25559]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75852: 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. 
Feb  1 20:47:22 joe gdm-simple-slave[25560]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75853: 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. 
Feb  1 20:47:22 joe gdm-simple-slave[25561]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75854: 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. 
Feb  1 20:47:22 joe gdm-simple-slave[25562]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75855: 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. 
Feb  1 20:47:22 joe gdm-simple-slave[25563]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75856: 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. 
Feb  1 20:47:22 joe gdm-simple-slave[25564]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75857: 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. 
Feb  1 20:47:22 joe gdm-simple-slave[25565]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75858: 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. 
Feb  1 20:47:23 joe gdm-simple-slave[25566]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75859: 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. 
Feb  1 20:47:23 joe gdm-simple-slave[25567]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75860: 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. 
Feb  1 20:47:23 joe gdm-simple-slave[25568]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75861: 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. 
Feb  1 20:47:23 joe gdm-simple-slave[25569]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75862: 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. 
Feb  1 20:47:23 joe gdm-simple-slave[25570]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75863: 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. 
Feb  1 20:47:23 joe gdm-simple-slave[25571]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75864: 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. 
Feb  1 20:47:23 joe gdm-simple-slave[25578]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75866: 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. 
Feb  1 20:47:23 joe gdm-simple-slave[25575]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75865: 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. 
Feb  1 20:47:23 joe gdm-simple-slave[25580]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75867: 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. 
Feb  1 20:47:24 joe gdm-simple-slave[25582]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75868: 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. 
Feb  1 20:47:24 joe gdm-simple-slave[25586]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75869: 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. 
Feb  1 20:47:24 joe gdm-simple-slave[25588]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75870: 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. 
Feb  1 20:47:24 joe gdm-simple-slave[25589]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75871: 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. 
Feb  1 20:47:24 joe gdm-simple-slave[25590]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75872: 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. 
Feb  1 20:47:24 joe gdm-simple-slave[25599]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75873: 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. 
Feb  1 20:47:24 joe gdm-simple-slave[25606]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display75874: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25617]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25619]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25620]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25621]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25622]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25623]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25624]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25625]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25626]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25627]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25628]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25629]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25630]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25631]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25642]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25634]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25638]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25633]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25636]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25632]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25637]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25639]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25641]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25635]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25640]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25652]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25653]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25654]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25655]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25656]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25658]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25659]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25660]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25661]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25662]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25663]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24957]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24972]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24975]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25694]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25691]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25690]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25692]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25695]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25693]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25696]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25688]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24954]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24951]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24945]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24948]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25647]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25699]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25698]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25697]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25702]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25700]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25701]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25649]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25646]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25643]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25645]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25648]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25651]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25644]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25689]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25115]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25116]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25117]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24979]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24976]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24982]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24985]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24988]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24991]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24994]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24997]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24998]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[24999]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25000]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25001]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25010]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25014]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25033]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25053]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25066]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25090]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25093]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25094]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25097]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25105]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25106]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25109]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25112]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25113]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25114]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25118]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25119]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25120]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25121]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25122]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25123]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25124]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25125]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25126]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25127]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25128]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25129]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25130]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25650]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25664]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25681]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25607]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25608]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25609]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25610]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25611]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25612]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25613]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25614]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25615]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[25616]: WARNING: Failed to get value: 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. 
Feb  1 20:47:49 joe gdm-simple-slave[26024]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76060: 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. 
Feb  1 20:47:50 joe gdm-simple-slave[26025]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76061: 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. 
Feb  1 20:47:50 joe gdm-simple-slave[26034]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76062: 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. 
Feb  1 20:47:50 joe gdm-simple-slave[26035]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76063: 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. 
Feb  1 20:47:50 joe gdm-simple-slave[26036]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76064: 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. 
Feb  1 20:47:50 joe gdm-simple-slave[26037]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76065: 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. 
Feb  1 20:47:50 joe gdm-simple-slave[26042]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76066: 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. 
Feb  1 20:47:50 joe gdm-simple-slave[26043]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76067: 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. 
Feb  1 20:47:50 joe gdm-simple-slave[26044]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76068: 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. 
Feb  1 20:47:50 joe gdm-simple-slave[26045]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76069: 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. 
Feb  1 20:47:50 joe gdm-simple-slave[26046]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76070: 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. 
Feb  1 20:47:50 joe gdm-simple-slave[26047]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76071: 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. 
Feb  1 20:47:51 joe gdm-simple-slave[26048]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76072: 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. 
Feb  1 20:47:51 joe gdm-simple-slave[26050]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76073: 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. 
Feb  1 20:47:51 joe gdm-simple-slave[26054]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76074: 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. 
Feb  1 20:47:51 joe gdm-simple-slave[26055]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76075: 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. 
Feb  1 20:47:51 joe gdm-simple-slave[26062]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76076: 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. 
Feb  1 20:47:51 joe gdm-simple-slave[26063]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76077: 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. 
Feb  1 20:47:51 joe gdm-simple-slave[26064]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76078: 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. 
Feb  1 20:47:51 joe gdm-simple-slave[26065]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76079: 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. 
Feb  1 20:47:54 joe gdm-simple-slave[26066]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76080: 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. 
Feb  1 20:47:54 joe gdm-simple-slave[26067]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76081: 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. 
Feb  1 20:47:54 joe gdm-simple-slave[26068]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76082: 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. 
Feb  1 20:47:54 joe gdm-simple-slave[26069]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76083: 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. 
Feb  1 20:47:54 joe gdm-simple-slave[26070]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76084: 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. 
Feb  1 20:47:54 joe gdm-simple-slave[26071]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76085: 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. 
Feb  1 20:47:54 joe gdm-simple-slave[26072]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76086: 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. 
Feb  1 20:47:54 joe gdm-simple-slave[26073]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76087: 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. 
Feb  1 20:47:54 joe gdm-simple-slave[26074]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76088: 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. 
Feb  1 20:47:54 joe gdm-simple-slave[26075]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76089: 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. 
Feb  1 20:47:54 joe gdm-simple-slave[26076]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76090: 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. 
Feb  1 20:47:54 joe gdm-simple-slave[26077]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76091: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25631]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25628]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25630]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25629]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25634]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25642]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25636]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25638]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25637]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25639]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25632]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25633]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25640]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25641]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25635]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25662]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25653]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25652]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25654]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25661]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25660]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25659]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25658]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25656]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25655]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25663]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25690]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25698]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25697]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25691]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25696]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25692]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25693]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25694]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25700]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25701]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25695]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25643]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25688]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25651]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25647]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25644]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25699]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25702]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25646]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25648]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25649]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25664]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25650]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25689]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25645]: WARNING: Failed to get value: 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. 
Feb  1 20:48:16 joe gdm-simple-slave[25681]: WARNING: Failed to get value: 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. 
Feb  1 20:48:22 joe gdm-simple-slave[25617]: WARNING: Failed to get value: 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. 
Feb  1 20:48:22 joe gdm-simple-slave[25620]: WARNING: Failed to get value: 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. 
Feb  1 20:48:22 joe gdm-simple-slave[25619]: WARNING: Failed to get value: 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. 
Feb  1 20:48:22 joe gdm-simple-slave[25621]: WARNING: Failed to get value: 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. 
Feb  1 20:48:22 joe gdm-simple-slave[25623]: WARNING: Failed to get value: 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. 
Feb  1 20:48:22 joe gdm-simple-slave[25624]: WARNING: Failed to get value: 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. 
Feb  1 20:48:22 joe gdm-simple-slave[25622]: WARNING: Failed to get value: 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. 
Feb  1 20:48:22 joe gdm-simple-slave[25625]: WARNING: Failed to get value: 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. 
Feb  1 20:48:22 joe gdm-simple-slave[25626]: WARNING: Failed to get value: 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. 
Feb  1 20:48:22 joe gdm-simple-slave[25627]: WARNING: Failed to get value: 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. 
Feb  1 20:48:22 joe gdm-simple-slave[26504]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76277: 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. 
Feb  1 20:48:22 joe gdm-simple-slave[26505]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76278: 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. 
Feb  1 20:48:24 joe gdm-simple-slave[26539]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76290: 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. 
Feb  1 20:48:24 joe gdm-simple-slave[26540]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76291: 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. 
Feb  1 20:48:25 joe gdm-simple-slave[26541]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76292: 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. 
Feb  1 20:48:25 joe gdm-simple-slave[26542]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76293: 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. 
Feb  1 20:48:25 joe gdm-simple-slave[26543]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76294: 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. 
Feb  1 20:48:52 joe gdm-simple-slave[26863]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:52 joe gdm-simple-slave[26869]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:52 joe gdm-simple-slave[26876]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:52 joe gdm-simple-slave[26879]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:52 joe gdm-simple-slave[26882]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:52 joe gdm-simple-slave[26885]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:52 joe gdm-simple-slave[26888]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:52 joe gdm-simple-slave[26891]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:52 joe gdm-simple-slave[26897]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:52 joe gdm-simple-slave[26894]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:52 joe gdm-simple-slave[26900]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:52 joe gdm-simple-slave[26903]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26906]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26916]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26931]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26934]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26943]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26946]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26947]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26948]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26949]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26950]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26951]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26952]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26953]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26954]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26955]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26956]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26957]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26959]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26961]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26962]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26963]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26964]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26967]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26977]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26978]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26979]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26980]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26988]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[26998]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27005]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27006]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27007]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27008]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27009]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27010]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27011]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27012]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27013]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27014]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27015]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27016]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27017]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27018]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27019]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27020]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27021]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27022]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27023]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27024]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27025]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27026]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27027]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27028]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27029]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27030]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27031]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27032]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27033]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27034]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27036]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27035]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27037]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27038]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27039]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27040]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27042]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27041]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27043]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27044]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27045]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27046]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27047]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27048]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27245]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76494: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27246]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76495: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27247]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76496: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27248]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76497: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27249]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76498: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27250]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76499: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27251]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76500: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27252]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76501: 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. 
Feb  1 20:48:53 joe gdm-simple-slave[27253]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76502: 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. 
Feb  1 20:48:54 joe gdm-simple-slave[27254]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76503: 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. 
Feb  1 20:48:54 joe gdm-simple-slave[27255]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76504: 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. 
Feb  1 20:48:54 joe gdm-simple-slave[27256]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76505: 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. 
Feb  1 20:48:54 joe gdm-simple-slave[27257]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76506: 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. 
Feb  1 20:48:54 joe gdm-simple-slave[27258]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76507: 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. 
Feb  1 20:48:54 joe gdm-simple-slave[27259]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76508: 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. 
Feb  1 20:48:54 joe gdm-simple-slave[27260]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76509: 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. 
Feb  1 20:48:54 joe gdm-simple-slave[27261]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76510: 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. 
Feb  1 20:48:54 joe gdm-simple-slave[27262]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76511: 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. 
Feb  1 20:48:54 joe gdm-simple-slave[27263]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76512: 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. 
Feb  1 20:48:55 joe gdm-simple-slave[27264]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76513: 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. 
Feb  1 20:48:55 joe gdm-simple-slave[27269]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76514: 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. 
Feb  1 20:48:55 joe gdm-simple-slave[27273]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76515: 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. 
Feb  1 20:48:55 joe gdm-simple-slave[27283]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76516: 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. 
Feb  1 20:48:55 joe gdm-simple-slave[27290]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76517: 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. 
Feb  1 20:48:55 joe gdm-simple-slave[27291]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76518: 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. 
Feb  1 20:48:55 joe gdm-simple-slave[27292]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76519: 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. 
Feb  1 20:48:55 joe gdm-simple-slave[27293]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76520: 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. 
Feb  1 20:48:57 joe gdm-simple-slave[27294]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76521: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27295]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76522: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27296]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76523: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27297]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76524: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27298]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76525: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27299]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76526: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27300]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76527: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27301]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76528: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27302]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76529: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27303]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76530: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27304]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76531: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27305]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76532: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27306]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76533: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27307]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76534: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27309]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76536: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27308]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76535: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27310]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76537: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27311]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76538: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27312]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76539: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27313]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76540: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27314]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76541: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27315]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76542: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27316]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76543: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27317]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76544: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27318]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76545: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27319]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76546: 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. 
Feb  1 20:48:58 joe gdm-simple-slave[27320]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76547: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27321]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27322]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27323]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27324]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27325]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27326]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27327]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27328]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27329]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27330]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27331]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26863]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26885]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26876]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26869]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26888]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26879]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26882]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26948]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26949]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26950]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26951]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26894]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26891]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26980]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26988]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26998]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27005]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27006]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27007]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27008]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27009]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27010]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27021]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27022]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27023]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27024]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27025]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27026]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27027]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27028]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27029]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27030]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27031]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26979]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27012]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26977]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27011]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26967]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26964]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26978]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27333]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27334]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27335]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27332]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27019]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27016]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27013]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27015]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27044]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27045]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27046]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27020]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26903]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26934]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26931]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26900]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26943]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26897]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26916]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26946]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26906]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27032]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27033]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27034]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27036]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27035]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27037]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27038]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27039]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27040]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27041]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27042]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27043]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26959]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26955]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26961]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26954]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26957]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26953]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26962]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26963]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26952]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26956]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[26947]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27047]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27048]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27014]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27017]: WARNING: Failed to get value: 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. 
Feb  1 20:49:23 joe gdm-simple-slave[27018]: WARNING: Failed to get value: 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. 
Feb  1 20:49:25 joe gdm-simple-slave[27670]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76710: 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. 
Feb  1 20:49:25 joe gdm-simple-slave[27716]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76711: 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. 
Feb  1 20:49:25 joe gdm-simple-slave[27669]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76709: 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. 
Feb  1 20:49:25 joe gdm-simple-slave[27763]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76712: 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. 
Feb  1 20:49:25 joe gdm-simple-slave[27764]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76713: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27766]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76714: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27767]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76715: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27768]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76716: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27769]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76717: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27771]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76719: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27770]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76718: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27772]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76720: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27773]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76721: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27774]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76722: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27775]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76723: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27776]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76724: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27777]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76725: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27779]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76727: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27778]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76726: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27781]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76729: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27783]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76731: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27780]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76728: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27782]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76730: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27784]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76732: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27786]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76734: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27788]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76736: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27789]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76737: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27790]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76738: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27791]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76739: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27785]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76733: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27787]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76735: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27792]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76740: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27793]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76741: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27794]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76742: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27795]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76743: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27796]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76744: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27797]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76745: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27798]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76746: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27799]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76747: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27800]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76748: 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. 
Feb  1 20:49:26 joe gdm-simple-slave[27801]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76749: 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. 
Feb  1 20:49:27 joe gdm-simple-slave[27802]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76750: 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. 
Feb  1 20:49:27 joe gdm-simple-slave[27803]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76751: 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. 
Feb  1 20:49:27 joe gdm-simple-slave[27804]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76752: 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. 
Feb  1 20:49:27 joe gdm-simple-slave[27805]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76753: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[27321]: WARNING: Failed to get value: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[27322]: WARNING: Failed to get value: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[27323]: WARNING: Failed to get value: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[27324]: WARNING: Failed to get value: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[27325]: WARNING: Failed to get value: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[27327]: WARNING: Failed to get value: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[27326]: WARNING: Failed to get value: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[27328]: WARNING: Failed to get value: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[27329]: WARNING: Failed to get value: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[27330]: WARNING: Failed to get value: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[27331]: WARNING: Failed to get value: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[27333]: WARNING: Failed to get value: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[27334]: WARNING: Failed to get value: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[27335]: WARNING: Failed to get value: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[27332]: WARNING: Failed to get value: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[28525]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:49:48 joe gdm-simple-slave[28102]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76882: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[28121]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76883: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[28122]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76884: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[28131]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76885: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[28144]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76886: 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. 
Feb  1 20:49:48 joe gdm-simple-slave[28147]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76887: 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. 
Feb  1 20:49:49 joe gdm-simple-slave[28148]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76888: 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. 
Feb  1 20:49:49 joe gdm-simple-slave[28149]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76889: 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. 
Feb  1 20:49:50 joe gdm-simple-slave[28165]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display76898: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28662]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28663]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28675]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28676]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28677]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28686]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28678]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28702]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28703]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28704]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28705]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28706]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28707]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28710]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28711]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28712]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28713]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28719]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28721]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28725]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28738]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28742]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28777]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28786]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28799]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28780]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28804]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28796]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28821]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28820]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28819]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28818]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28817]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28816]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28783]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28789]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28810]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28811]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28814]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28822]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28823]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28824]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28825]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28826]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28827]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28828]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28829]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28830]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28831]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28832]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28833]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28834]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28838]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28852]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28859]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28860]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28861]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28862]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28863]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28873]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28864]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28872]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28865]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28871]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28866]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28870]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28867]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28868]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28869]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28874]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28875]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28885]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28876]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28884]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28877]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28883]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28878]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28882]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28881]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28880]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28879]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28886]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28887]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28888]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28889]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28890]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28891]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28892]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28893]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28894]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28895]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28896]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28897]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28898]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28899]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28900]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28901]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28902]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28903]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28905]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28906]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28907]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28908]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28909]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28910]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:50:24 joe gdm-simple-slave[28982]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77143: 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. 
Feb  1 20:50:25 joe gdm-simple-slave[28983]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77144: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[28984]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77145: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[28985]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77146: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[28986]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77147: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[28987]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77148: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[28988]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77149: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[28989]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77150: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[28990]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77151: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[28991]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77152: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[28992]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77153: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[28996]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77157: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[28993]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77154: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[28997]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77158: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[28994]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77155: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[28995]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77156: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[28998]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77159: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[28999]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77160: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[29000]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77161: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[29001]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77162: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[29003]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77163: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[29005]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77165: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[29004]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77164: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[29007]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77167: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[29006]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77166: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[29008]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77168: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[29009]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77169: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[29010]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77170: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[29011]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77171: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[29012]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77172: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[29013]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77173: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[29014]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77174: 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. 
Feb  1 20:50:27 joe gdm-simple-slave[29015]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77175: 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. 
Feb  1 20:50:28 joe gdm-simple-slave[29016]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77176: 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. 
Feb  1 20:50:28 joe gdm-simple-slave[29017]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77177: 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. 
Feb  1 20:50:28 joe gdm-simple-slave[29018]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77178: 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. 
Feb  1 20:50:28 joe gdm-simple-slave[29019]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77179: 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. 
Feb  1 20:50:28 joe gdm-simple-slave[29020]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77180: 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. 
Feb  1 20:50:28 joe gdm-simple-slave[29021]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77181: 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. 
Feb  1 20:50:28 joe gdm-simple-slave[29022]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77182: 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. 
Feb  1 20:50:28 joe gdm-simple-slave[29023]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77183: 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. 
Feb  1 20:50:28 joe gdm-simple-slave[29024]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77184: 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. 
Feb  1 20:50:28 joe gdm-simple-slave[29025]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77185: 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. 
Feb  1 20:50:28 joe gdm-simple-slave[29026]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77186: 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. 
Feb  1 20:50:29 joe gdm-simple-slave[29027]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77187: 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. 
Feb  1 20:50:29 joe gdm-simple-slave[29029]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77188: 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. 
Feb  1 20:50:29 joe gdm-simple-slave[29030]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77189: 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. 
Feb  1 20:50:29 joe gdm-simple-slave[29031]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77190: 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. 
Feb  1 20:50:29 joe gdm-simple-slave[29032]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77191: 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. 
Feb  1 20:50:36 joe gdm-simple-slave[29489]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:51:00 joe gdm-simple-slave[28662]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28663]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28675]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28676]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28677]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28678]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28686]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28702]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28703]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28704]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28705]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28706]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28707]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28710]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28711]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28712]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28713]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28719]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28721]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28725]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28738]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28742]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28777]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28780]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28786]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28799]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28796]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28804]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28816]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28817]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28818]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28819]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28820]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28821]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28783]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28789]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28810]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28811]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28814]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28822]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28823]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28824]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28825]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28826]: WARNING: Failed to get value: 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. 
Feb  1 20:51:00 joe gdm-simple-slave[28827]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28828]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28829]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28830]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28831]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28832]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28833]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28834]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28838]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28852]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28859]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28860]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28861]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28862]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28863]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28864]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28865]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28866]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28868]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28867]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28869]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28870]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28871]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28872]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28873]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28874]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28875]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28876]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28877]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28878]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28879]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28880]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28881]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28882]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28883]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28884]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28885]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28886]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28887]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28888]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28889]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28890]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28891]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28892]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28893]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28894]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28895]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28896]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28897]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28898]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28899]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28900]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28901]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28902]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28903]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28905]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28906]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28907]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28908]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28909]: WARNING: Failed to get value: 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. 
Feb  1 20:51:01 joe gdm-simple-slave[28910]: WARNING: Failed to get value: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29584]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77385: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29585]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77386: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29586]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77387: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29587]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77388: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29588]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77389: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29589]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77390: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29590]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77391: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29591]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77392: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29592]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77393: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29593]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77394: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29594]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77395: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29597]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77398: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29598]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77399: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29596]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77397: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29595]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77396: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29600]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77401: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29599]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77400: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29603]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77404: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29607]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77405: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29601]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77402: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29609]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77407: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29602]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77403: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29611]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77409: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29608]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77406: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29610]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77408: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29612]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77410: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29613]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77411: 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. 
Feb  1 20:51:03 joe gdm-simple-slave[29614]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77412: 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. 
Feb  1 20:51:04 joe gdm-simple-slave[29615]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77413: 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. 
Feb  1 20:51:04 joe gdm-simple-slave[29616]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77414: 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. 
Feb  1 20:51:04 joe gdm-simple-slave[29617]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77415: 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. 
Feb  1 20:51:04 joe gdm-simple-slave[29618]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77416: 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. 
Feb  1 20:51:04 joe gdm-simple-slave[29619]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77417: 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. 
Feb  1 20:51:04 joe gdm-simple-slave[29620]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77418: 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. 
Feb  1 20:51:04 joe gdm-simple-slave[29621]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77419: 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. 
Feb  1 20:51:04 joe gdm-simple-slave[29622]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77420: 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. 
Feb  1 20:51:04 joe gdm-simple-slave[29623]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77421: 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. 
Feb  1 20:51:04 joe gdm-simple-slave[29624]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77422: 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. 
Feb  1 20:51:04 joe gdm-simple-slave[29625]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77423: 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. 
Feb  1 20:51:04 joe gdm-simple-slave[29626]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77424: 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. 
Feb  1 20:51:05 joe gdm-simple-slave[29627]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77425: 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. 
Feb  1 20:51:05 joe gdm-simple-slave[29628]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77426: 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. 
Feb  1 20:51:05 joe gdm-simple-slave[29630]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77427: 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. 
Feb  1 20:51:05 joe gdm-simple-slave[29631]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77428: 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. 
Feb  1 20:51:05 joe gdm-simple-slave[29632]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77429: 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. 
Feb  1 20:51:05 joe gdm-simple-slave[29633]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77430: 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. 
Feb  1 20:51:05 joe gdm-simple-slave[29634]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77431: 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. 
Feb  1 20:51:05 joe gdm-simple-slave[29642]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77432: 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. 
Feb  1 20:51:05 joe gdm-simple-slave[29652]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77433: 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. 
Feb  1 20:51:32 joe gnome-session[3441]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.  
Feb  1 20:52:03 joe gdm-simple-slave[30547]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77714: 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. 
Feb  1 20:52:03 joe gdm-simple-slave[30541]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77711: 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. 
Feb  1 20:52:03 joe gdm-simple-slave[30530]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77706: 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. 
Feb  1 20:52:03 joe gdm-simple-slave[30512]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77704: 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. 
Feb  1 20:52:03 joe gdm-simple-slave[30546]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77713: 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. 
Feb  1 20:52:03 joe gdm-simple-slave[30538]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77708: 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. 
Feb  1 20:52:03 joe gdm-simple-slave[30542]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77712: 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. 
Feb  1 20:52:03 joe gdm-simple-slave[30537]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77707: 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. 
Feb  1 20:52:03 joe gdm-simple-slave[30548]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77715: 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. 
Feb  1 20:52:03 joe gdm-simple-slave[30511]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77703: 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. 
Feb  1 20:52:03 joe gdm-simple-slave[30552]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77717: 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. 
Feb  1 20:52:03 joe gdm-simple-slave[30549]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77716: 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. 
Feb  1 20:52:03 joe gdm-simple-slave[30539]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77709: 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. 
Feb  1 20:52:03 joe gdm-simple-slave[30540]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77710: 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. 
Feb  1 20:52:03 joe gdm-simple-slave[30516]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77705: 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. 
Feb  1 20:52:03 joe gdm-simple-slave[30510]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77702: 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. 
Feb  1 20:52:03 joe gdm-simple-slave[30597]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:52:04 joe acpid: client connected from 30597[0:0]
Feb  1 20:52:04 joe acpid: 1 client rule loaded
Feb  1 20:52:08 joe gdm[30773]: ******************* START **********************************
Feb  1 20:52:12 joe gdm[30773]: [Thread debugging using libthread_db enabled]
Feb  1 20:52:12 joe gdm[30773]: [New Thread 0xf6d42b70 (LWP 30703)]
Feb  1 20:52:15 joe gdm[30773]: 0xf77d5425 in __kernel_vsyscall ()
Feb  1 20:52:15 joe gdm[30773]: #0  0xf77d5425 in __kernel_vsyscall ()
Feb  1 20:52:15 joe gdm[30773]: #1  0xf75bf1eb in waitpid () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:52:15 joe gdm[30773]: #2  0x08067a25 in ?? ()
Feb  1 20:52:15 joe gdm[30773]: #3  0x08067e39 in ?? ()
Feb  1 20:52:15 joe gdm[30773]: #4  <signal handler called>
Feb  1 20:52:15 joe gdm[30773]: #5  0x0805f5bf in ?? ()
Feb  1 20:52:15 joe gdm[30773]: #6  0x08063248 in ?? ()
Feb  1 20:52:16 joe gdm[30773]: #7  0xf7348270 in g_idle_dispatch (source=0xa073688, callback=0x8063220, user_data=0xa07b000) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4776
Feb  1 20:52:16 joe gdm[30773]: #8  0xf734ba3f in g_main_dispatch (context=0xa0739c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2442
Feb  1 20:52:16 joe gdm[30773]: #9  g_main_context_dispatch (context=0xa0739c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2998
Feb  1 20:52:16 joe gdm[30773]: #10 0xf734c170 in g_main_context_iterate (context=0xa0739c0, block=-147477808, dispatch=1, self=<optimized out>) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3076
Feb  1 20:52:16 joe gdm[30773]: #11 0xf734c77b in g_main_loop_run (loop=0xa078740) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3284
Feb  1 20:52:16 joe gdm[30773]: #12 0x0804dfa1 in ?? ()
Feb  1 20:52:16 joe gdm[30773]: #13 0xf7167e46 in __libc_start_main (main=0x804dc70, argc=3, ubp_av=0xffa9f284, init=0x80695d0, fini=0x80695c0, rtld_fini=0xf77e4310, stack_end=0xffa9f27c) at libc-start.c:228
Feb  1 20:52:16 joe gdm[30773]: #14 0x0804e0a9 in ?? ()
Feb  1 20:52:16 joe gdm[30773]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:52:16 joe gdm[30773]: 
Feb  1 20:52:16 joe gdm[30773]: Thread 2 (Thread 0xf6d42b70 (LWP 30703)):
Feb  1 20:52:16 joe gdm[30773]: #0  0xf77d5425 in __kernel_vsyscall ()
Feb  1 20:52:16 joe gdm[30773]: No symbol table info available.
Feb  1 20:52:16 joe gdm[30773]: #1  0xf75be33b in read () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:52:16 joe gdm[30773]: No locals.
Feb  1 20:52:16 joe gdm[30773]: #2  0xf734760b in unix_signal_helper_thread (data=0x0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4542
Feb  1 20:52:16 joe gdm[30773]:         i = <optimized out>
Feb  1 20:52:16 joe gdm[30773]:         bytes_read = <optimized out>
Feb  1 20:52:16 joe gdm[30773]: 
Feb  1 20:52:16 joe gdm[30773]:         sigterm_received = 0
Feb  1 20:52:16 joe gdm[30773]:         sigint_received = 0
Feb  1 20:52:16 joe gdm[30773]: 
Feb  1 20:52:16 joe gdm[30773]: #3  0xf7372dd4 in g_thread_create_proxy (data=0xa07cc38) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gthread.c:1962
Feb  1 20:52:16 joe gdm[30773]:         thread = 0xa07cc38
Feb  1 20:52:16 joe gdm[30773]: 
Feb  1 20:52:16 joe gdm[30773]: #4  0xf75b6c39 in start_thread (arg=0xf6d42b70) at pthread_create.c:304
Feb  1 20:52:16 joe gdm[30773]:         __res = <optimized out>
Feb  1 20:52:16 joe gdm[30773]:         __ignore1 = <optimized out>
Feb  1 20:52:16 joe gdm[30773]:         __ignore2 = <optimized out>
Feb  1 20:52:16 joe gdm[30773]:         pd = 0xf6d42b70
Feb  1 20:52:16 joe gdm[30773]:         now = <optimized out>
Feb  1 20:52:16 joe gdm[30773]: 
Feb  1 20:52:16 joe gdm[30773]:         not_first_call = <optimized out>
Feb  1 20:52:16 joe gdm[30773]:         freesize = <optimized out>
Feb  1 20:52:16 joe gdm[30773]: 
Feb  1 20:52:16 joe gdm[30773]: #5  0xf722112e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Feb  1 20:52:16 joe gdm[30773]: No locals.
Feb  1 20:52:16 joe gdm[30773]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:52:16 joe gdm[30773]: 
Feb  1 20:52:16 joe gdm[30773]: Thread 1 (Thread 0xf6ebaac0 (LWP 29633)):
Feb  1 20:52:16 joe gdm[30773]: #0  0xf77d5425 in __kernel_vsyscall ()
Feb  1 20:52:16 joe gdm[30773]: No symbol table info available.
Feb  1 20:52:16 joe gdm[30773]: #1  0xf75bf1eb in waitpid () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:52:16 joe gdm[30773]: No locals.
Feb  1 20:52:16 joe gdm[30773]: #2  0x08067a25 in ?? ()
Feb  1 20:52:16 joe gdm[30773]: No symbol table info available.
Feb  1 20:52:16 joe gdm[30773]: #3  0x08067e39 in ?? ()
Feb  1 20:52:16 joe gdm[30773]: No symbol table info available.
Feb  1 20:52:16 joe gdm[30773]: #4  <signal handler called>
Feb  1 20:52:16 joe gdm[30773]: No symbol table info available.
Feb  1 20:52:16 joe gdm[30773]: #5  0x0805f5bf in ?? ()
Feb  1 20:52:16 joe gdm[30773]: No symbol table info available.
Feb  1 20:52:16 joe gdm[30773]: #6  0x08063248 in ?? ()
Feb  1 20:52:16 joe gdm[30773]: No symbol table info available.
Feb  1 20:52:16 joe gdm[30773]: #7  0xf7348270 in g_idle_dispatch (source=0xa073688, callback=0x8063220, user_data=0xa07b000) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4776
Feb  1 20:52:16 joe gdm[30773]: No locals.
Feb  1 20:52:16 joe gdm[30773]: #8  0xf734ba3f in g_main_dispatch (context=0xa0739c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2442
Feb  1 20:52:16 joe gdm[30773]:         dispatch = 0xf7348250 <g_idle_dispatch>
Feb  1 20:52:16 joe gdm[30773]:         was_in_call = 0
Feb  1 20:52:16 joe gdm[30773]:         user_data = 0xa07b000
Feb  1 20:52:16 joe gdm[30773]:  callback = 0x8063220
Feb  1 20:52:16 joe gdm[30773]:         cb_funcs = 0xf740071c
Feb  1 20:52:16 joe gdm[30773]:         cb_data = 0xa07cfc8
Feb  1 20:52:16 joe gdm[30773]:         current_source_link = {data = 0xa073688, next = 0x0}
Feb  1 20:52:16 joe gdm[30773]:         need_destroy = <optimized out>
Feb  1 20:52:16 joe gdm[30773]:         source = 0xa073688
Feb  1 20:52:16 joe gdm[30773]:         current = 0xa07aaa0
Feb  1 20:52:16 joe gdm[30773]: ed out>
Feb  1 20:52:16 joe gdm[30773]: #9  g_main_context_dispatch (context=0xa0739c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2998
Feb  1 20:52:16 joe gdm[30773]: No locals.
Feb  1 20:52:16 joe gdm[30773]: out>) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3076
Feb  1 20:52:16 joe gdm[30773]:         max_priority = 200
Feb  1 20:52:16 joe gdm[30773]:         timeout = 0
Feb  1 20:52:16 joe gdm[30773]:         some_ready = 1
Feb  1 20:52:16 joe gdm[30773]:         nfds = <optimized out>
Feb  1 20:52:16 joe gdm[30773]:         allocated_nfds = <optimized out>
Feb  1 20:52:16 joe gdm[30773]:         fds = 0xa07ccb0
Feb  1 20:52:16 joe gdm[30773]: 1 0xf734c77b in g_main_loop_run (loop=0xa078740) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3284
Feb  1 20:52:16 joe gdm[30773]:         __PRETTY_FUNCTION__ = "g_main_loop_run"
Feb  1 20:52:16 joe gdm[30773]: #12 0x0804dfa1 in ?? ()
Feb  1 20:52:16 joe gdm[30773]: No symbol table info available.
Feb  1 20:52:16 joe gdm[30773]: ibc_start_main (main=0x804dc70, argc=3, ubp_av=0xffa9f284, init=0x80695d0, fini=0x80695c0, rtld_fini=0xf77e4310, stack_end=0xffa9f27c) at libc-start.c:228
Feb  1 20:52:16 joe gdm[30773]:         result = <optimized out>
Feb  1 20:52:16 joe gdm[30773]: 0, -5639592, 896936073, 1248460440}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x3, 0x804e088}, data = {prev = 0x0, cleanup = 0x0, canceltype = 3}}}
Feb  1 20:52:16 joe gdm[30773]:         not_first_call = <optimized out>
Feb  1 20:52:16 joe gdm[30773]: #14 0x0804e0a9 in ?? ()
Feb  1 20:52:16 joe gdm[30773]: No symbol table info available.
Feb  1 20:52:16 joe gdm[30773]: trace stopped: Not enough registers or memory available to unwind further
Feb  1 20:52:16 joe gdm[30773]: A debugging session is active.
Feb  1 20:52:16 joe gdm[30773]: 
Feb  1 20:52:16 joe gdm[30773]: ^IInferior 1 [process 29633] will be detached.
Feb  1 20:52:16 joe gdm[30773]: 
Feb  1 20:52:16 joe gdm[30773]: Quit anyway? (y or n) [answered Y; input not from terminal]
Feb  1 20:52:16 joe gdm[30773]: ******************* END **********************************
Feb  1 20:52:37 joe gdm-simple-slave[30559]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30671]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30675]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30674]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30673]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30686]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30685]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30684]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30683]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30682]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30681]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30672]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30676]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30680]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30693]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30690]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30689]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30688]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30687]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30679]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30678]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30677]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30691]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30692]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30696]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30700]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30723]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30724]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30694]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30695]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30697]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30698]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30699]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30736]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30725]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30701]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30735]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30702]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30719]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30734]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30721]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30726]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30722]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30728]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30739]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30740]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30733]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30741]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30727]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30742]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30732]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30731]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30729]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30737]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30738]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30747]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30746]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30749]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30754]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30757]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30761]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30745]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30744]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30743]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30748]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30750]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30752]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30759]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30758]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30760]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30765]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30767]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30762]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30768]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30766]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30764]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30769]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30772]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30776]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30807]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30806]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30790]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30782]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30781]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30780]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30779]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30778]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30777]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30775]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30771]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30808]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30811]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30819]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30818]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30817]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30816]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30815]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30814]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30813]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30812]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30810]: WARNING: Failed to set slave bus name on parent: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30855]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77819: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30856]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77820: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30857]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77821: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30858]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77822: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30859]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77823: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30860]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77824: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30861]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77825: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30862]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77826: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30863]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77827: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30864]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77828: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30865]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77829: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30866]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77830: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30867]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77831: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30868]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77832: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30869]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77833: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30870]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77834: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30871]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77835: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30872]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77836: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30873]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77837: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30874]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77838: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30875]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77839: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30876]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77840: 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. 
Feb  1 20:52:37 joe gdm-simple-slave[30877]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77841: 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. 
Feb  1 20:52:38 joe gdm-simple-slave[30878]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77842: 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. 
Feb  1 20:52:38 joe gdm-simple-slave[30879]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77843: 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. 
Feb  1 20:52:38 joe gdm-simple-slave[30880]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77844: 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. 
Feb  1 20:52:38 joe gdm-simple-slave[30881]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77845: 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. 
Feb  1 20:52:38 joe gdm-simple-slave[30882]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77846: 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. 
Feb  1 20:52:38 joe gdm-simple-slave[30883]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77847: 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. 
Feb  1 20:52:38 joe gdm-simple-slave[30885]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77849: 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. 
Feb  1 20:52:38 joe gdm-simple-slave[30884]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77848: 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. 
Feb  1 20:52:38 joe gdm-simple-slave[30886]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77850: 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. 
Feb  1 20:52:38 joe gdm-simple-slave[30887]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77851: 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. 
Feb  1 20:52:39 joe gdm-simple-slave[30888]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77852: 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. 
Feb  1 20:52:39 joe gdm-simple-slave[30889]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77853: 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. 
Feb  1 20:52:39 joe gdm-simple-slave[30890]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77854: 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. 
Feb  1 20:52:39 joe gdm-simple-slave[30891]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77855: 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. 
Feb  1 20:52:39 joe gdm-simple-slave[30908]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77856: 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. 
Feb  1 20:52:39 joe gdm-simple-slave[30913]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77857: 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. 
Feb  1 20:52:39 joe gdm-simple-slave[30916]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77858: 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. 
Feb  1 20:52:39 joe gdm-simple-slave[30917]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77859: 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. 
Feb  1 20:52:39 joe gdm-simple-slave[30918]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77860: 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. 
Feb  1 20:52:39 joe gdm-simple-slave[30919]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77861: 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. 
Feb  1 20:52:39 joe gdm-simple-slave[30920]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77862: 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. 
Feb  1 20:52:40 joe gdm-simple-slave[30921]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77863: 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. 
Feb  1 20:52:40 joe gdm-simple-slave[30922]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77864: 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. 
Feb  1 20:52:41 joe gdm-simple-slave[30923]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77865: 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. 
Feb  1 20:52:41 joe gdm-simple-slave[30924]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77866: 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. 
Feb  1 20:52:41 joe gdm-simple-slave[30925]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77867: 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. 
Feb  1 20:52:41 joe gdm-simple-slave[30926]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77868: 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. 
Feb  1 20:52:41 joe gdm-simple-slave[30927]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77869: 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. 
Feb  1 20:52:41 joe gdm-simple-slave[30928]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77870: 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. 
Feb  1 20:52:41 joe gdm-simple-slave[30929]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77871: 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. 
Feb  1 20:52:41 joe gdm-simple-slave[30930]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77872: 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. 
Feb  1 20:52:41 joe gdm-simple-slave[30931]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77873: 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. 
Feb  1 20:52:41 joe gdm-simple-slave[30935]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display77875: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30689]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30691]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30694]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30700]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30692]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30723]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30695]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30724]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30696]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30725]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30697]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30701]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30739]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30740]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30733]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30702]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30726]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30741]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30742]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30727]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30728]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30737]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30746]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30743]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30738]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30729]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30761]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30744]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30750]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30732]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30747]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30731]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30749]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30745]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30754]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30752]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30757]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30748]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30759]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30768]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30767]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30765]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30760]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30758]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30807]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30780]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30772]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30764]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30781]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30766]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30777]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30762]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30806]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30776]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30769]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30819]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30775]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30778]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30790]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30808]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30782]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30817]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30818]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30811]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30771]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30779]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30813]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30814]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30815]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30816]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30810]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30812]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30721]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30698]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30722]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30699]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30736]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30719]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30734]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe gdm-simple-slave[30735]: WARNING: Failed to get value: 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. 
Feb  1 20:53:02 joe acpid: client 30597[0:0] has disconnected
Feb  1 20:53:02 joe acpid: client connected from 31598[0:0]
Feb  1 20:53:02 joe acpid: 1 client rule loaded
Feb  1 20:53:03 joe gdm[31676]: ******************* START **********************************
Feb  1 20:53:04 joe gdm[31676]: [Thread debugging using libthread_db enabled]
Feb  1 20:53:04 joe gdm[31676]: [New Thread 0xf6c8ab70 (LWP 31602)]
Feb  1 20:53:05 joe gdm[31676]: 0xf771d425 in __kernel_vsyscall ()
Feb  1 20:53:05 joe gdm[31676]: #0  0xf771d425 in __kernel_vsyscall ()
Feb  1 20:53:05 joe gdm[31676]: #1  0xf75071eb in waitpid () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:53:05 joe gdm[31676]: #2  0x08067a25 in ?? ()
Feb  1 20:53:05 joe gdm[31676]: #3  0x08067e39 in ?? ()
Feb  1 20:53:05 joe gdm[31676]: #4  <signal handler called>
Feb  1 20:53:05 joe gdm[31676]: #5  0x0805f5bf in ?? ()
Feb  1 20:53:05 joe gdm[31676]: #6  0x08063248 in ?? ()
Feb  1 20:53:05 joe gdm[31676]: #7  0xf7290270 in g_idle_dispatch (source=0x80f1600, callback=0x8063220, user_data=0x80f9000) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4776
Feb  1 20:53:05 joe gdm[31676]: #8  0xf7293a3f in g_main_dispatch (context=0x80f19c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2442
Feb  1 20:53:05 joe gdm[31676]: #9  g_main_context_dispatch (context=0x80f19c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2998
Feb  1 20:53:05 joe gdm[31676]: #10 0xf7294170 in g_main_context_iterate (context=0x80f19c0, block=-148231472, dispatch=1, self=<optimized out>) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3076
Feb  1 20:53:05 joe gdm[31676]: #11 0xf729477b in g_main_loop_run (loop=0x80f6740) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3284
Feb  1 20:53:05 joe gdm[31676]: #12 0x0804dfa1 in ?? ()
Feb  1 20:53:05 joe gdm[31676]: #13 0xf70afe46 in __libc_start_main (main=0x804dc70, argc=3, ubp_av=0xffe14c64, init=0x80695d0, fini=0x80695c0, rtld_fini=0xf772c310, stack_end=0xffe14c5c) at libc-start.c:228
Feb  1 20:53:05 joe gdm[31676]: #14 0x0804e0a9 in ?? ()
Feb  1 20:53:05 joe gdm[31676]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:53:05 joe gdm[31676]: 
Feb  1 20:53:05 joe gdm[31676]: Thread 2 (Thread 0xf6c8ab70 (LWP 31602)):
Feb  1 20:53:05 joe gdm[31676]: #0  0xf771d425 in __kernel_vsyscall ()
Feb  1 20:53:05 joe gdm[31676]: No symbol table info available.
Feb  1 20:53:05 joe gdm[31676]: #1  0xf750633b in read () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:53:05 joe gdm[31676]: No locals.
Feb  1 20:53:05 joe gdm[31676]: #2  0xf728f60b in unix_signal_helper_thread (data=0x0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4542
Feb  1 20:53:05 joe gdm[31676]:         i = <optimized out>
Feb  1 20:53:05 joe gdm[31676]:         bytes_read = <optimized out>
Feb  1 20:53:05 joe gdm[31676]: 
Feb  1 20:53:05 joe last message repeated 3 times
Feb  1 20:53:05 joe gdm[31676]: #3  0xf72badd4 in g_thread_create_proxy (data=0x80fac38) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gthread.c:1962
Feb  1 20:53:05 joe gdm[31676]:         thread = 0x80fac38
Feb  1 20:53:05 joe gdm[31676]: 
Feb  1 20:53:05 joe gdm[31676]: #4  0xf74fec39 in start_thread (arg=0xf6c8ab70) at pthread_create.c:304
Feb  1 20:53:05 joe gdm[31676]:         __res = <optimized out>
Feb  1 20:53:05 joe gdm[31676]:         __ignore1 = <optimized out>
Feb  1 20:53:05 joe gdm[31676]:         __ignore2 = <optimized out>
Feb  1 20:53:05 joe gdm[31676]:         pd = 0xf6c8ab70
Feb  1 20:53:05 joe gdm[31676]:         now = <optimized out>
Feb  1 20:53:05 joe gdm[31676]: 
Feb  1 20:53:05 joe gdm[31676]:         not_first_call = <optimized out>
Feb  1 20:53:05 joe gdm[31676]:         freesize = <optimized out>
Feb  1 20:53:05 joe gdm[31676]: 
Feb  1 20:53:05 joe gdm[31676]: #5  0xf716912e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Feb  1 20:53:05 joe gdm[31676]: No locals.
Feb  1 20:53:05 joe gdm[31676]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:53:05 joe gdm[31676]: 
Feb  1 20:53:05 joe gdm[31676]: Thread 1 (Thread 0xf6e02ac0 (LWP 30855)):
Feb  1 20:53:05 joe gdm[31676]: #0  0xf771d425 in __kernel_vsyscall ()
Feb  1 20:53:05 joe gdm[31676]: No symbol table info available.
Feb  1 20:53:05 joe gdm[31676]: #1  0xf75071eb in waitpid () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:53:05 joe gdm[31676]: No locals.
Feb  1 20:53:05 joe gdm[31676]: #2  0x08067a25 in ?? ()
Feb  1 20:53:05 joe gdm[31676]: No symbol table info available.
Feb  1 20:53:05 joe gdm[31676]: #3  0x08067e39 in ?? ()
Feb  1 20:53:05 joe gdm[31676]: No symbol table info available.
Feb  1 20:53:05 joe gdm[31676]: #4  <signal handler called>
Feb  1 20:53:05 joe gdm[31676]: No symbol table info available.
Feb  1 20:53:05 joe gdm[31676]: #5  0x0805f5bf in ?? ()
Feb  1 20:53:05 joe gdm[31676]: No symbol table info available.
Feb  1 20:53:05 joe gdm[31676]: #6  0x08063248 in ?? ()
Feb  1 20:53:05 joe gdm[31676]: No symbol table info available.
Feb  1 20:53:05 joe gdm[31676]: #7  0xf7290270 in g_idle_dispatch (source=0x80f1600, callback=0x8063220, user_data=0x80f9000) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4776
Feb  1 20:53:05 joe gdm[31676]: No locals.
Feb  1 20:53:05 joe gdm[31676]: #8  0xf7293a3f in g_main_dispatch (context=0x80f19c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2442
Feb  1 20:53:05 joe gdm[31676]:         dispatch = 0xf7290250 <g_idle_dispatch>
Feb  1 20:53:05 joe gdm[31676]: 
Feb  1 20:53:05 joe gdm[31676]:         user_data = 0x80f9000
Feb  1 20:53:05 joe gdm[31676]:         callback = 0x8063220
Feb  1 20:53:05 joe gdm[31676]:         cb_funcs = 0xf734871c
Feb  1 20:53:05 joe gdm[31676]:         cb_data = 0x80fa398
Feb  1 20:53:05 joe gdm[31676]: 
Feb  1 20:53:05 joe gdm[31676]:         need_destroy = <optimized out>
Feb  1 20:53:05 joe gdm[31676]:         source = 0x80f1600
Feb  1 20:53:05 joe gdm[31676]:         current = 0x80f8aa0
Feb  1 20:53:05 joe gdm[31676]:         i = <optimized out>
Feb  1 20:53:05 joe gdm[31676]: #9  g_main_context_dispatch (context=0x80f19c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2998
Feb  1 20:53:05 joe gdm[31676]: No locals.
Feb  1 20:53:05 joe gdm[31676]: #10 0xf7294170 in g_main_context_iterate (context=0x80f19c0, block=-148231472, dispatch=1, self=<optimized out>) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3076
Feb  1 20:53:05 joe gdm[31676]: 
Feb  1 20:53:05 joe last message repeated 2 times
Feb  1 20:53:05 joe gdm[31676]:         nfds = <optimized out>
Feb  1 20:53:05 joe gdm[31676]:         allocated_nfds = <optimized out>
Feb  1 20:53:05 joe gdm[31676]:         fds = 0x80facb0
Feb  1 20:53:05 joe gdm[31676]: #11 0xf729477b in g_main_loop_run (loop=0x80f6740) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3284
Feb  1 20:53:05 joe gdm[31676]: 
Feb  1 20:53:05 joe gdm[31676]: #12 0x0804dfa1 in ?? ()
Feb  1 20:53:05 joe gdm[31676]: No symbol table info available.
Feb  1 20:53:05 joe gdm[31676]: #13 0xf70afe46 in __libc_start_main (main=0x804dc70, argc=3, ubp_av=0xffe14c64, init=0x80695d0, fini=0x80695c0, rtld_fini=0xf772c310, stack_end=0xffe14c5c) at libc-start.c:228
Feb  1 20:53:05 joe gdm[31676]:         result = <optimized out>
Feb  1 20:53:05 joe gdm[31676]: 
Feb  1 20:53:05 joe gdm[31676]:         not_first_call = <optimized out>
Feb  1 20:53:05 joe gdm[31676]: #14 0x0804e0a9 in ?? ()
Feb  1 20:53:05 joe gdm[31676]: No symbol table info available.
Feb  1 20:53:05 joe gdm[31676]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:53:05 joe gdm[31676]: A debugging session is active.
Feb  1 20:53:05 joe gdm[31676]: 
Feb  1 20:53:05 joe gdm[31676]: ^IInferior 1 [process 30855] will be detached.
Feb  1 20:53:05 joe gdm[31676]: 
Feb  1 20:53:05 joe gdm[31676]: Quit anyway? (y or n) [answered Y; input not from terminal]
Feb  1 20:53:05 joe gdm[31676]: ******************* END **********************************
Feb  1 20:53:05 joe acpid: client 31598[0:0] has disconnected
Feb  1 20:53:05 joe acpid: client connected from 31730[0:0]
Feb  1 20:53:05 joe acpid: 1 client rule loaded
Feb  1 20:53:07 joe gdm[31788]: ******************* START **********************************
Feb  1 20:53:07 joe gdm[31788]: [Thread debugging using libthread_db enabled]
Feb  1 20:53:07 joe gdm[31788]: [New Thread 0xf6c93b70 (LWP 31732)]
Feb  1 20:53:07 joe gdm[31788]: 0xf7726425 in __kernel_vsyscall ()
Feb  1 20:53:07 joe gdm[31788]: #0  0xf7726425 in __kernel_vsyscall ()
Feb  1 20:53:07 joe gdm[31788]: #1  0xf75101eb in waitpid () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:53:07 joe gdm[31788]: #2  0x08067a25 in ?? ()
Feb  1 20:53:07 joe gdm[31788]: #3  0x08067e39 in ?? ()
Feb  1 20:53:07 joe gdm[31788]: #4  <signal handler called>
Feb  1 20:53:07 joe gdm[31788]: #5  0x0805f5bf in ?? ()
Feb  1 20:53:07 joe gdm[31788]: #6  0x08063248 in ?? ()
Feb  1 20:53:07 joe gdm[31788]: #7  0xf7299270 in g_idle_dispatch (source=0x990b600, callback=0x8063220, user_data=0x9913000) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4776
Feb  1 20:53:07 joe gdm[31788]: #8  0xf729ca3f in g_main_dispatch (context=0x990b6f0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2442
Feb  1 20:53:07 joe gdm[31788]: #9  g_main_context_dispatch (context=0x990b6f0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2998
Feb  1 20:53:07 joe gdm[31788]: #10 0xf729d170 in g_main_context_iterate (context=0x990b6f0, block=-148194608, dispatch=1, self=<optimized out>) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3076
Feb  1 20:53:07 joe gdm[31788]: #11 0xf729d77b in g_main_loop_run (loop=0x9910440) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3284
Feb  1 20:53:07 joe gdm[31788]: #12 0x0804dfa1 in ?? ()
Feb  1 20:53:07 joe gdm[31788]: #13 0xf70b8e46 in __libc_start_main (main=0x804dc70, argc=3, ubp_av=0xffc213b4, init=0x80695d0, fini=0x80695c0, rtld_fini=0xf7735310, stack_end=0xffc213ac) at libc-start.c:228
Feb  1 20:53:07 joe gdm[31788]: #14 0x0804e0a9 in ?? ()
Feb  1 20:53:07 joe gdm[31788]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:53:07 joe gdm[31788]: 
Feb  1 20:53:07 joe gdm[31788]: Thread 2 (Thread 0xf6c93b70 (LWP 31732)):
Feb  1 20:53:07 joe gdm[31788]: #0  0xf7726425 in __kernel_vsyscall ()
Feb  1 20:53:07 joe gdm[31788]: No symbol table info available.
Feb  1 20:53:07 joe gdm[31788]: #1  0xf750f33b in read () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:53:07 joe gdm[31788]: No locals.
Feb  1 20:53:07 joe gdm[31788]: #2  0xf729860b in unix_signal_helper_thread (data=0x0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4542
Feb  1 20:53:07 joe gdm[31788]:         i = <optimized out>
Feb  1 20:53:07 joe gdm[31788]:         bytes_read = <optimized out>
Feb  1 20:53:07 joe gdm[31788]: 
Feb  1 20:53:07 joe last message repeated 3 times
Feb  1 20:53:07 joe gdm[31788]: #3  0xf72c3dd4 in g_thread_create_proxy (data=0x9914c38) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gthread.c:1962
Feb  1 20:53:07 joe gdm[31788]:         thread = 0x9914c38
Feb  1 20:53:07 joe gdm[31788]: 
Feb  1 20:53:07 joe gdm[31788]: #4  0xf7507c39 in start_thread (arg=0xf6c93b70) at pthread_create.c:304
Feb  1 20:53:07 joe gdm[31788]:         __res = <optimized out>
Feb  1 20:53:07 joe gdm[31788]:         __ignore1 = <optimized out>
Feb  1 20:53:07 joe gdm[31788]:         __ignore2 = <optimized out>
Feb  1 20:53:07 joe gdm[31788]:         pd = 0xf6c93b70
Feb  1 20:53:07 joe gdm[31788]:         now = <optimized out>
Feb  1 20:53:07 joe gdm[31788]: 
Feb  1 20:53:07 joe gdm[31788]:         not_first_call = <optimized out>
Feb  1 20:53:07 joe gdm[31788]:         freesize = <optimized out>
Feb  1 20:53:07 joe gdm[31788]: 
Feb  1 20:53:07 joe gdm[31788]: #5  0xf717212e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Feb  1 20:53:07 joe gdm[31788]: No locals.
Feb  1 20:53:07 joe gdm[31788]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:53:07 joe gdm[31788]: 
Feb  1 20:53:07 joe gdm[31788]: Thread 1 (Thread 0xf6e0bac0 (LWP 30924)):
Feb  1 20:53:07 joe gdm[31788]: #0  0xf7726425 in __kernel_vsyscall ()
Feb  1 20:53:07 joe gdm[31788]: No symbol table info available.
Feb  1 20:53:07 joe gdm[31788]: #1  0xf75101eb in waitpid () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:53:07 joe gdm[31788]: No locals.
Feb  1 20:53:07 joe gdm[31788]: #2  0x08067a25 in ?? ()
Feb  1 20:53:07 joe gdm[31788]: No symbol table info available.
Feb  1 20:53:07 joe gdm[31788]: #3  0x08067e39 in ?? ()
Feb  1 20:53:07 joe gdm[31788]: No symbol table info available.
Feb  1 20:53:07 joe gdm[31788]: #4  <signal handler called>
Feb  1 20:53:07 joe gdm[31788]: No symbol table info available.
Feb  1 20:53:07 joe gdm[31788]: #5  0x0805f5bf in ?? ()
Feb  1 20:53:07 joe gdm[31788]: No symbol table info available.
Feb  1 20:53:07 joe gdm[31788]: #6  0x08063248 in ?? ()
Feb  1 20:53:07 joe gdm[31788]: No symbol table info available.
Feb  1 20:53:07 joe gdm[31788]: #7  0xf7299270 in g_idle_dispatch (source=0x990b600, callback=0x8063220, user_data=0x9913000) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4776
Feb  1 20:53:07 joe gdm[31788]: No locals.
Feb  1 20:53:07 joe gdm[31788]: #8  0xf729ca3f in g_main_dispatch (context=0x990b6f0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2442
Feb  1 20:53:07 joe gdm[31788]:         dispatch = 0xf7299250 <g_idle_dispatch>
Feb  1 20:53:07 joe gdm[31788]: 
Feb  1 20:53:07 joe gdm[31788]:         user_data = 0x9913000
Feb  1 20:53:07 joe gdm[31788]:         callback = 0x8063220
Feb  1 20:53:07 joe gdm[31788]:         cb_funcs = 0xf735171c
Feb  1 20:53:07 joe gdm[31788]:         cb_data = 0x990f168
Feb  1 20:53:07 joe gdm[31788]: 
Feb  1 20:53:07 joe gdm[31788]:         need_destroy = <optimized out>
Feb  1 20:53:07 joe gdm[31788]:         source = 0x990b600
Feb  1 20:53:07 joe gdm[31788]:         current = 0x9912820
Feb  1 20:53:07 joe gdm[31788]:         i = <optimized out>
Feb  1 20:53:07 joe gdm[31788]: #9  g_main_context_dispatch (context=0x990b6f0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2998
Feb  1 20:53:07 joe gdm[31788]: No locals.
Feb  1 20:53:07 joe gdm[31788]: #10 0xf729d170 in g_main_context_iterate (context=0x990b6f0, block=-148194608, dispatch=1, self=<optimized out>) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3076
Feb  1 20:53:07 joe gdm[31788]: 
Feb  1 20:53:07 joe last message repeated 2 times
Feb  1 20:53:07 joe gdm[31788]:         nfds = <optimized out>
Feb  1 20:53:07 joe gdm[31788]:         allocated_nfds = <optimized out>
Feb  1 20:53:07 joe gdm[31788]:         fds = 0x9914cb0
Feb  1 20:53:07 joe gdm[31788]: #11 0xf729d77b in g_main_loop_run (loop=0x9910440) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3284
Feb  1 20:53:07 joe gdm[31788]: 
Feb  1 20:53:07 joe gdm[31788]: #12 0x0804dfa1 in ?? ()
Feb  1 20:53:07 joe gdm[31788]: No symbol table info available.
Feb  1 20:53:07 joe gdm[31788]: #13 0xf70b8e46 in __libc_start_main (main=0x804dc70, argc=3, ubp_av=0xffc213b4, init=0x80695d0, fini=0x80695c0, rtld_fini=0xf7735310, stack_end=0xffc213ac) at libc-start.c:228
Feb  1 20:53:07 joe gdm[31788]:         result = <optimized out>
Feb  1 20:53:07 joe gdm[31788]: 
Feb  1 20:53:07 joe gdm[31788]:         not_first_call = <optimized out>
Feb  1 20:53:07 joe gdm[31788]: #14 0x0804e0a9 in ?? ()
Feb  1 20:53:07 joe gdm[31788]: No symbol table info available.
Feb  1 20:53:07 joe gdm[31788]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:53:07 joe gdm[31788]: A debugging session is active.
Feb  1 20:53:07 joe gdm[31788]: 
Feb  1 20:53:07 joe gdm[31788]: ^IInferior 1 [process 30924] will be detached.
Feb  1 20:53:07 joe gdm[31788]: 
Feb  1 20:53:07 joe gdm[31788]: Quit anyway? (y or n) [answered Y; input not from terminal]
Feb  1 20:53:07 joe gdm[31788]: ******************* END **********************************
Feb  1 20:53:14 joe gdm-simple-slave[30559]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30673]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30671]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30674]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30675]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30685]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30686]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30684]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30683]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30682]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30681]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30672]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30676]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30680]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30690]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30693]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30677]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30678]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30679]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30687]: WARNING: Failed to get value: 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. 
Feb  1 20:53:14 joe gdm-simple-slave[30688]: WARNING: Failed to get value: 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. 
Feb  1 20:53:23 joe acpid: client 31730[0:0] has disconnected
Feb  1 20:53:23 joe acpid: client connected from 32028[0:0]
Feb  1 20:53:23 joe acpid: 1 client rule loaded
Feb  1 20:53:23 joe gdm-simple-slave[32051]: WARNING: gdm_server_spawn: Protokolldatei für Anzeige (null) konnte nicht geöffnet werden! 
Feb  1 20:53:24 joe gdm[32244]: ******************* START **********************************
Feb  1 20:53:24 joe gdm[32244]: [Thread debugging using libthread_db enabled]
Feb  1 20:53:24 joe gdm[32244]: [New Thread 0xf6c7ab70 (LWP 32033)]
Feb  1 20:53:25 joe gdm[32244]: 0xf770d425 in __kernel_vsyscall ()
Feb  1 20:53:25 joe gdm[32244]: #0  0xf770d425 in __kernel_vsyscall ()
Feb  1 20:53:25 joe gdm[32244]: #1  0xf74f71eb in waitpid () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:53:25 joe gdm[32244]: #2  0x08067a25 in ?? ()
Feb  1 20:53:25 joe gdm[32244]: #3  0x08067e39 in ?? ()
Feb  1 20:53:25 joe gdm[32244]: #4  <signal handler called>
Feb  1 20:53:25 joe gdm[32244]: #5  0x0805f5bf in ?? ()
Feb  1 20:53:25 joe gdm[32244]: #6  0x08063248 in ?? ()
Feb  1 20:53:25 joe gdm[32244]: #7  0xf7280270 in g_idle_dispatch (source=0x82082f8, callback=0x8063220, user_data=0x8206000) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4776
Feb  1 20:53:25 joe gdm[32244]: #8  0xf7283a3f in g_main_dispatch (context=0x81fe9c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2442
Feb  1 20:53:25 joe gdm[32244]: #9  g_main_context_dispatch (context=0x81fe9c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2998
Feb  1 20:53:25 joe gdm[32244]: #10 0xf7284170 in g_main_context_iterate (context=0x81fe9c0, block=-148297008, dispatch=1, self=<optimized out>) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3076
Feb  1 20:53:25 joe gdm[32244]: #11 0xf728477b in g_main_loop_run (loop=0x8203740) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3284
Feb  1 20:53:25 joe gdm[32244]: #12 0x0804dfa1 in ?? ()
Feb  1 20:53:25 joe gdm[32244]: #13 0xf709fe46 in __libc_start_main (main=0x804dc70, argc=3, ubp_av=0xffd01684, init=0x80695d0, fini=0x80695c0, rtld_fini=0xf771c310, stack_end=0xffd0167c) at libc-start.c:228
Feb  1 20:53:25 joe gdm[32244]: #14 0x0804e0a9 in ?? ()
Feb  1 20:53:25 joe gdm[32244]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:53:25 joe gdm[32244]: 
Feb  1 20:53:25 joe gdm[32244]: Thread 2 (Thread 0xf6c7ab70 (LWP 32033)):
Feb  1 20:53:25 joe gdm[32244]: #0  0xf770d425 in __kernel_vsyscall ()
Feb  1 20:53:25 joe gdm[32244]: No symbol table info available.
Feb  1 20:53:25 joe gdm[32244]: #1  0xf74f633b in read () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:53:25 joe gdm[32244]: No locals.
Feb  1 20:53:25 joe gdm[32244]: #2  0xf727f60b in unix_signal_helper_thread (data=0x0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4542
Feb  1 20:53:25 joe gdm[32244]:         i = <optimized out>
Feb  1 20:53:25 joe gdm[32244]:         bytes_read = <optimized out>
Feb  1 20:53:25 joe gdm[32244]: 
Feb  1 20:53:25 joe last message repeated 3 times
Feb  1 20:53:25 joe gdm[32244]: #3  0xf72aadd4 in g_thread_create_proxy (data=0x8207ed0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gthread.c:1962
Feb  1 20:53:25 joe gdm[32244]:         thread = 0x8207ed0
Feb  1 20:53:25 joe gdm[32244]: 
Feb  1 20:53:25 joe gdm[32244]: #4  0xf74eec39 in start_thread (arg=0xf6c7ab70) at pthread_create.c:304
Feb  1 20:53:25 joe gdm[32244]:         __res = <optimized out>
Feb  1 20:53:25 joe gdm[32244]:         __ignore1 = <optimized out>
Feb  1 20:53:25 joe gdm[32244]:         __ignore2 = <optimized out>
Feb  1 20:53:25 joe gdm[32244]:         pd = 0xf6c7ab70
Feb  1 20:53:25 joe gdm[32244]:         now = <optimized out>
Feb  1 20:53:25 joe gdm[32244]: 
Feb  1 20:53:25 joe gdm[32244]:         not_first_call = <optimized out>
Feb  1 20:53:25 joe gdm[32244]:         freesize = <optimized out>
Feb  1 20:53:25 joe gdm[32244]: 
Feb  1 20:53:25 joe gdm[32244]: #5  0xf715912e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Feb  1 20:53:25 joe gdm[32244]: No locals.
Feb  1 20:53:25 joe gdm[32244]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:53:25 joe gdm[32244]: 
Feb  1 20:53:25 joe gdm[32244]: Thread 1 (Thread 0xf6df2ac0 (LWP 30689)):
Feb  1 20:53:25 joe gdm[32244]: #0  0xf770d425 in __kernel_vsyscall ()
Feb  1 20:53:25 joe gdm[32244]: No symbol table info available.
Feb  1 20:53:25 joe gdm[32244]: #1  0xf74f71eb in waitpid () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:53:25 joe gdm[32244]: No locals.
Feb  1 20:53:25 joe gdm[32244]: #2  0x08067a25 in ?? ()
Feb  1 20:53:25 joe gdm[32244]: No symbol table info available.
Feb  1 20:53:25 joe gdm[32244]: #3  0x08067e39 in ?? ()
Feb  1 20:53:25 joe gdm[32244]: No symbol table info available.
Feb  1 20:53:25 joe gdm[32244]: #4  <signal handler called>
Feb  1 20:53:25 joe gdm[32244]: No symbol table info available.
Feb  1 20:53:25 joe gdm[32244]: #5  0x0805f5bf in ?? ()
Feb  1 20:53:25 joe gdm[32244]: No symbol table info available.
Feb  1 20:53:25 joe gdm[32244]: #6  0x08063248 in ?? ()
Feb  1 20:53:25 joe gdm[32244]: No symbol table info available.
Feb  1 20:53:25 joe gdm[32244]: #7  0xf7280270 in g_idle_dispatch (source=0x82082f8, callback=0x8063220, user_data=0x8206000) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4776
Feb  1 20:53:25 joe gdm[32244]: No locals.
Feb  1 20:53:25 joe gdm[32244]: #8  0xf7283a3f in g_main_dispatch (context=0x81fe9c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2442
Feb  1 20:53:25 joe gdm[32244]:         dispatch = 0xf7280250 <g_idle_dispatch>
Feb  1 20:53:25 joe gdm[32244]: 
Feb  1 20:53:25 joe gdm[32244]:         user_data = 0x8206000
Feb  1 20:53:25 joe gdm[32244]:         callback = 0x8063220
Feb  1 20:53:25 joe gdm[32244]:         cb_funcs = 0xf733871c
Feb  1 20:53:25 joe gdm[32244]:         cb_data = 0x8207378
Feb  1 20:53:25 joe gdm[32244]: 
Feb  1 20:53:25 joe gdm[32244]:         need_destroy = <optimized out>
Feb  1 20:53:25 joe gdm[32244]:         source = 0x82082f8
Feb  1 20:53:25 joe gdm[32244]:         current = 0x8205a60
Feb  1 20:53:25 joe gdm[32244]:         i = <optimized out>
Feb  1 20:53:25 joe gdm[32244]: #9  g_main_context_dispatch (context=0x81fe9c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2998
Feb  1 20:53:25 joe gdm[32244]: No locals.
Feb  1 20:53:25 joe gdm[32244]: #10 0xf7284170 in g_main_context_iterate (context=0x81fe9c0, block=-148297008, dispatch=1, self=<optimized out>) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3076
Feb  1 20:53:25 joe gdm[32244]: 
Feb  1 20:53:25 joe last message repeated 2 times
Feb  1 20:53:25 joe gdm[32244]:         nfds = <optimized out>
Feb  1 20:53:25 joe gdm[32244]:         allocated_nfds = <optimized out>
Feb  1 20:53:25 joe gdm[32244]:         fds = 0x8208198
Feb  1 20:53:25 joe gdm[32244]: #11 0xf728477b in g_main_loop_run (loop=0x8203740) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3284
Feb  1 20:53:25 joe gdm[32244]: 
Feb  1 20:53:25 joe gdm[32244]: #12 0x0804dfa1 in ?? ()
Feb  1 20:53:25 joe gdm[32244]: No symbol table info available.
Feb  1 20:53:25 joe gdm[32244]: #13 0xf709fe46 in __libc_start_main (main=0x804dc70, argc=3, ubp_av=0xffd01684, init=0x80695d0, fini=0x80695c0, rtld_fini=0xf771c310, stack_end=0xffd0167c) at libc-start.c:228
Feb  1 20:53:25 joe gdm[32244]:         result = <optimized out>
Feb  1 20:53:25 joe gdm[32244]: 
Feb  1 20:53:25 joe gdm[32244]:         not_first_call = <optimized out>
Feb  1 20:53:25 joe gdm[32244]: #14 0x0804e0a9 in ?? ()
Feb  1 20:53:25 joe gdm[32244]: No symbol table info available.
Feb  1 20:53:25 joe gdm[32244]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:53:25 joe gdm[32244]: A debugging session is active.
Feb  1 20:53:25 joe gdm[32244]: 
Feb  1 20:53:25 joe gdm[32244]: ^IInferior 1 [process 30689] will be detached.
Feb  1 20:53:25 joe gdm[32244]: 
Feb  1 20:53:25 joe gdm[32244]: Quit anyway? (y or n) [answered Y; input not from terminal]
Feb  1 20:53:25 joe gdm[32244]: ******************* END **********************************
Feb  1 20:53:27 joe acpid: client 32028[0:0] has disconnected
Feb  1 20:53:27 joe acpid: client connected from 32151[0:0]
Feb  1 20:53:27 joe acpid: 1 client rule loaded
Feb  1 20:53:28 joe gdm[32319]: ******************* START **********************************
Feb  1 20:53:28 joe gdm[32319]: [Thread debugging using libthread_db enabled]
Feb  1 20:53:28 joe gdm[32319]: [New Thread 0xf6c5db70 (LWP 32159)]
Feb  1 20:53:29 joe gdm[32319]: 0xf76f0425 in __kernel_vsyscall ()
Feb  1 20:53:29 joe gdm[32319]: #0  0xf76f0425 in __kernel_vsyscall ()
Feb  1 20:53:29 joe gdm[32319]: #1  0xf74da1eb in waitpid () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:53:29 joe gdm[32319]: #2  0x08067a25 in ?? ()
Feb  1 20:53:29 joe gdm[32319]: #3  0x08067e39 in ?? ()
Feb  1 20:53:29 joe gdm[32319]: #4  <signal handler called>
Feb  1 20:53:29 joe gdm[32319]: #5  0x0805f5bf in ?? ()
Feb  1 20:53:29 joe gdm[32319]: #6  0x08063248 in ?? ()
Feb  1 20:53:29 joe gdm[32319]: #7  0xf7263270 in g_idle_dispatch (source=0x995e2f8, callback=0x8063220, user_data=0x995c000) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4776
Feb  1 20:53:29 joe gdm[32319]: #8  0xf7266a3f in g_main_dispatch (context=0x99549c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2442
Feb  1 20:53:29 joe gdm[32319]: #9  g_main_context_dispatch (context=0x99549c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2998
Feb  1 20:53:29 joe gdm[32319]: #10 0xf7267170 in g_main_context_iterate (context=0x99549c0, block=-148415792, dispatch=1, self=<optimized out>) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3076
Feb  1 20:53:29 joe gdm[32319]: #11 0xf726777b in g_main_loop_run (loop=0x9959740) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3284
Feb  1 20:53:29 joe gdm[32319]: #12 0x0804dfa1 in ?? ()
Feb  1 20:53:29 joe gdm[32319]: #13 0xf7082e46 in __libc_start_main (main=0x804dc70, argc=3, ubp_av=0xffac5fc4, init=0x80695d0, fini=0x80695c0, rtld_fini=0xf76ff310, stack_end=0xffac5fbc) at libc-start.c:228
Feb  1 20:53:29 joe gdm[32319]: #14 0x0804e0a9 in ?? ()
Feb  1 20:53:29 joe gdm[32319]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:53:29 joe gdm[32319]: 
Feb  1 20:53:29 joe gdm[32319]: Thread 2 (Thread 0xf6c5db70 (LWP 32159)):
Feb  1 20:53:29 joe gdm[32319]: #0  0xf76f0425 in __kernel_vsyscall ()
Feb  1 20:53:29 joe gdm[32319]: No symbol table info available.
Feb  1 20:53:29 joe gdm[32319]: #1  0xf74d933b in read () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:53:29 joe gdm[32319]: No locals.
Feb  1 20:53:29 joe gdm[32319]: #2  0xf726260b in unix_signal_helper_thread (data=0x0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4542
Feb  1 20:53:29 joe gdm[32319]:         i = <optimized out>
Feb  1 20:53:29 joe gdm[32319]:         bytes_read = <optimized out>
Feb  1 20:53:29 joe gdm[32319]: 
Feb  1 20:53:29 joe last message repeated 3 times
Feb  1 20:53:29 joe gdm[32319]: #3  0xf728ddd4 in g_thread_create_proxy (data=0x995ded0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gthread.c:1962
Feb  1 20:53:29 joe gdm[32319]:         thread = 0x995ded0
Feb  1 20:53:29 joe gdm[32319]: 
Feb  1 20:53:29 joe gdm[32319]: #4  0xf74d1c39 in start_thread (arg=0xf6c5db70) at pthread_create.c:304
Feb  1 20:53:29 joe gdm[32319]:         __res = <optimized out>
Feb  1 20:53:29 joe gdm[32319]:         __ignore1 = <optimized out>
Feb  1 20:53:29 joe gdm[32319]:         __ignore2 = <optimized out>
Feb  1 20:53:29 joe gdm[32319]:         pd = 0xf6c5db70
Feb  1 20:53:29 joe gdm[32319]:         now = <optimized out>
Feb  1 20:53:29 joe gdm[32319]: 
Feb  1 20:53:29 joe gdm[32319]:         not_first_call = <optimized out>
Feb  1 20:53:29 joe gdm[32319]:         freesize = <optimized out>
Feb  1 20:53:29 joe gdm[32319]: 
Feb  1 20:53:29 joe gdm[32319]: #5  0xf713c12e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Feb  1 20:53:29 joe gdm[32319]: No locals.
Feb  1 20:53:29 joe gdm[32319]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:53:29 joe gdm[32319]: 
Feb  1 20:53:29 joe gdm[32319]: Thread 1 (Thread 0xf6dd5ac0 (LWP 30780)):
Feb  1 20:53:29 joe gdm[32319]: #0  0xf76f0425 in __kernel_vsyscall ()
Feb  1 20:53:29 joe gdm[32319]: No symbol table info available.
Feb  1 20:53:29 joe gdm[32319]: all-template.S:82
Feb  1 20:53:29 joe gdm[32319]: No locals.
Feb  1 20:53:29 joe gdm[32319]: #2  0x08067a25 in ?? ()
Feb  1 20:53:29 joe gdm[32319]: No symbol table info available.
Feb  1 20:53:29 joe gdm[32319]: #3  0x08067e39 in ?? ()
Feb  1 20:53:29 joe gdm[32319]: No symbol table info available.
Feb  1 20:53:29 joe gdm[32319]: #4  <signal handler called>
Feb  1 20:53:29 joe gdm[32319]: No symbol table info available.
Feb  1 20:53:29 joe gdm[32319]: #5  0x0805f5bf in ?? ()
Feb  1 20:53:29 joe gdm[32319]: .
Feb  1 20:53:29 joe gdm[32319]: #6  0x08063248 in ?? ()
Feb  1 20:53:29 joe gdm[32319]: No symbol table info available.
Feb  1 20:53:29 joe gdm[32319]: #7  0xf7263270 in g_idle_dispatch (source=0x995e2f8, callback=0x8063220, user_data=0x995c000) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4776
Feb  1 20:53:29 joe gdm[32319]: No locals.
Feb  1 20:53:29 joe gdm[32319]: a3f in g_main_dispatch (context=0x99549c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2442
Feb  1 20:53:29 joe gdm[32319]:         dispatch = 0xf7263250 <g_idle_dispatch>
Feb  1 20:53:29 joe gdm[32319]:         was_in_call = 0
Feb  1 20:53:29 joe gdm[32319]:         user_data = 0x995c000
Feb  1 20:53:29 joe gdm[32319]:         callback = 0x8063220
Feb  1 20:53:29 joe gdm[32319]:         cb_funcs = 0xf731b71c
Feb  1 20:53:29 joe gdm[32319]:         cb_data = 0x995d378
Feb  1 20:53:29 joe gdm[32319]:         current_source_link = {data = 0x995e2f8, next = 0x0}
Feb  1 20:53:29 joe gdm[32319]:         need_destroy = <optimized out>
Feb  1 20:53:29 joe gdm[32319]:         source = 0x995e2f8
Feb  1 20:53:29 joe gdm[32319]:         current = 0x995ba60
Feb  1 20:53:29 joe gdm[32319]:         i = <optimized out>
Feb  1 20:53:29 joe gdm[32319]: text_dispatch (context=0x99549c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2998
Feb  1 20:53:29 joe gdm[32319]: No locals.
Feb  1 20:53:29 joe gdm[32319]: -glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3076
Feb  1 20:53:29 joe gdm[32319]:         max_priority = 200
Feb  1 20:53:29 joe gdm[32319]:         timeout = 0
Feb  1 20:53:29 joe gdm[32319]:         some_ready = 1
Feb  1 20:53:29 joe gdm[32319]:         nfds = <optimized out>
Feb  1 20:53:29 joe gdm[32319]:         allocated_nfds = <optimized out>
Feb  1 20:53:29 joe gdm[32319]:         fds = 0x995e198
Feb  1 20:53:29 joe gdm[32319]: _loop_run (loop=0x9959740) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3284
Feb  1 20:53:29 joe gdm[32319]: 
Feb  1 20:53:29 joe gdm[32319]: #12 0x0804dfa1 in ?? ()
Feb  1 20:53:29 joe gdm[32319]: No symbol table info available.
Feb  1 20:53:29 joe gdm[32319]: #13 0xf7082e46 in __libc_start_main (main=0x804dc70, argc=3, ubp_av=0xffac5fc4, init=0x80695d0, fini=0x80695c0, rtld_fini=0xf76ff310, stack_end=0xffac5fbc) at libc-start.c:228
Feb  1 20:53:29 joe gdm[32319]:         result = <optimized out>
Feb  1 20:53:29 joe gdm[32319]: 
Feb  1 20:53:29 joe gdm[32319]:         not_first_call = <optimized out>
Feb  1 20:53:29 joe gdm[32319]: #14 0x0804e0a9 in ?? ()
Feb  1 20:53:29 joe gdm[32319]: No symbol table info available.
Feb  1 20:53:29 joe gdm[32319]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:53:29 joe gdm[32319]: A debugging session is active.
Feb  1 20:53:29 joe gdm[32319]: 
Feb  1 20:53:29 joe gdm[32319]: ^IInferior 1 [process 30780] will be detached.
Feb  1 20:53:29 joe gdm[32319]: 
Feb  1 20:53:29 joe gdm[32319]: Quit anyway? (y or n) [answered Y; input not from terminal]
Feb  1 20:53:29 joe gdm[32319]: ******************* END **********************************
Feb  1 20:53:44 joe gdm-simple-slave[32398]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78388: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32397]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78387: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32396]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78386: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32395]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78385: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32394]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78384: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32370]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78374: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32392]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78382: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32391]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78381: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32390]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78380: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32389]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78379: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32388]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78378: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32387]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78377: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32386]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78376: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32384]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78375: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32361]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78373: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32360]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78372: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32393]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78383: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32358]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78370: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32359]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78371: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32355]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78367: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32357]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78369: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32354]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78366: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32356]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78368: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32353]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78365: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32352]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78364: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32350]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78362: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32348]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78360: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32351]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78363: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32346]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78358: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32349]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78361: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32345]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78357: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32347]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78359: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32343]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78355: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32344]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78356: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32341]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78353: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32342]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78354: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32338]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78351: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32340]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78352: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32336]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78350: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32334]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78348: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32332]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78346: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32335]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78349: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32330]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78344: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32333]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78347: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32329]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78343: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32331]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78345: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32327]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78341: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32328]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78342: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32325]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78339: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32326]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78340: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32322]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78338: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32317]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78337: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32315]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78336: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32313]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78334: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32314]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78335: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32311]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78332: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32309]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78330: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32312]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78333: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32310]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78331: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32308]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78329: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32307]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78328: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32306]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78327: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32304]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78326: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32303]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78325: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32302]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78324: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32301]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78323: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32299]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78321: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32273]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78317: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32291]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78319: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32300]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78322: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32274]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78318: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32298]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78320: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32272]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78316: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32271]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78315: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32270]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78314: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32269]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78313: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32268]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78312: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32267]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78311: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32265]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78310: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32263]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78309: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32262]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78308: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32261]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78307: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32260]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78306: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32256]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78305: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32255]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78304: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32254]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78303: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32253]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78302: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32252]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78301: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32251]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78300: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32250]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78299: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32247]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78298: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32242]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78297: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32240]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78296: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32239]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78295: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32238]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78294: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32237]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78293: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32236]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78292: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32235]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78291: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32234]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78290: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32233]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78289: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[32232]: WARNING: Failed to get display ID /org/gnome/DisplayManager/Display78288: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31818]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31817]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31816]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31815]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31814]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31813]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31812]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31811]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31810]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31809]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31807]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31806]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31805]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31804]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31803]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31802]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31801]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31800]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31799]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31798]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31797]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31796]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31794]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31791]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31783]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31780]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31779]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31769]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31765]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31795]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31764]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31763]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31744]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31761]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31743]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31737]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31740]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31734]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31726]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31731]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31722]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31705]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31709]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31696]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31702]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31686]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31668]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31683]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31667]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31661]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31666]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31656]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31658]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31652]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31597]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe gdm-simple-slave[31647]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus) 
Feb  1 20:53:44 joe acpid: client 32151[0:0] has disconnected
Feb  1 20:53:44 joe gdm[32560]: ******************* START **********************************
Feb  1 20:53:44 joe gdm[32560]: [Thread debugging using libthread_db enabled]
Feb  1 20:53:44 joe acpid: client connected from 32533[0:0]
Feb  1 20:53:44 joe gdm[32560]: [New Thread 0xf6d48b70 (LWP 32539)]
Feb  1 20:53:44 joe acpid: 1 client rule loaded
Feb  1 20:53:44 joe gdm-simple-slave[31597]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31647]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31652]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31656]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31658]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31661]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31666]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31667]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31668]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31683]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31686]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31696]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31702]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31705]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31709]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31722]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31726]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31731]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31734]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31737]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31740]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31743]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31744]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31761]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31763]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31764]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31765]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31769]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31779]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31780]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31783]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31791]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31794]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31795]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31796]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31797]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31798]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31799]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31800]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31801]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31802]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31803]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31804]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31805]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31806]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31807]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31809]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31810]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31811]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31812]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31813]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31814]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31815]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31816]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31817]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:44 joe gdm-simple-slave[31818]: WARNING: Failed to get value: The name :1.11 was not provided by any .service files 
Feb  1 20:53:45 joe gdm[32560]: 0xf77db425 in __kernel_vsyscall ()
Feb  1 20:53:45 joe gdm[32560]: #0  0xf77db425 in __kernel_vsyscall ()
Feb  1 20:53:45 joe gdm[32560]: #1  0xf75c51eb in waitpid () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:53:45 joe gdm[32560]: #2  0x08067a25 in ?? ()
Feb  1 20:53:45 joe gdm[32560]: #3  0x08067e39 in ?? ()
Feb  1 20:53:45 joe gdm[32560]: #4  <signal handler called>
Feb  1 20:53:45 joe gdm[32560]: #5  0x0805f5bf in ?? ()
Feb  1 20:53:45 joe gdm[32560]: #6  0x08063248 in ?? ()
Feb  1 20:53:45 joe gdm[32560]: #7  0xf734e270 in g_idle_dispatch (source=0x9019ce8, callback=0x8063220, user_data=0x9018000) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4776
Feb  1 20:53:45 joe gdm[32560]: #8  0xf7351a3f in g_main_dispatch (context=0x90109c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2442
Feb  1 20:53:45 joe gdm[32560]: #9  g_main_context_dispatch (context=0x90109c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2998
Feb  1 20:53:45 joe gdm[32560]: #10 0xf7352170 in g_main_context_iterate (context=0x90109c0, block=-147453232, dispatch=1, self=<optimized out>) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3076
Feb  1 20:53:45 joe gdm[32560]: #11 0xf735277b in g_main_loop_run (loop=0x9015740) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3284
Feb  1 20:53:45 joe gdm[32560]: #12 0x0804dfa1 in ?? ()
Feb  1 20:53:45 joe gdm[32560]: #13 0xf716de46 in __libc_start_main (main=0x804dc70, argc=3, ubp_av=0xffc74104, init=0x80695d0, fini=0x80695c0, rtld_fini=0xf77ea310, stack_end=0xffc740fc) at libc-start.c:228
Feb  1 20:53:45 joe gdm[32560]: #14 0x0804e0a9 in ?? ()
Feb  1 20:53:45 joe gdm[32560]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:53:45 joe gdm[32560]: 
Feb  1 20:53:45 joe gdm[32560]: Thread 2 (Thread 0xf6d48b70 (LWP 32539)):
Feb  1 20:53:45 joe gdm[32560]: #0  0xf77db425 in __kernel_vsyscall ()
Feb  1 20:53:45 joe gdm[32560]: No symbol table info available.
Feb  1 20:53:45 joe gdm[32560]: #1  0xf75c433b in read () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:53:45 joe gdm[32560]: No locals.
Feb  1 20:53:45 joe gdm[32560]: #2  0xf734d60b in unix_signal_helper_thread (data=0x0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4542
Feb  1 20:53:45 joe gdm[32560]:         i = <optimized out>
Feb  1 20:53:45 joe gdm[32560]:         bytes_read = <optimized out>
Feb  1 20:53:45 joe gdm[32560]: 
Feb  1 20:53:45 joe last message repeated 3 times
Feb  1 20:53:45 joe gdm[32560]: #3  0xf7378dd4 in g_thread_create_proxy (data=0x901a230) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gthread.c:1962
Feb  1 20:53:45 joe gdm[32560]:         thread = 0x901a230
Feb  1 20:53:45 joe gdm[32560]: 
Feb  1 20:53:45 joe gdm[32560]: #4  0xf75bcc39 in start_thread (arg=0xf6d48b70) at pthread_create.c:304
Feb  1 20:53:45 joe gdm[32560]:         __res = <optimized out>
Feb  1 20:53:45 joe gdm[32560]:         __ignore1 = <optimized out>
Feb  1 20:53:45 joe gdm[32560]:         __ignore2 = <optimized out>
Feb  1 20:53:45 joe gdm[32560]:         pd = 0xf6d48b70
Feb  1 20:53:45 joe gdm[32560]:         now = <optimized out>
Feb  1 20:53:45 joe gdm[32560]: 
Feb  1 20:53:45 joe gdm[32560]:         not_first_call = <optimized out>
Feb  1 20:53:45 joe gdm[32560]:         freesize = <optimized out>
Feb  1 20:53:45 joe gdm[32560]: 
Feb  1 20:53:45 joe gdm[32560]: #5  0xf722712e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Feb  1 20:53:45 joe gdm[32560]: No locals.
Feb  1 20:53:45 joe gdm[32560]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:53:45 joe gdm[32560]: 
Feb  1 20:53:45 joe gdm[32560]: Thread 1 (Thread 0xf6ec0ac0 (LWP 32370)):
Feb  1 20:53:45 joe gdm[32560]: #0  0xf77db425 in __kernel_vsyscall ()
Feb  1 20:53:45 joe gdm[32560]: No symbol table info available.
Feb  1 20:53:45 joe gdm[32560]: #1  0xf75c51eb in waitpid () at ../sysdeps/unix/syscall-template.S:82
Feb  1 20:53:45 joe gdm[32560]: No locals.
Feb  1 20:53:45 joe gdm[32560]: #2  0x08067a25 in ?? ()
Feb  1 20:53:45 joe gdm[32560]: No symbol table info available.
Feb  1 20:53:45 joe gdm[32560]: #3  0x08067e39 in ?? ()
Feb  1 20:53:45 joe gdm[32560]: No symbol table info available.
Feb  1 20:53:45 joe gdm[32560]: #4  <signal handler called>
Feb  1 20:53:45 joe gdm[32560]: No symbol table info available.
Feb  1 20:53:45 joe gdm[32560]: #5  0x0805f5bf in ?? ()
Feb  1 20:53:45 joe gdm[32560]: No symbol table info available.
Feb  1 20:53:45 joe gdm[32560]: #6  0x08063248 in ?? ()
Feb  1 20:53:45 joe gdm[32560]: No symbol table info available.
Feb  1 20:53:45 joe gdm[32560]: #7  0xf734e270 in g_idle_dispatch (source=0x9019ce8, callback=0x8063220, user_data=0x9018000) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:4776
Feb  1 20:53:45 joe gdm[32560]: No locals.
Feb  1 20:53:45 joe gdm[32560]: #8  0xf7351a3f in g_main_dispatch (context=0x90109c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2442
Feb  1 20:53:45 joe gdm[32560]:         dispatch = 0xf734e250 <g_idle_dispatch>
Feb  1 20:53:45 joe gdm[32560]: 
Feb  1 20:53:45 joe gdm[32560]:         user_data = 0x9018000
Feb  1 20:53:45 joe gdm[32560]:         callback = 0x8063220
Feb  1 20:53:45 joe gdm[32560]:         cb_funcs = 0xf740671c
Feb  1 20:53:45 joe gdm[32560]:         cb_data = 0x901a260
Feb  1 20:53:45 joe gdm[32560]: 
Feb  1 20:53:45 joe gdm[32560]:         need_destroy = <optimized out>
Feb  1 20:53:45 joe gdm[32560]:         source = 0x9019ce8
Feb  1 20:53:45 joe gdm[32560]:         current = 0x9017aa0
Feb  1 20:53:45 joe gdm[32560]:         i = <optimized out>
Feb  1 20:53:45 joe gdm[32560]: #9  g_main_context_dispatch (context=0x90109c0) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:2998
Feb  1 20:53:45 joe gdm[32560]: No locals.
Feb  1 20:53:45 joe gdm[32560]: #10 0xf7352170 in g_main_context_iterate (context=0x90109c0, block=-147453232, dispatch=1, self=<optimized out>) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3076
Feb  1 20:53:45 joe gdm[32560]: 
Feb  1 20:53:45 joe last message repeated 2 times
Feb  1 20:53:45 joe gdm[32560]:         nfds = <optimized out>
Feb  1 20:53:45 joe gdm[32560]:         allocated_nfds = <optimized out>
Feb  1 20:53:45 joe gdm[32560]:         fds = 0x901a070
Feb  1 20:53:45 joe gdm[32560]: #11 0xf735277b in g_main_loop_run (loop=0x9015740) at /build/buildd-glib2.0_2.30.2-6-i386-6DwKmX/glib2.0-2.30.2/./glib/gmain.c:3284
Feb  1 20:53:45 joe gdm[32560]: 
Feb  1 20:53:45 joe gdm[32560]: #12 0x0804dfa1 in ?? ()
Feb  1 20:53:45 joe gdm[32560]: No symbol table info available.
Feb  1 20:53:45 joe gdm[32560]: #13 0xf716de46 in __libc_start_main (main=0x804dc70, argc=3, ubp_av=0xffc74104, init=0x80695d0, fini=0x80695c0, rtld_fini=0xf77ea310, stack_end=0xffc740fc) at libc-start.c:228
Feb  1 20:53:45 joe gdm[32560]:         result = <optimized out>
Feb  1 20:53:45 joe gdm[32560]: 
Feb  1 20:53:45 joe gdm[32560]:         not_first_call = <optimized out>
Feb  1 20:53:45 joe gdm[32560]: #14 0x0804e0a9 in ?? ()
Feb  1 20:53:45 joe gdm[32560]: No symbol table info available.
Feb  1 20:53:45 joe gdm[32560]: Backtrace stopped: Not enough registers or memory available to unwind further
Feb  1 20:53:45 joe gdm[32560]: A debugging session is active.
Feb  1 20:53:45 joe gdm[32560]: 
Feb  1 20:53:45 joe gdm[32560]: ^IInferior 1 [process 32370] will be detached.
Feb  1 20:53:45 joe gdm[32560]: 
Feb  1 20:53:45 joe gdm[32560]: Quit anyway? (y or n) [answered Y; input not from terminal]
Feb  1 20:53:45 joe gdm[32560]: ******************* END **********************************
Feb  1 20:53:45 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,038527 seconds 
Feb  1 20:53:46 joe acpid: client 32533[0:0] has disconnected
Feb  1 20:53:46 joe acpid: client connected from 418[0:0]
Feb  1 20:53:46 joe acpid: 1 client rule loaded
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,058275 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,049099 seconds 
Feb  1 20:53:46 joe acpid: client connected from 429[0:0]
Feb  1 20:53:46 joe acpid: 1 client rule loaded
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,054890 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,070908 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,070440 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,067490 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,105973 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,114736 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,111286 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,126839 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,136234 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,143373 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,153236 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,185367 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,171391 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,262753 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,277636 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,268707 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,278859 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,285127 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,295174 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,292582 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,315471 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,336042 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,342264 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,358967 seconds 
Feb  1 20:53:46 joe acpid: client connected from 529[0:0]
Feb  1 20:53:46 joe acpid: 1 client rule loaded
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,387095 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,339678 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,343407 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,485976 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,457540 seconds 
Feb  1 20:53:46 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,449575 seconds 
Feb  1 20:53:47 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,462103 seconds 
Feb  1 20:53:47 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,473256 seconds 
Feb  1 20:53:47 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,485225 seconds 
Feb  1 20:53:47 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,496502 seconds 
Feb  1 20:53:47 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,509386 seconds 
Feb  1 20:53:47 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,524779 seconds 
Feb  1 20:53:50 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,582275 seconds 
Feb  1 20:53:50 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,598204 seconds 
Feb  1 20:53:50 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,609856 seconds 
Feb  1 20:53:50 joe acpid: client 529[0:0] has disconnected
Feb  1 20:53:50 joe acpid: client connected from 606[0:0]
Feb  1 20:53:50 joe acpid: 1 client rule loaded
Feb  1 20:53:50 joe acpid: client connected from 624[0:0]
Feb  1 20:53:50 joe acpid: 1 client rule loaded
Feb  1 20:53:50 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,850287 seconds 
Feb  1 20:53:50 joe acpid: client 606[0:0] has disconnected
Feb  1 20:53:50 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,912812 seconds 
Feb  1 20:53:50 joe acpid: client 624[0:0] has disconnected
Feb  1 20:53:50 joe acpid: client connected from 640[0:0]
Feb  1 20:53:50 joe acpid: 1 client rule loaded
Feb  1 20:53:50 joe acpid: client 640[0:0] has disconnected
Feb  1 20:53:50 joe acpid: client connected from 648[0:0]
Feb  1 20:53:50 joe acpid: 1 client rule loaded
Feb  1 20:53:50 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,292966 seconds 
Feb  1 20:53:50 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,189218 seconds 
Feb  1 20:53:50 joe acpid: client 648[0:0] has disconnected
Feb  1 20:53:50 joe acpid: client connected from 760[0:0]
Feb  1 20:53:50 joe acpid: 1 client rule loaded
Feb  1 20:53:50 joe acpid: client connected from 772[0:0]
Feb  1 20:53:50 joe acpid: 1 client rule loaded
Feb  1 20:53:50 joe acpid: client connected from 787[0:0]
Feb  1 20:53:50 joe acpid: 1 client rule loaded
Feb  1 20:53:50 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,683333 seconds 
Feb  1 20:53:50 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,690193 seconds 
Feb  1 20:53:50 joe acpid: client 760[0:0] has disconnected
Feb  1 20:53:50 joe acpid: client connected from 829[0:0]
Feb  1 20:53:50 joe acpid: 1 client rule loaded
Feb  1 20:53:50 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,411448 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,863590 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,849691 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,834595 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,826862 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,823766 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,843623 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,861230 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,872760 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,885142 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,894932 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,908394 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,918077 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,931824 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,939360 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,955640 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,976722 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,983582 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,997702 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,015524 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,035316 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,040716 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,046199 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,062712 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,070085 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,084059 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,161619 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,179915 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,178044 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,198172 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,206944 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,204760 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,217875 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,631574 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,481374 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,356390 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,340253 seconds 
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,346849 seconds 
Feb  1 20:53:51 joe acpid: client 772[0:0] has disconnected
Feb  1 20:53:51 joe acpid: client 787[0:0] has disconnected
Feb  1 20:53:51 joe acpid: client 829[0:0] has disconnected
Feb  1 20:53:51 joe acpid: client connected from 942[0:0]
Feb  1 20:53:51 joe acpid: 1 client rule loaded
Feb  1 20:53:51 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,395203 seconds 
Feb  1 20:53:52 joe acpid: client 942[0:0] has disconnected
Feb  1 20:53:52 joe acpid: client connected from 948[0:0]
Feb  1 20:53:52 joe acpid: 1 client rule loaded
Feb  1 20:53:52 joe acpid: client 948[0:0] has disconnected
Feb  1 20:53:52 joe acpid: client connected from 957[0:0]
Feb  1 20:53:52 joe acpid: 1 client rule loaded
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,618759 seconds 
Feb  1 20:53:52 joe acpid: client 957[0:0] has disconnected
Feb  1 20:53:52 joe acpid: client connected from 960[0:0]
Feb  1 20:53:52 joe acpid: 1 client rule loaded
Feb  1 20:53:52 joe acpid: client connected from 962[0:0]
Feb  1 20:53:52 joe acpid: 1 client rule loaded
Feb  1 20:53:52 joe acpid: client connected from 964[0:0]
Feb  1 20:53:52 joe acpid: 1 client rule loaded
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,704629 seconds 
Feb  1 20:53:52 joe acpid: client 960[0:0] has disconnected
Feb  1 20:53:52 joe acpid: client 962[0:0] has disconnected
Feb  1 20:53:52 joe acpid: client 964[0:0] has disconnected
Feb  1 20:53:52 joe acpid: client connected from 1015[0:0]
Feb  1 20:53:52 joe acpid: 1 client rule loaded
Feb  1 20:53:52 joe acpid: client connected from 1021[0:0]
Feb  1 20:53:52 joe acpid: 1 client rule loaded
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,785392 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,786731 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,760226 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,746872 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,704609 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,684701 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,659614 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,658751 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,657582 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,669282 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,680673 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,690662 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,695480 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,706155 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,710523 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,997259 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,926312 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,933358 seconds 
Feb  1 20:53:52 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,888782 seconds 
Feb  1 20:53:53 joe acpid: client 1015[0:0] has disconnected
Feb  1 20:53:53 joe acpid: client 1021[0:0] has disconnected
Feb  1 20:53:53 joe acpid: client connected from 1078[0:0]
Feb  1 20:53:53 joe acpid: 1 client rule loaded
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,048693 seconds 
Feb  1 20:53:53 joe acpid: client connected from 1103[0:0]
Feb  1 20:53:53 joe acpid: 1 client rule loaded
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,119286 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,132119 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,043048 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,055046 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,067345 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,079449 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,092083 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,102965 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,106999 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,121438 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,131834 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,140873 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,153311 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,167723 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,175328 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,195605 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,205142 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,217354 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,232739 seconds 
Feb  1 20:53:53 joe acpid: client 1078[0:0] has disconnected
Feb  1 20:53:53 joe acpid: client 1103[0:0] has disconnected
Feb  1 20:53:53 joe acpid: client connected from 1199[0:0]
Feb  1 20:53:53 joe acpid: 1 client rule loaded
Feb  1 20:53:53 joe acpid: client connected from 1197[0:0]
Feb  1 20:53:53 joe acpid: 1 client rule loaded
Feb  1 20:53:53 joe acpid: client 1197[0:0] has disconnected
Feb  1 20:53:53 joe acpid: client connected from 1204[0:0]
Feb  1 20:53:53 joe acpid: 1 client rule loaded
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,304283 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,318585 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,329917 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,348976 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,348157 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,355416 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,370437 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,378776 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,385319 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,400284 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,413437 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,430947 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,439929 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,447579 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,458102 seconds 
Feb  1 20:53:53 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,474673 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,483019 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,497333 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,509388 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,453461 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,474730 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,485451 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,502819 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,516559 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,528103 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,534457 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,545500 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,561000 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,574839 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,592801 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,602526 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,612506 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,624659 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,604323 seconds 
Feb  1 20:53:54 joe acpid: client 1199[0:0] has disconnected
Feb  1 20:53:54 joe acpid: client 1204[0:0] has disconnected
Feb  1 20:53:54 joe acpid: client connected from 1275[0:0]
Feb  1 20:53:54 joe acpid: 1 client rule loaded
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,659540 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,668002 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,694344 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,165792 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,174555 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,789035 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,794312 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,265099 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,232726 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,236320 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,241323 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,244039 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,237801 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,243003 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,244834 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,248627 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,298483 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,289383 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,308866 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,323296 seconds 
Feb  1 20:53:54 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,334645 seconds 
Feb  1 20:53:55 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,349330 seconds 
Feb  1 20:53:55 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,364647 seconds 
Feb  1 20:53:55 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,385568 seconds 
Feb  1 20:53:55 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,402330 seconds 
Feb  1 20:53:55 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,420196 seconds 
Feb  1 20:53:57 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,437426 seconds 
Feb  1 20:53:57 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,446958 seconds 
Feb  1 20:53:58 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,463500 seconds 
Feb  1 20:53:58 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,481905 seconds 
Feb  1 20:53:58 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,498859 seconds 
Feb  1 20:53:58 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,515030 seconds 
Feb  1 20:53:58 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,534655 seconds 
Feb  1 20:53:58 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 0,552196 seconds 
Feb  1 20:53:59 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,292745 seconds 
Feb  1 20:53:59 joe acpid: client 1275[0:0] has disconnected
Feb  1 20:53:59 joe acpid: client connected from 1385[0:0]
Feb  1 20:53:59 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,325981 seconds 
Feb  1 20:53:59 joe acpid: 1 client rule loaded
Feb  1 20:53:59 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,865121 seconds 
Feb  1 20:53:59 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,115345 seconds 
Feb  1 20:53:59 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,130338 seconds 
Feb  1 20:53:59 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,151544 seconds 
Feb  1 20:53:59 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,174340 seconds 
Feb  1 20:53:59 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,181131 seconds 
Feb  1 20:53:59 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,183787 seconds 
Feb  1 20:53:59 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,739054 seconds 
Feb  1 20:53:59 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,762621 seconds 
Feb  1 20:53:59 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,883487 seconds 
Feb  1 20:53:59 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,895646 seconds 
Feb  1 20:53:59 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,880873 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,879753 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,887030 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,895362 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,910801 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,927089 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,944897 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,961587 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,979250 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,994463 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,009732 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,023994 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,043585 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,066691 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,088397 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,099245 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,110919 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,119733 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,136374 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,150676 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,158170 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,167075 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,178399 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,191429 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,201343 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,212535 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,220555 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,232001 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,240614 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,726051 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,728735 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,730313 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,735126 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,748832 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,757899 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,784021 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,790927 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,802841 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,813055 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,812323 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,836357 seconds 
Feb  1 20:54:00 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,856267 seconds 
Feb  1 20:54:01 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,882310 seconds 
Feb  1 20:54:01 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,359378 seconds 
Feb  1 20:54:01 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,360875 seconds 
Feb  1 20:54:01 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,356160 seconds 
Feb  1 20:54:01 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,356070 seconds 
Feb  1 20:54:01 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,360697 seconds 
Feb  1 20:54:01 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,402266 seconds 
Feb  1 20:54:01 joe acpid: client 1385[0:0] has disconnected
Feb  1 20:54:01 joe acpid: client connected from 1572[0:0]
Feb  1 20:54:01 joe acpid: 1 client rule loaded
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,206897 seconds 
Feb  1 20:54:02 joe acpid: client 1572[0:0] has disconnected
Feb  1 20:54:02 joe acpid: client connected from 1581[0:0]
Feb  1 20:54:02 joe acpid: 1 client rule loaded
Feb  1 20:54:02 joe acpid: client connected from 1585[0:0]
Feb  1 20:54:02 joe acpid: 1 client rule loaded
Feb  1 20:54:02 joe acpid: client connected from 1594[0:0]
Feb  1 20:54:02 joe acpid: 1 client rule loaded
Feb  1 20:54:02 joe acpid: client connected from 1586[0:0]
Feb  1 20:54:02 joe acpid: 1 client rule loaded
Feb  1 20:54:02 joe acpid: client connected from 1588[0:0]
Feb  1 20:54:02 joe acpid: 1 client rule loaded
Feb  1 20:54:02 joe acpid: client connected from 1576[0:0]
Feb  1 20:54:02 joe acpid: 1 client rule loaded
Feb  1 20:54:02 joe acpid: client connected from 1580[0:0]
Feb  1 20:54:02 joe acpid: 1 client rule loaded
Feb  1 20:54:02 joe acpid: client connected from 1596[0:0]
Feb  1 20:54:02 joe acpid: 1 client rule loaded
Feb  1 20:54:02 joe acpid: client connected from 1578[0:0]
Feb  1 20:54:02 joe acpid: 1 client rule loaded
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,250132 seconds 
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,285965 seconds 
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,354384 seconds 
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,379237 seconds 
Feb  1 20:54:02 joe gnome-session[816]: WARNING: Failed to start app: Unable to start application: Kindprozess »gnome-power-manager« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) 
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,417548 seconds 
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,465367 seconds 
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,493155 seconds 
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,551569 seconds 
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,579146 seconds 
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,612655 seconds 
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,654606 seconds 
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,684527 seconds 
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,719920 seconds 
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,749393 seconds 
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,776163 seconds 
Feb  1 20:54:02 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,799695 seconds 
Feb  1 20:54:04 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,840241 seconds 
Feb  1 20:54:05 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,869520 seconds 
Feb  1 20:54:05 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,905097 seconds 
Feb  1 20:54:05 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,923570 seconds 
Feb  1 20:54:05 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,959547 seconds 
Feb  1 20:54:05 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,969328 seconds 
Feb  1 20:54:05 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,981467 seconds 
Feb  1 20:54:06 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,992512 seconds 
Feb  1 20:54:06 joe acpid: client 1581[0:0] has disconnected
Feb  1 20:54:06 joe acpid: client 1585[0:0] has disconnected
Feb  1 20:54:06 joe acpid: client 1594[0:0] has disconnected
Feb  1 20:54:06 joe acpid: client 1586[0:0] has disconnected
Feb  1 20:54:06 joe acpid: client 1588[0:0] has disconnected
Feb  1 20:54:06 joe acpid: client 1576[0:0] has disconnected
Feb  1 20:54:06 joe acpid: client 1580[0:0] has disconnected
Feb  1 20:54:06 joe acpid: client 1596[0:0] has disconnected
Feb  1 20:54:06 joe acpid: client 1578[0:0] has disconnected
Feb  1 20:54:06 joe acpid: client connected from 1787[0:0]
Feb  1 20:54:06 joe acpid: 1 client rule loaded
Feb  1 20:54:06 joe acpid: client 1787[0:0] has disconnected
Feb  1 20:54:06 joe acpid: client connected from 1786[0:0]
Feb  1 20:54:06 joe acpid: 1 client rule loaded
Feb  1 20:54:06 joe acpid: client 1786[0:0] has disconnected
Feb  1 20:54:06 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 1,998571 seconds 
Feb  1 20:54:06 joe acpid: client connected from 1791[0:0]
Feb  1 20:54:06 joe acpid: 1 client rule loaded
Feb  1 20:54:06 joe acpid: client 1791[0:0] has disconnected
Feb  1 20:54:06 joe acpid: client connected from 1795[0:0]
Feb  1 20:54:06 joe acpid: 1 client rule loaded
Feb  1 20:54:06 joe acpid: client 1795[0:0] has disconnected
Feb  1 20:54:06 joe acpid: client connected from 1799[0:0]
Feb  1 20:54:06 joe acpid: 1 client rule loaded
Feb  1 20:54:06 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,051490 seconds 
Feb  1 20:54:06 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,034299 seconds 
Feb  1 20:54:06 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,022713 seconds 
Feb  1 20:54:06 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,003142 seconds 
Feb  1 20:54:06 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,011605 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,003935 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,006477 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,013192 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,020259 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,023275 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,023114 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,022607 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,027408 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,021664 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,028024 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,021058 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,020138 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,014647 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,021643 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,030066 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,032915 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,030596 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,036162 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,047219 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,058584 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,069325 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,079034 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,089812 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,095102 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,106531 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,117427 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,128979 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,139005 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,149726 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,159796 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,169605 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,180575 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,190659 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,200965 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,211157 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,221521 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,231469 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,242905 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,252817 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,262828 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,274061 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,285507 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,297188 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,309853 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,320610 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,332290 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,347523 seconds 
Feb  1 20:54:07 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,357367 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,369120 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,380625 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,392394 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,402958 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,412508 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,424143 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,435739 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,447219 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,458776 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,470732 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,482359 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,489752 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,500274 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,510430 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,522857 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,534073 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,546344 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,558415 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,570631 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,580496 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,593713 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,606165 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,618372 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,476420 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,495055 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,515229 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,533519 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,551316 seconds 
Feb  1 20:54:08 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,562885 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,575518 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,589446 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,608257 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,619761 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,641213 seconds 
Feb  1 20:54:09 joe gdm-simple-greeter[1634]: Gtk-WARNING: Overriding tab label for notebook 
Feb  1 20:54:09 joe last message repeated 4 times
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,660217 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,673378 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,687251 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,702272 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,715888 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,728428 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,740943 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,762936 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,777087 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,790193 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,804599 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,817380 seconds 
Feb  1 20:54:09 joe gdm-simple-greeter[1634]: Gtk-WARNING: /build/buildd-gtk+3.0_3.2.3-1-i386-GA85Ik/gtk+3.0-3.2.3/./gtk/gtkwidget.c:6857: widget not within a GtkWindow 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,836371 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,858349 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,878513 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,899088 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,913141 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,934578 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,948756 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,963602 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,989673 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,986164 seconds 
Feb  1 20:54:09 joe gdm3[32623]: WARNING: GdmDisplay: display lasted 2,999318 seconds 
Feb  1 20:54:12 joe gdm-simple-greeter[1634]: Gtk-CRITICAL: gtk_widget_get_preferred_height_for_width: assertion `width >= 0' failed 
Feb  1 20:54:12 joe gdm-simple-greeter[1634]: Gtk-WARNING: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height -3 
Feb  1 20:54:12 joe gdm-simple-greeter[1634]: Gtk-CRITICAL: gtk_widget_get_preferred_height_for_width: assertion `width >= 0' failed 
Feb  1 20:54:12 joe gdm-simple-greeter[1634]: Gtk-CRITICAL: gtk_widget_get_preferred_height_for_width: assertion `width >= 0' failed 
Feb  1 20:54:12 joe gdm-simple-greeter[1634]: Gtk-WARNING: gtk_widget_size_allocate(): attempt to allocate widget with width -47 and height -47 
Feb  1 20:54:16 joe acpid: client 1799[0:0] has disconnected
Feb  1 20:54:16 joe acpid: client connected from 2448[0:0]
Feb  1 20:54:16 joe acpid: 1 client rule loaded
Feb  1 20:54:16 joe acpid: client 2448[0:0] has disconnected
Feb  1 20:54:16 joe acpid: client connected from 2436[0:0]
Feb  1 20:54:16 joe acpid: 1 client rule loaded
Feb  1 20:54:16 joe acpid: client 2436[0:0] has disconnected
Feb  1 20:54:16 joe acpid: client connected from 2434[0:0]
Feb  1 20:54:16 joe acpid: 1 client rule loaded
Feb  1 20:54:16 joe acpid: client 2434[0:0] has disconnected
Feb  1 20:54:17 joe acpid: client connected from 2433[0:0]
Feb  1 20:54:17 joe acpid: 1 client rule loaded
Feb  1 20:54:17 joe acpid: client 2433[0:0] has disconnected
Feb  1 20:54:17 joe acpid: client connected from 2452[0:0]
Feb  1 20:54:17 joe acpid: 1 client rule loaded
Feb  1 20:54:17 joe acpid: client 2452[0:0] has disconnected
Feb  1 20:54:17 joe acpid: client connected from 2432[0:0]
Feb  1 20:54:17 joe acpid: 1 client rule loaded
Feb  1 20:54:17 joe acpid: client 2432[0:0] has disconnected
Feb  1 20:54:17 joe acpid: client connected from 2443[0:0]
Feb  1 20:54:17 joe acpid: 1 client rule loaded
Feb  1 20:54:17 joe acpid: client 2443[0:0] has disconnected
Feb  1 20:54:17 joe acpid: client connected from 2445[0:0]
Feb  1 20:54:17 joe acpid: 1 client rule loaded
Feb  1 20:54:17 joe acpid: client 2445[0:0] has disconnected
Feb  1 20:54:17 joe acpid: client connected from 2456[0:0]
Feb  1 20:54:17 joe acpid: 1 client rule loaded
Feb  1 20:54:17 joe acpid: client 2456[0:0] has disconnected
Feb  1 20:54:17 joe acpid: client connected from 2458[0:0]
Feb  1 20:54:17 joe acpid: 1 client rule loaded
Feb  1 20:54:17 joe acpid: client 2458[0:0] has disconnected
Feb  1 20:54:17 joe acpid: client connected from 2464[0:0]
Feb  1 20:54:18 joe acpid: 1 client rule loaded
Feb  1 20:54:18 joe acpid: client 2464[0:0] has disconnected
Feb  1 20:54:18 joe acpid: client connected from 2440[0:0]
Feb  1 20:54:18 joe acpid: 1 client rule loaded
Feb  1 20:54:18 joe acpid: client 2440[0:0] has disconnected
Feb  1 20:54:18 joe acpid: client connected from 2471[0:0]
Feb  1 20:54:18 joe acpid: 1 client rule loaded
Feb  1 20:54:18 joe acpid: client 2471[0:0] has disconnected
Feb  1 20:54:18 joe acpid: client connected from 2481[0:0]
Feb  1 20:54:18 joe acpid: 1 client rule loaded
Feb  1 20:54:18 joe acpid: client 2481[0:0] has disconnected
Feb  1 20:54:18 joe acpid: client connected from 2474[0:0]
Feb  1 20:54:18 joe acpid: 1 client rule loaded
Feb  1 20:54:18 joe acpid: client 2474[0:0] has disconnected
Feb  1 20:54:18 joe acpid: client connected from 2461[0:0]
Feb  1 20:54:18 joe acpid: 1 client rule loaded
Feb  1 20:54:18 joe acpid: client 2461[0:0] has disconnected
Feb  1 20:54:18 joe acpid: client connected from 2466[0:0]
Feb  1 20:54:18 joe acpid: 1 client rule loaded
Feb  1 20:54:18 joe acpid: client 2466[0:0] has disconnected
Feb  1 20:54:18 joe acpid: client connected from 2469[0:0]
Feb  1 20:54:18 joe acpid: 1 client rule loaded
Feb  1 20:54:18 joe acpid: client 2469[0:0] has disconnected
Feb  1 20:54:18 joe acpid: client connected from 2482[0:0]
Feb  1 20:54:18 joe acpid: 1 client rule loaded
Feb  1 20:54:18 joe acpid: client 2482[0:0] has disconnected
Feb  1 20:54:18 joe acpid: client connected from 2438[0:0]
Feb  1 20:54:18 joe acpid: 1 client rule loaded
Feb  1 20:54:18 joe acpid: client 2438[0:0] has disconnected
Feb  1 20:54:18 joe acpid: client connected from 2454[0:0]
Feb  1 20:54:18 joe acpid: 1 client rule loaded
Feb  1 20:54:18 joe acpid: client 2454[0:0] has disconnected
Feb  1 20:54:18 joe acpid: client connected from 2463[0:0]
Feb  1 20:54:18 joe acpid: 1 client rule loaded
Feb  1 20:54:18 joe acpid: client 2463[0:0] has disconnected
Feb  1 20:54:18 joe acpid: client connected from 2751[0:0]
Feb  1 20:54:18 joe acpid: 1 client rule loaded
Feb  1 20:54:18 joe acpid: client 2751[0:0] has disconnected
Feb  1 20:54:18 joe acpid: client connected from 2803[0:0]
Feb  1 20:54:18 joe acpid: 1 client rule loaded
Feb  1 20:54:18 joe acpid: client 2803[0:0] has disconnected
Feb  1 20:54:18 joe acpid: client connected from 2754[0:0]
Feb  1 20:54:18 joe acpid: 1 client rule loaded
Feb  1 20:54:18 joe acpid: client 2754[0:0] has disconnected
Feb  1 20:54:18 joe acpid: client connected from 2762[0:0]
Feb  1 20:54:18 joe acpid: 1 client rule loaded
Feb  1 20:54:23 joe acpid: client 2762[0:0] has disconnected
Feb  1 20:54:23 joe acpid: client connected from 2758[0:0]
Feb  1 20:54:23 joe acpid: 1 client rule loaded
Feb  1 20:54:23 joe acpid: client connected from 2756[0:0]
Feb  1 20:54:23 joe acpid: 1 client rule loaded
Feb  1 20:54:23 joe acpid: client connected from 2766[0:0]
Feb  1 20:54:23 joe acpid: 1 client rule loaded
Feb  1 20:54:23 joe acpid: client connected from 2752[0:0]
Feb  1 20:54:23 joe acpid: 1 client rule loaded
Feb  1 20:54:23 joe acpid: client connected from 2770[0:0]
Feb  1 20:54:25 joe acpid: 1 client rule loaded
Feb  1 20:54:25 joe acpid: client 2758[0:0] has disconnected
Feb  1 20:54:25 joe acpid: client 2756[0:0] has disconnected
Feb  1 20:54:25 joe acpid: client 2766[0:0] has disconnected
Feb  1 20:54:25 joe acpid: client 2752[0:0] has disconnected
Feb  1 20:54:25 joe acpid: client 2770[0:0] has disconnected
Feb  1 20:54:25 joe acpid: client connected from 2764[0:0]
Feb  1 20:54:25 joe acpid: 1 client rule loaded
Feb  1 20:54:25 joe acpid: client 2764[0:0] has disconnected
Feb  1 20:54:25 joe acpid: client connected from 2780[0:0]
Feb  1 20:54:25 joe acpid: 1 client rule loaded
Feb  1 20:54:26 joe acpid: client 2780[0:0] has disconnected
Feb  1 20:54:26 joe acpid: client connected from 2774[0:0]
Feb  1 20:54:26 joe acpid: 1 client rule loaded
Feb  1 20:54:26 joe acpid: client 2774[0:0] has disconnected
Feb  1 20:54:26 joe acpid: client connected from 2776[0:0]
Feb  1 20:54:26 joe acpid: 1 client rule loaded
Feb  1 20:54:26 joe acpid: client 2776[0:0] has disconnected
Feb  1 20:54:26 joe acpid: client connected from 2772[0:0]
Feb  1 20:54:26 joe acpid: 1 client rule loaded
Feb  1 20:54:26 joe acpid: client 2772[0:0] has disconnected
Feb  1 20:54:26 joe acpid: client connected from 2778[0:0]
Feb  1 20:54:26 joe acpid: 1 client rule loaded
Feb  1 20:54:26 joe acpid: client 2778[0:0] has disconnected
Feb  1 20:54:26 joe acpid: client connected from 2792[0:0]
Feb  1 20:54:26 joe acpid: 1 client rule loaded
Feb  1 20:54:26 joe acpid: client 2792[0:0] has disconnected
Feb  1 20:54:26 joe acpid: client connected from 2805[0:0]
Feb  1 20:54:26 joe acpid: 1 client rule loaded
Feb  1 20:54:26 joe acpid: client 2805[0:0] has disconnected
Feb  1 20:54:26 joe acpid: client connected from 2816[0:0]
Feb  1 20:54:26 joe acpid: 1 client rule loaded
Feb  1 20:54:26 joe acpid: client 2816[0:0] has disconnected
Feb  1 20:54:27 joe acpid: client connected from 2808[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client 2808[0:0] has disconnected
Feb  1 20:54:27 joe acpid: client connected from 2790[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client 2790[0:0] has disconnected
Feb  1 20:54:27 joe acpid: client connected from 2784[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client 2784[0:0] has disconnected
Feb  1 20:54:27 joe acpid: client connected from 2810[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client 2810[0:0] has disconnected
Feb  1 20:54:27 joe acpid: client connected from 2804[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client 2804[0:0] has disconnected
Feb  1 20:54:27 joe acpid: client connected from 2768[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client 2768[0:0] has disconnected
Feb  1 20:54:27 joe acpid: client connected from 2797[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client 2797[0:0] has disconnected
Feb  1 20:54:27 joe acpid: client connected from 2786[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client 2786[0:0] has disconnected
Feb  1 20:54:27 joe acpid: client connected from 2795[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client 2795[0:0] has disconnected
Feb  1 20:54:27 joe acpid: client connected from 2801[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client 2801[0:0] has disconnected
Feb  1 20:54:27 joe acpid: client connected from 2812[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client 2812[0:0] has disconnected
Feb  1 20:54:27 joe acpid: client connected from 2814[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client 2814[0:0] has disconnected
Feb  1 20:54:27 joe acpid: client connected from 2818[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client 2818[0:0] has disconnected
Feb  1 20:54:27 joe acpid: client connected from 2788[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client 2788[0:0] has disconnected
Feb  1 20:54:27 joe acpid: client connected from 2820[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client 2820[0:0] has disconnected
Feb  1 20:54:27 joe acpid: client connected from 2799[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client connected from 3138[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client connected from 2782[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client connected from 3139[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client connected from 3351[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client connected from 3352[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client connected from 3354[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:27 joe acpid: client connected from 3353[0:0]
Feb  1 20:54:27 joe acpid: 1 client rule loaded
Feb  1 20:54:36 joe acpid: client 2799[0:0] has disconnected
Feb  1 20:54:36 joe acpid: client 3138[0:0] has disconnected
Feb  1 20:54:36 joe acpid: client 2782[0:0] has disconnected
Feb  1 20:54:36 joe acpid: client 3139[0:0] has disconnected
Feb  1 20:54:36 joe acpid: client 3351[0:0] has disconnected
Feb  1 20:54:36 joe acpid: client 3352[0:0] has disconnected
Feb  1 20:54:36 joe acpid: client 3354[0:0] has disconnected
Feb  1 20:54:36 joe acpid: client 3353[0:0] has disconnected
Feb  1 20:54:37 joe acpid: client connected from 3907[0:0]
Feb  1 20:54:38 joe acpid: 1 client rule loaded
Feb  1 20:54:38 joe acpid: client 3907[0:0] has disconnected
Feb  1 20:54:38 joe acpid: client connected from 3910[0:0]
Feb  1 20:54:38 joe acpid: 1 client rule loaded
Feb  1 20:54:38 joe acpid: client 3910[0:0] has disconnected
Feb  1 20:54:38 joe acpid: client connected from 3908[0:0]
Feb  1 20:54:38 joe acpid: 1 client rule loaded
Feb  1 20:54:38 joe acpid: client 3908[0:0] has disconnected
Feb  1 20:54:38 joe acpid: client connected from 3915[0:0]
Feb  1 20:54:38 joe acpid: 1 client rule loaded
Feb  1 20:54:38 joe acpid: client 3915[0:0] has disconnected
Feb  1 20:54:38 joe acpid: client connected from 3911[0:0]
Feb  1 20:54:38 joe acpid: 1 client rule loaded
Feb  1 20:54:38 joe acpid: client 3911[0:0] has disconnected
Feb  1 20:54:38 joe acpid: client connected from 3922[0:0]
Feb  1 20:54:38 joe acpid: 1 client rule loaded
Feb  1 20:54:38 joe acpid: client 3922[0:0] has disconnected
Feb  1 20:54:38 joe acpid: client connected from 3919[0:0]
Feb  1 20:54:38 joe acpid: 1 client rule loaded
Feb  1 20:54:38 joe acpid: client 3919[0:0] has disconnected
Feb  1 20:54:38 joe acpid: client connected from 3924[0:0]
Feb  1 20:54:38 joe acpid: 1 client rule loaded
Feb  1 20:54:39 joe acpid: client 3924[0:0] has disconnected
Feb  1 20:54:39 joe acpid: client connected from 3921[0:0]
Feb  1 20:54:39 joe acpid: 1 client rule loaded
Feb  1 20:54:39 joe acpid: client 3921[0:0] has disconnected
Feb  1 20:54:39 joe acpid: client connected from 3925[0:0]
Feb  1 20:54:39 joe acpid: 1 client rule loaded
Feb  1 20:54:39 joe acpid: client 3925[0:0] has disconnected
Feb  1 20:54:39 joe acpid: client connected from 3923[0:0]
Feb  1 20:54:39 joe acpid: 1 client rule loaded
Feb  1 20:54:39 joe acpid: client 3923[0:0] has disconnected
Feb  1 20:54:39 joe acpid: client connected from 3916[0:0]
Feb  1 20:54:39 joe acpid: 1 client rule loaded
Feb  1 20:54:39 joe acpid: client 3916[0:0] has disconnected
Feb  1 20:54:39 joe acpid: client connected from 3912[0:0]
Feb  1 20:54:39 joe acpid: 1 client rule loaded
Feb  1 20:54:39 joe acpid: client 3912[0:0] has disconnected
Feb  1 20:54:39 joe acpid: client connected from 3920[0:0]
Feb  1 20:54:39 joe acpid: 1 client rule loaded
Feb  1 20:54:39 joe acpid: client 3920[0:0] has disconnected
Feb  1 20:54:39 joe acpid: client connected from 3917[0:0]
Feb  1 20:54:39 joe acpid: 1 client rule loaded
Feb  1 20:54:39 joe acpid: client 3917[0:0] has disconnected
Feb  1 20:54:39 joe acpid: client connected from 4061[0:0]
Feb  1 20:54:39 joe acpid: 1 client rule loaded
Feb  1 20:54:39 joe acpid: client 4061[0:0] has disconnected
Feb  1 20:54:39 joe acpid: client connected from 4060[0:0]
Feb  1 20:54:39 joe acpid: 1 client rule loaded
Feb  1 20:54:39 joe acpid: client connected from 4062[0:0]
Feb  1 20:54:39 joe acpid: 1 client rule loaded
Feb  1 20:54:39 joe acpid: client connected from 4063[0:0]
Feb  1 20:54:39 joe acpid: 1 client rule loaded
Feb  1 20:54:39 joe acpid: client connected from 4068[0:0]
Feb  1 20:54:39 joe acpid: 1 client rule loaded
Feb  1 20:54:39 joe acpid: client connected from 4064[0:0]
Feb  1 20:54:39 joe acpid: 1 client rule loaded
Feb  1 20:54:39 joe acpid: client connected from 4329[0:0]
Feb  1 20:54:39 joe acpid: 1 client rule loaded
Feb  1 20:54:39 joe acpid: client connected from 4332[0:0]
Feb  1 20:54:39 joe acpid: 1 client rule loaded
Feb  1 20:54:39 joe acpid: client connected from 4341[0:0]
Feb  1 20:54:39 joe acpid: 1 client rule loaded
Feb  1 20:54:50 joe acpid: client 4060[0:0] has disconnected
Feb  1 20:54:50 joe acpid: client 4062[0:0] has disconnected
Feb  1 20:54:50 joe acpid: client 4063[0:0] has disconnected
Feb  1 20:54:50 joe acpid: client 4068[0:0] has disconnected
Feb  1 20:54:50 joe acpid: client 4064[0:0] has disconnected
Feb  1 20:54:50 joe acpid: client 4329[0:0] has disconnected
Feb  1 20:54:50 joe acpid: client 4332[0:0] has disconnected
Feb  1 20:54:51 joe acpid: client 4341[0:0] has disconnected
Feb  1 20:54:53 joe acpid: client connected from 4612[0:0]
Feb  1 20:54:53 joe acpid: 1 client rule loaded
Feb  1 20:54:53 joe acpid: client 4612[0:0] has disconnected
Feb  1 20:54:53 joe acpid: client connected from 4614[0:0]
Feb  1 20:54:53 joe acpid: 1 client rule loaded
Feb  1 20:54:53 joe acpid: client 4614[0:0] has disconnected
Feb  1 20:54:53 joe acpid: client connected from 4618[0:0]
Feb  1 20:54:53 joe acpid: 1 client rule loaded
Feb  1 20:54:54 joe acpid: client 4618[0:0] has disconnected
Feb  1 20:54:54 joe acpid: client connected from 4611[0:0]
Feb  1 20:54:54 joe acpid: 1 client rule loaded
Feb  1 20:54:54 joe acpid: client 4611[0:0] has disconnected
Feb  1 20:54:54 joe acpid: client connected from 4616[0:0]
Feb  1 20:54:54 joe acpid: 1 client rule loaded
Feb  1 20:54:55 joe acpid: client 4616[0:0] has disconnected
Feb  1 20:54:55 joe acpid: client connected from 4633[0:0]
Feb  1 20:54:55 joe acpid: 1 client rule loaded
Feb  1 20:54:56 joe acpid: client 4633[0:0] has disconnected
Feb  1 20:54:56 joe acpid: client connected from 4634[0:0]
Feb  1 20:54:56 joe acpid: 1 client rule loaded
Feb  1 20:54:56 joe acpid: client 4634[0:0] has disconnected
Feb  1 20:54:56 joe acpid: client connected from 4632[0:0]
Feb  1 20:54:56 joe acpid: 1 client rule loaded
Feb  1 20:54:56 joe acpid: client 4632[0:0] has disconnected
Feb  1 20:54:56 joe acpid: client connected from 4636[0:0]
Feb  1 20:54:56 joe acpid: 1 client rule loaded
Feb  1 20:54:56 joe acpid: client 4636[0:0] has disconnected
Feb  1 20:54:56 joe acpid: client connected from 4640[0:0]
Feb  1 20:54:56 joe acpid: 1 client rule loaded
Feb  1 20:54:56 joe acpid: client 4640[0:0] has disconnected
Feb  1 20:54:56 joe acpid: client connected from 4638[0:0]
Feb  1 20:54:56 joe acpid: 1 client rule loaded
Feb  1 20:54:56 joe acpid: client 4638[0:0] has disconnected
Feb  1 20:54:56 joe acpid: client connected from 4637[0:0]
Feb  1 20:54:56 joe acpid: 1 client rule loaded
Feb  1 20:54:56 joe acpid: client 4637[0:0] has disconnected
Feb  1 20:54:56 joe acpid: client connected from 4641[0:0]
Feb  1 20:54:56 joe acpid: 1 client rule loaded
Feb  1 20:54:56 joe acpid: client 4641[0:0] has disconnected
Feb  1 20:54:58 joe acpid: client connected from 4619[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client 4619[0:0] has disconnected
Feb  1 20:54:58 joe acpid: client connected from 4639[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client 4639[0:0] has disconnected
Feb  1 20:54:58 joe acpid: client connected from 4649[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client 4649[0:0] has disconnected
Feb  1 20:54:58 joe acpid: client connected from 4646[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client 4646[0:0] has disconnected
Feb  1 20:54:58 joe acpid: client connected from 4645[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client 4645[0:0] has disconnected
Feb  1 20:54:58 joe acpid: client connected from 4648[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client 4648[0:0] has disconnected
Feb  1 20:54:58 joe acpid: client connected from 4644[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client 4644[0:0] has disconnected
Feb  1 20:54:58 joe acpid: client connected from 4642[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client 4642[0:0] has disconnected
Feb  1 20:54:58 joe acpid: client connected from 4658[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client 4658[0:0] has disconnected
Feb  1 20:54:58 joe acpid: client connected from 4650[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client 4650[0:0] has disconnected
Feb  1 20:54:58 joe acpid: client connected from 4657[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client 4657[0:0] has disconnected
Feb  1 20:54:58 joe acpid: client connected from 4660[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client 4660[0:0] has disconnected
Feb  1 20:54:58 joe acpid: client connected from 4654[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client 4654[0:0] has disconnected
Feb  1 20:54:58 joe acpid: client connected from 4656[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client 4656[0:0] has disconnected
Feb  1 20:54:58 joe acpid: client connected from 4655[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client 4655[0:0] has disconnected
Feb  1 20:54:58 joe acpid: client connected from 4659[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 4652[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 4927[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 4653[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 4926[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5141[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 4925[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5140[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5139[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5138[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5151[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5162[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5178[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5153[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5159[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5155[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5425[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5436[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5446[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5460[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5439[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5469[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5468[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5473[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5454[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5457[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5462[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5461[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5450[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5466[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5471[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5444[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5437[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5448[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5427[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5440[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5474[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5452[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5458[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5475[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5463[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5451[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5449[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5443[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe acpid: client connected from 5459[0:0]
Feb  1 20:54:58 joe acpid: 1 client rule loaded
Feb  1 20:54:58 joe pulseaudio[5644]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:54:59 joe dbus[1463]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Feb  1 20:54:59 joe dbus[1463]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Feb  1 20:55:09 joe acpid: client 4659[0:0] has disconnected
Feb  1 20:55:09 joe acpid: client 4652[0:0] has disconnected
Feb  1 20:55:09 joe acpid: client 4927[0:0] has disconnected
Feb  1 20:55:09 joe acpid: client 4653[0:0] has disconnected
Feb  1 20:55:09 joe acpid: client 4926[0:0] has disconnected
Feb  1 20:55:09 joe acpid: client 5141[0:0] has disconnected
Feb  1 20:55:09 joe acpid: client 4925[0:0] has disconnected
Feb  1 20:55:09 joe acpid: client 5140[0:0] has disconnected
Feb  1 20:55:09 joe acpid: client 5139[0:0] has disconnected
Feb  1 20:55:09 joe acpid: client 5138[0:0] has disconnected
Feb  1 20:55:11 joe gnome-session[3620]: WARNING: Failed to start app: Unable to start application: Kindprozess »/usr/lib/gnome-volume-manager/gnome-volume-manager« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) 
Feb  1 20:55:13 joe acpid: client 5151[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5162[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5178[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5153[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5159[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5155[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5425[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5436[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5446[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5460[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5439[0:0] has disconnected
Feb  1 20:55:13 joe pulseaudio[5991]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:55:13 joe gnome-session[3620]: WARNING: Failed to start app: Unable to start application: Kindprozess »beagle-search« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) 
Feb  1 20:55:13 joe acpid: client 5469[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5468[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5473[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5454[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5457[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5462[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5461[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5450[0:0] has disconnected
Feb  1 20:55:13 joe acpid: client 5466[0:0] has disconnected
Feb  1 20:55:15 joe acpid: client 5471[0:0] has disconnected
Feb  1 20:55:15 joe acpid: client 5444[0:0] has disconnected
Feb  1 20:55:15 joe acpid: client 5437[0:0] has disconnected
Feb  1 20:55:15 joe acpid: client 5448[0:0] has disconnected
Feb  1 20:55:15 joe acpid: client 5427[0:0] has disconnected
Feb  1 20:55:15 joe acpid: client 5440[0:0] has disconnected
Feb  1 20:55:15 joe acpid: client 5474[0:0] has disconnected
Feb  1 20:55:15 joe acpid: client 5452[0:0] has disconnected
Feb  1 20:55:15 joe acpid: client 5458[0:0] has disconnected
Feb  1 20:55:15 joe acpid: client 5475[0:0] has disconnected
Feb  1 20:55:15 joe acpid: client 5463[0:0] has disconnected
Feb  1 20:55:15 joe acpid: client 5451[0:0] has disconnected
Feb  1 20:55:15 joe gnome-session[3620]: WARNING: Failed to start app: Unable to start application: Kindprozess »beagled« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) 
Feb  1 20:55:15 joe acpid: client 5449[0:0] has disconnected
Feb  1 20:55:15 joe acpid: client 5443[0:0] has disconnected
Feb  1 20:55:15 joe acpid: client 5459[0:0] has disconnected
Feb  1 20:55:15 joe acpid: client connected from 5804[0:0]
Feb  1 20:55:15 joe acpid: 1 client rule loaded
Feb  1 20:55:15 joe acpid: client 5804[0:0] has disconnected
Feb  1 20:55:15 joe acpid: client connected from 5802[0:0]
Feb  1 20:55:15 joe acpid: 1 client rule loaded
Feb  1 20:55:15 joe acpid: client 5802[0:0] has disconnected
Feb  1 20:55:24 joe acpid: client connected from 5813[0:0]
Feb  1 20:55:37 joe acpid: 1 client rule loaded
Feb  1 20:55:37 joe acpid: client 5813[0:0] has disconnected
Feb  1 20:55:37 joe acpid: client connected from 5810[0:0]
Feb  1 20:55:37 joe acpid: 1 client rule loaded
Feb  1 20:55:37 joe acpid: client 5810[0:0] has disconnected
Feb  1 20:55:37 joe acpid: client connected from 5809[0:0]
Feb  1 20:55:37 joe acpid: 1 client rule loaded
Feb  1 20:55:37 joe acpid: client 5809[0:0] has disconnected
Feb  1 20:55:37 joe acpid: client connected from 5812[0:0]
Feb  1 20:55:37 joe pulseaudio[6471]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:55:40 joe pulseaudio[6906]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:55:40 joe acpid: 1 client rule loaded
Feb  1 20:55:40 joe acpid: client 5812[0:0] has disconnected
Feb  1 20:55:40 joe acpid: client connected from 5823[0:0]
Feb  1 20:55:40 joe acpid: 1 client rule loaded
Feb  1 20:55:40 joe acpid: client 5823[0:0] has disconnected
Feb  1 20:55:40 joe acpid: client connected from 5819[0:0]
Feb  1 20:55:40 joe acpid: 1 client rule loaded
Feb  1 20:55:40 joe acpid: client 5819[0:0] has disconnected
Feb  1 20:55:40 joe acpid: client connected from 5821[0:0]
Feb  1 20:55:40 joe acpid: 1 client rule loaded
Feb  1 20:55:40 joe acpid: client 5821[0:0] has disconnected
Feb  1 20:55:40 joe acpid: client connected from 5825[0:0]
Feb  1 20:55:40 joe acpid: 1 client rule loaded
Feb  1 20:55:40 joe acpid: client 5825[0:0] has disconnected
Feb  1 20:55:40 joe acpid: client connected from 5817[0:0]
Feb  1 20:55:40 joe acpid: 1 client rule loaded
Feb  1 20:55:40 joe acpid: client 5817[0:0] has disconnected
Feb  1 20:55:40 joe acpid: client connected from 5818[0:0]
Feb  1 20:55:40 joe acpid: 1 client rule loaded
Feb  1 20:55:40 joe acpid: client 5818[0:0] has disconnected
Feb  1 20:55:40 joe acpid: client connected from 5815[0:0]
Feb  1 20:55:40 joe pulseaudio[6602]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:55:42 joe pulseaudio[7049]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client 5815[0:0] has disconnected
Feb  1 20:55:42 joe acpid: client connected from 5824[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client 5824[0:0] has disconnected
Feb  1 20:55:42 joe acpid: client connected from 5822[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client 5822[0:0] has disconnected
Feb  1 20:55:42 joe acpid: client connected from 5826[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client 5826[0:0] has disconnected
Feb  1 20:55:42 joe acpid: client connected from 5806[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client 5806[0:0] has disconnected
Feb  1 20:55:42 joe acpid: client connected from 5803[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client 5803[0:0] has disconnected
Feb  1 20:55:42 joe acpid: client connected from 5820[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client 5820[0:0] has disconnected
Feb  1 20:55:42 joe acpid: client connected from 5814[0:0]
Feb  1 20:55:42 joe pulseaudio[7345]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:55:42 joe dbus[1463]: [system] Activating service name='org.debian.apt' (using servicehelper)
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client 5814[0:0] has disconnected
Feb  1 20:55:42 joe acpid: client connected from 6087[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client 6087[0:0] has disconnected
Feb  1 20:55:42 joe acpid: client connected from 5805[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client 5805[0:0] has disconnected
Feb  1 20:55:42 joe acpid: client connected from 6304[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client 6304[0:0] has disconnected
Feb  1 20:55:42 joe acpid: client connected from 6302[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client 6302[0:0] has disconnected
Feb  1 20:55:42 joe acpid: client connected from 6306[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client 6306[0:0] has disconnected
Feb  1 20:55:42 joe acpid: client connected from 6310[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client 6310[0:0] has disconnected
Feb  1 20:55:42 joe acpid: client connected from 6305[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client 6305[0:0] has disconnected
Feb  1 20:55:42 joe acpid: client connected from 6313[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client connected from 6317[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client connected from 6312[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client connected from 6303[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client connected from 6311[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client connected from 6318[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client connected from 6314[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client connected from 6316[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client connected from 6536[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client connected from 6537[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client connected from 6541[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client connected from 6544[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client connected from 6543[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:42 joe acpid: client connected from 6545[0:0]
Feb  1 20:55:42 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 6802[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 6803[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 6804[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 6805[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 7023[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 7041[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 7036[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 7029[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 7027[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 7038[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 7026[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 7039[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 7024[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 7030[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 7025[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 7040[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 7037[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 7327[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 7328[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:55:43 joe acpid: client connected from 7332[0:0]
Feb  1 20:55:43 joe acpid: 1 client rule loaded
Feb  1 20:56:08 joe pulseaudio[7495]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:08 joe acpid: client 6313[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 6317[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 6312[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 6303[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 6311[0:0] has disconnected
Feb  1 20:56:08 joe pulseaudio[7706]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:08 joe acpid: client 6318[0:0] has disconnected
Feb  1 20:56:08 joe goa[7265]: goa-daemon version 3.2.1 starting [main.c:112, main()]
Feb  1 20:56:08 joe pulseaudio[8318]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:08 joe acpid: client 6314[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 6316[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 6536[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 6537[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 6541[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 6544[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 6543[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 6545[0:0] has disconnected
Feb  1 20:56:08 joe AptDaemon: INFO: Initializing daemon
Feb  1 20:56:08 joe acpid: client 6802[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 6803[0:0] has disconnected
Feb  1 20:56:08 joe dbus[1463]: [system] Activating service name='org.gnome.SettingsDaemon.DateTimeMechanism' (using servicehelper)
Feb  1 20:56:08 joe acpid: client 6804[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 6805[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 7023[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 7041[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 7036[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 7029[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 7027[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 7038[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 7026[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 7039[0:0] has disconnected
Feb  1 20:56:08 joe dbus[1463]: [system] Failed to activate service 'org.debian.apt': timed out
Feb  1 20:56:08 joe acpid: client 7024[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 7030[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 7025[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 7040[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 7037[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 7327[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 7328[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client 7332[0:0] has disconnected
Feb  1 20:56:08 joe acpid: client connected from 7538[0:0]
Feb  1 20:56:08 joe acpid: 1 client rule loaded
Feb  1 20:56:08 joe acpid: client 7538[0:0] has disconnected
Feb  1 20:56:08 joe pulseaudio[9095]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:11 joe acpid: client connected from 7539[0:0]
Feb  1 20:56:11 joe acpid: 1 client rule loaded
Feb  1 20:56:11 joe acpid: client 7539[0:0] has disconnected
Feb  1 20:56:11 joe acpid: client connected from 7537[0:0]
Feb  1 20:56:11 joe acpid: 1 client rule loaded
Feb  1 20:56:11 joe acpid: client 7537[0:0] has disconnected
Feb  1 20:56:11 joe acpid: client connected from 7544[0:0]
Feb  1 20:56:11 joe acpid: 1 client rule loaded
Feb  1 20:56:11 joe acpid: client 7544[0:0] has disconnected
Feb  1 20:56:11 joe acpid: client connected from 7549[0:0]
Feb  1 20:56:11 joe dbus[1463]: [system] Activated service 'org.gnome.SettingsDaemon.DateTimeMechanism' failed: Launch helper exited with unknown return code 1
Feb  1 20:56:12 joe acpid: 1 client rule loaded
Feb  1 20:56:12 joe acpid: client 7549[0:0] has disconnected
Feb  1 20:56:12 joe acpid: client connected from 7545[0:0]
Feb  1 20:56:12 joe acpid: 1 client rule loaded
Feb  1 20:56:12 joe acpid: client 7545[0:0] has disconnected
Feb  1 20:56:12 joe acpid: client connected from 7546[0:0]
Feb  1 20:56:12 joe acpid: 1 client rule loaded
Feb  1 20:56:12 joe acpid: client 7546[0:0] has disconnected
Feb  1 20:56:12 joe acpid: client connected from 7548[0:0]
Feb  1 20:56:12 joe acpid: 1 client rule loaded
Feb  1 20:56:12 joe acpid: client 7548[0:0] has disconnected
Feb  1 20:56:12 joe acpid: client connected from 7561[0:0]
Feb  1 20:56:12 joe acpid: 1 client rule loaded
Feb  1 20:56:13 joe acpid: client 7561[0:0] has disconnected
Feb  1 20:56:13 joe acpid: client connected from 7562[0:0]
Feb  1 20:56:13 joe acpid: 1 client rule loaded
Feb  1 20:56:13 joe acpid: client 7562[0:0] has disconnected
Feb  1 20:56:13 joe acpid: client connected from 7559[0:0]
Feb  1 20:56:13 joe acpid: 1 client rule loaded
Feb  1 20:56:13 joe acpid: client 7559[0:0] has disconnected
Feb  1 20:56:13 joe acpid: client connected from 7563[0:0]
Feb  1 20:56:13 joe acpid: 1 client rule loaded
Feb  1 20:56:13 joe acpid: client 7563[0:0] has disconnected
Feb  1 20:56:13 joe acpid: client connected from 7556[0:0]
Feb  1 20:56:13 joe pulseaudio[9350]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:13 joe acpid: 1 client rule loaded
Feb  1 20:56:13 joe acpid: client 7556[0:0] has disconnected
Feb  1 20:56:13 joe acpid: client connected from 7564[0:0]
Feb  1 20:56:13 joe acpid: 1 client rule loaded
Feb  1 20:56:13 joe acpid: client 7564[0:0] has disconnected
Feb  1 20:56:13 joe acpid: client connected from 7565[0:0]
Feb  1 20:56:13 joe acpid: 1 client rule loaded
Feb  1 20:56:13 joe acpid: client 7565[0:0] has disconnected
Feb  1 20:56:13 joe acpid: client connected from 7776[0:0]
Feb  1 20:56:13 joe acpid: 1 client rule loaded
Feb  1 20:56:13 joe acpid: client 7776[0:0] has disconnected
Feb  1 20:56:13 joe acpid: client connected from 7820[0:0]
Feb  1 20:56:13 joe acpid: 1 client rule loaded
Feb  1 20:56:13 joe acpid: client 7820[0:0] has disconnected
Feb  1 20:56:13 joe acpid: client connected from 7775[0:0]
Feb  1 20:56:13 joe acpid: 1 client rule loaded
Feb  1 20:56:13 joe acpid: client 7775[0:0] has disconnected
Feb  1 20:56:13 joe acpid: client connected from 7779[0:0]
Feb  1 20:56:13 joe acpid: 1 client rule loaded
Feb  1 20:56:13 joe acpid: client 7779[0:0] has disconnected
Feb  1 20:56:13 joe acpid: client connected from 7822[0:0]
Feb  1 20:56:13 joe acpid: 1 client rule loaded
Feb  1 20:56:13 joe acpid: client 7822[0:0] has disconnected
Feb  1 20:56:13 joe acpid: client connected from 7836[0:0]
Feb  1 20:56:13 joe acpid: 1 client rule loaded
Feb  1 20:56:13 joe acpid: client 7836[0:0] has disconnected
Feb  1 20:56:13 joe acpid: client connected from 7792[0:0]
Feb  1 20:56:13 joe acpid: 1 client rule loaded
Feb  1 20:56:13 joe acpid: client 7792[0:0] has disconnected
Feb  1 20:56:13 joe acpid: client connected from 7840[0:0]
Feb  1 20:56:13 joe acpid: 1 client rule loaded
Feb  1 20:56:13 joe acpid: client 7840[0:0] has disconnected
Feb  1 20:56:13 joe acpid: client connected from 7824[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 7824[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 7823[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7842[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7839[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7806[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7826[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7794[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7805[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7843[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7844[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7845[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7803[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7829[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7777[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7825[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7847[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7833[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7831[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7800[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7853[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7862[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7830[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7863[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7865[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7867[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7864[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7849[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7782[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7868[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7869[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7832[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7811[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7870[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7796[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7816[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7871[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7793[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7798[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7810[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7815[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7874[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7876[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7877[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7817[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7879[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7809[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7814[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7881[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7882[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7880[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7884[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7883[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7885[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7795[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 7829[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 7886[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7875[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 7843[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 7910[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 7794[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 7808[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 7803[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7832[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 7900[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 7862[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 7781[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7903[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7902[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7901[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7904[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7852[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7812[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7909[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7780[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7797[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7801[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7804[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7908[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7828[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7851[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7835[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7813[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7856[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7878[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7841[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7821[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7837[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7838[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7827[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7846[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 7839[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7845[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7777[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7825[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7847[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7833[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7831[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7853[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7830[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7863[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7865[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7867[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7864[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7849[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7868[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7870[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7796[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7876[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7817[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7879[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7814[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7881[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7883[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7885[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7795[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7875[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 7807[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 7799[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 7844[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7782[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7811[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7815[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7882[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7880[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7886[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7910[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7808[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7900[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7781[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7903[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7901[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7904[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7852[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7812[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7780[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7908[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7841[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 7834[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 7842[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7826[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7800[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7869[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7816[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7871[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7793[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7798[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7810[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7874[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7877[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7809[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7884[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7856[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 7802[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 7835[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 7818[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 7878[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7807[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 8505[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 7851[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7834[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 8506[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 8506[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 8510[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 7902[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7909[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7797[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7804[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7828[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7813[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7821[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7838[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client 7846[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 8512[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 8512[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 8509[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 8509[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 8511[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 8511[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 8507[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 8507[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 8519[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 8537[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 8529[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 8522[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 8526[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe pulseaudio[9371]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:14 joe acpid: client connected from 8533[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client 7827[0:0] has disconnected
Feb  1 20:56:14 joe acpid: client connected from 8532[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 8535[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 8561[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:14 joe acpid: client connected from 8558[0:0]
Feb  1 20:56:14 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8559[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8560[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8566[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8555[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8564[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8551[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client 7805[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client 7801[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client 7799[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client 8510[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client 8533[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client 8558[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client 8566[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client connected from 8556[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client 7837[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client 7818[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client 8505[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client connected from 8557[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client 7802[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client 8532[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client connected from 8568[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client 7823[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client 8561[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client 8555[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client connected from 8552[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8562[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8596[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client 8596[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client connected from 7819[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8553[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client 7806[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client 8519[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client 8522[0:0] has disconnected
Feb  1 20:56:15 joe acpid: client connected from 8550[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8567[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8554[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8563[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8565[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8592[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8595[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8591[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8589[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8590[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8588[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8593[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:15 joe acpid: client connected from 8594[0:0]
Feb  1 20:56:15 joe acpid: 1 client rule loaded
Feb  1 20:56:30 joe pulseaudio[9606]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:30 joe pulseaudio[9609]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:31 joe pulseaudio[9848]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:31 joe pulseaudio[9847]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:34 joe pulseaudio[10125]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:34 joe pulseaudio[10127]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:39 joe pulseaudio[10390]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:39 joe pulseaudio[10388]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:45 joe pulseaudio[10649]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:45 joe pulseaudio[10650]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:50 joe acpid: client 8537[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8529[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8526[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8535[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8559[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8560[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8564[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8551[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8556[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8557[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8568[0:0] has disconnected
Feb  1 20:56:50 joe pulseaudio[10850]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:50 joe pulseaudio[10851]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:50 joe acpid: client 8552[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8562[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 7819[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8553[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8550[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8567[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8554[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8563[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8565[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8592[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8595[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8591[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8589[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8590[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8588[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8593[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client 8594[0:0] has disconnected
Feb  1 20:56:50 joe acpid: client connected from 10822[0:0]
Feb  1 20:56:50 joe acpid: 1 client rule loaded
Feb  1 20:56:56 joe acpid: client 10822[0:0] has disconnected
Feb  1 20:56:56 joe acpid: client connected from 11082[0:0]
Feb  1 20:56:56 joe acpid: 1 client rule loaded
Feb  1 20:56:56 joe acpid: client connected from 11081[0:0]
Feb  1 20:56:56 joe acpid: 1 client rule loaded
Feb  1 20:56:56 joe acpid: client connected from 11085[0:0]
Feb  1 20:56:56 joe acpid: 1 client rule loaded
Feb  1 20:56:56 joe acpid: client 11082[0:0] has disconnected
Feb  1 20:56:56 joe acpid: client 11081[0:0] has disconnected
Feb  1 20:56:56 joe acpid: client 11085[0:0] has disconnected
Feb  1 20:56:56 joe pulseaudio[11183]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:56:56 joe acpid: client connected from 11084[0:0]
Feb  1 20:56:56 joe acpid: 1 client rule loaded
Feb  1 20:56:56 joe acpid: client 11084[0:0] has disconnected
Feb  1 20:56:56 joe acpid: client connected from 11086[0:0]
Feb  1 20:56:56 joe acpid: 1 client rule loaded
Feb  1 20:56:56 joe acpid: client 11086[0:0] has disconnected
Feb  1 20:56:56 joe acpid: client connected from 11083[0:0]
Feb  1 20:56:56 joe acpid: 1 client rule loaded
Feb  1 20:56:56 joe pulseaudio[11184]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:02 joe acpid: client 11083[0:0] has disconnected
Feb  1 20:57:02 joe acpid: client connected from 11358[0:0]
Feb  1 20:57:02 joe acpid: 1 client rule loaded
Feb  1 20:57:02 joe acpid: client connected from 11359[0:0]
Feb  1 20:57:02 joe acpid: 1 client rule loaded
Feb  1 20:57:02 joe acpid: client connected from 11355[0:0]
Feb  1 20:57:02 joe acpid: 1 client rule loaded
Feb  1 20:57:02 joe acpid: client connected from 11353[0:0]
Feb  1 20:57:02 joe acpid: 1 client rule loaded
Feb  1 20:57:02 joe acpid: client 11355[0:0] has disconnected
Feb  1 20:57:02 joe acpid: client 11353[0:0] has disconnected
Feb  1 20:57:03 joe pulseaudio[11426]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:03 joe acpid: client connected from 11356[0:0]
Feb  1 20:57:03 joe acpid: 1 client rule loaded
Feb  1 20:57:03 joe acpid: client 11358[0:0] has disconnected
Feb  1 20:57:03 joe acpid: client 11359[0:0] has disconnected
Feb  1 20:57:03 joe acpid: client 11356[0:0] has disconnected
Feb  1 20:57:03 joe acpid: client connected from 11354[0:0]
Feb  1 20:57:03 joe acpid: 1 client rule loaded
Feb  1 20:57:03 joe acpid: client 11354[0:0] has disconnected
Feb  1 20:57:03 joe acpid: client connected from 11357[0:0]
Feb  1 20:57:03 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client 11357[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client connected from 11626[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client connected from 11633[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client connected from 11625[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client connected from 11627[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client connected from 11629[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client 11626[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client 11633[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client 11625[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client 11627[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client 11629[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client connected from 11638[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client 11638[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client connected from 11640[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client 11640[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client connected from 11639[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client 11639[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client connected from 11641[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client 11641[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client connected from 11647[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client 11647[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client connected from 11644[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client 11644[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client connected from 11632[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client 11632[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client connected from 11646[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client 11646[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client connected from 11631[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client 11631[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client connected from 11655[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client 11655[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client connected from 11665[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client 11665[0:0] has disconnected
Feb  1 20:57:07 joe acpid: client connected from 11657[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client connected from 11654[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client connected from 11653[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:07 joe acpid: client connected from 11658[0:0]
Feb  1 20:57:07 joe acpid: 1 client rule loaded
Feb  1 20:57:08 joe pulseaudio[11792]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:15 joe acpid: client 11657[0:0] has disconnected
Feb  1 20:57:15 joe acpid: client 11654[0:0] has disconnected
Feb  1 20:57:15 joe acpid: client 11653[0:0] has disconnected
Feb  1 20:57:15 joe acpid: client 11658[0:0] has disconnected
Feb  1 20:57:15 joe acpid: client connected from 11939[0:0]
Feb  1 20:57:15 joe acpid: 1 client rule loaded
Feb  1 20:57:15 joe acpid: client connected from 11935[0:0]
Feb  1 20:57:15 joe acpid: 1 client rule loaded
Feb  1 20:57:15 joe acpid: client connected from 11934[0:0]
Feb  1 20:57:15 joe acpid: 1 client rule loaded
Feb  1 20:57:15 joe acpid: client 11939[0:0] has disconnected
Feb  1 20:57:15 joe pulseaudio[12150]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:15 joe acpid: client 11935[0:0] has disconnected
Feb  1 20:57:15 joe acpid: client 11934[0:0] has disconnected
Feb  1 20:57:15 joe acpid: client connected from 11940[0:0]
Feb  1 20:57:15 joe acpid: 1 client rule loaded
Feb  1 20:57:15 joe acpid: client 11940[0:0] has disconnected
Feb  1 20:57:15 joe acpid: client connected from 11942[0:0]
Feb  1 20:57:15 joe acpid: 1 client rule loaded
Feb  1 20:57:15 joe acpid: client 11942[0:0] has disconnected
Feb  1 20:57:15 joe acpid: client connected from 11941[0:0]
Feb  1 20:57:15 joe acpid: 1 client rule loaded
Feb  1 20:57:16 joe acpid: client 11941[0:0] has disconnected
Feb  1 20:57:16 joe acpid: client connected from 11976[0:0]
Feb  1 20:57:16 joe acpid: 1 client rule loaded
Feb  1 20:57:16 joe acpid: client 11976[0:0] has disconnected
Feb  1 20:57:16 joe acpid: client connected from 11931[0:0]
Feb  1 20:57:16 joe acpid: 1 client rule loaded
Feb  1 20:57:16 joe acpid: client 11931[0:0] has disconnected
Feb  1 20:57:16 joe acpid: client connected from 11946[0:0]
Feb  1 20:57:16 joe acpid: 1 client rule loaded
Feb  1 20:57:16 joe acpid: client 11946[0:0] has disconnected
Feb  1 20:57:16 joe acpid: client connected from 11945[0:0]
Feb  1 20:57:18 joe acpid: 1 client rule loaded
Feb  1 20:57:18 joe acpid: client 11945[0:0] has disconnected
Feb  1 20:57:18 joe acpid: client connected from 11944[0:0]
Feb  1 20:57:18 joe acpid: 1 client rule loaded
Feb  1 20:57:18 joe acpid: client 11944[0:0] has disconnected
Feb  1 20:57:18 joe acpid: client connected from 11948[0:0]
Feb  1 20:57:18 joe acpid: 1 client rule loaded
Feb  1 20:57:18 joe acpid: client 11948[0:0] has disconnected
Feb  1 20:57:18 joe acpid: client connected from 11947[0:0]
Feb  1 20:57:18 joe acpid: 1 client rule loaded
Feb  1 20:57:18 joe acpid: client 11947[0:0] has disconnected
Feb  1 20:57:20 joe acpid: client connected from 11950[0:0]
Feb  1 20:57:20 joe acpid: 1 client rule loaded
Feb  1 20:57:20 joe acpid: client 11950[0:0] has disconnected
Feb  1 20:57:20 joe acpid: client connected from 11949[0:0]
Feb  1 20:57:20 joe acpid: 1 client rule loaded
Feb  1 20:57:20 joe acpid: client 11949[0:0] has disconnected
Feb  1 20:57:20 joe acpid: client connected from 11938[0:0]
Feb  1 20:57:20 joe acpid: 1 client rule loaded
Feb  1 20:57:20 joe acpid: client 11938[0:0] has disconnected
Feb  1 20:57:20 joe acpid: client connected from 11936[0:0]
Feb  1 20:57:20 joe acpid: 1 client rule loaded
Feb  1 20:57:20 joe acpid: client 11936[0:0] has disconnected
Feb  1 20:57:20 joe acpid: client connected from 11933[0:0]
Feb  1 20:57:20 joe acpid: 1 client rule loaded
Feb  1 20:57:20 joe acpid: client 11933[0:0] has disconnected
Feb  1 20:57:20 joe acpid: client connected from 11965[0:0]
Feb  1 20:57:20 joe acpid: 1 client rule loaded
Feb  1 20:57:20 joe acpid: client 11965[0:0] has disconnected
Feb  1 20:57:20 joe acpid: client connected from 11968[0:0]
Feb  1 20:57:20 joe acpid: 1 client rule loaded
Feb  1 20:57:20 joe acpid: client 11968[0:0] has disconnected
Feb  1 20:57:20 joe acpid: client connected from 11967[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 11967[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 11932[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 11932[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 11969[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 11969[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 11966[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 11966[0:0] has disconnected
Feb  1 20:57:23 joe pulseaudio[12542]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:23 joe acpid: client connected from 11988[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 11988[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 11978[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 11978[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 12008[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 12008[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 12010[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 12010[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 11981[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 11981[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 11982[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 11982[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 11991[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 11991[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 12011[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 12011[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 11984[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 11984[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 11970[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 11970[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 11977[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 11977[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 11989[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 11989[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 12003[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 11980[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 11985[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12013[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12002[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12005[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12012[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12009[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12014[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12048[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12007[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12017[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12006[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12019[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12037[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12016[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12001[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12022[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12021[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12018[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12047[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12054[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12053[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12050[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12051[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12052[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 11986[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12044[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12317[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12319[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12323[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12321[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12325[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12330[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12322[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12336[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12331[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12352[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12346[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12329[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12345[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12350[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12356[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12355[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12347[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 12037[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 12342[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12332[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12349[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12335[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12353[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12391[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12395[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12341[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12394[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12327[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12398[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12396[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12393[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12387[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12351[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12411[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12413[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12340[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12388[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12412[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12337[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12389[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12410[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 12053[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 12378[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12334[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12338[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 12005[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12009[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12014[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12007[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12017[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12001[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12022[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12317[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12319[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12323[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12321[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12325[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12346[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12350[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12349[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12335[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12391[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12395[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12398[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 12380[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 12003[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12013[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client 12002[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 12381[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12382[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12344[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12386[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12383[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client 12387[0:0] has disconnected
Feb  1 20:57:23 joe acpid: client connected from 12354[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12385[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:23 joe acpid: client connected from 12379[0:0]
Feb  1 20:57:23 joe acpid: 1 client rule loaded
Feb  1 20:57:24 joe pulseaudio[12671]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:28 joe pulseaudio[12712]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:30 joe pulseaudio[12752]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:38 joe pulseaudio[13002]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:38 joe pulseaudio[13003]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:41 joe pulseaudio[13240]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:41 joe pulseaudio[13241]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:47 joe pulseaudio[13463]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:47 joe pulseaudio[13462]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:50 joe pulseaudio[13611]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:53 joe acpid: client 11980[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 11985[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12012[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12048[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12006[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12019[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12016[0:0] has disconnected
Feb  1 20:57:53 joe pulseaudio[13654]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:53 joe acpid: client 12021[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12018[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12047[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12054[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12050[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12051[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12052[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 11986[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12044[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12330[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12322[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12336[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12331[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12352[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12329[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12345[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12356[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12355[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12347[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12342[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12332[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12353[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12341[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12394[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12327[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12396[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12393[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12351[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12411[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12413[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12340[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12388[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12412[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12337[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12389[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12410[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12378[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12334[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12338[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12380[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12381[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12382[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12344[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12386[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12383[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12354[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12385[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client 12379[0:0] has disconnected
Feb  1 20:57:53 joe acpid: client connected from 13643[0:0]
Feb  1 20:57:53 joe acpid: 1 client rule loaded
Feb  1 20:57:55 joe pulseaudio[13841]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:59 joe acpid: client 13643[0:0] has disconnected
Feb  1 20:57:59 joe acpid: client connected from 13905[0:0]
Feb  1 20:57:59 joe acpid: 1 client rule loaded
Feb  1 20:57:59 joe acpid: client connected from 13910[0:0]
Feb  1 20:57:59 joe acpid: 1 client rule loaded
Feb  1 20:57:59 joe acpid: client connected from 13908[0:0]
Feb  1 20:57:59 joe acpid: 1 client rule loaded
Feb  1 20:57:59 joe acpid: client 13905[0:0] has disconnected
Feb  1 20:57:59 joe pulseaudio[13945]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:57:59 joe acpid: client 13910[0:0] has disconnected
Feb  1 20:57:59 joe acpid: client 13908[0:0] has disconnected
Feb  1 20:57:59 joe acpid: client connected from 13911[0:0]
Feb  1 20:57:59 joe acpid: 1 client rule loaded
Feb  1 20:57:59 joe acpid: client 13911[0:0] has disconnected
Feb  1 20:57:59 joe acpid: client connected from 13909[0:0]
Feb  1 20:57:59 joe acpid: 1 client rule loaded
Feb  1 20:57:59 joe acpid: client 13909[0:0] has disconnected
Feb  1 20:57:59 joe acpid: client connected from 13912[0:0]
Feb  1 20:57:59 joe acpid: 1 client rule loaded
Feb  1 20:58:00 joe pulseaudio[14076]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:03 joe pulseaudio[14189]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:04 joe acpid: client 13912[0:0] has disconnected
Feb  1 20:58:04 joe acpid: client connected from 14204[0:0]
Feb  1 20:58:04 joe acpid: 1 client rule loaded
Feb  1 20:58:04 joe acpid: client connected from 14201[0:0]
Feb  1 20:58:04 joe acpid: 1 client rule loaded
Feb  1 20:58:04 joe acpid: client connected from 14205[0:0]
Feb  1 20:58:04 joe acpid: 1 client rule loaded
Feb  1 20:58:04 joe acpid: client connected from 14206[0:0]
Feb  1 20:58:04 joe acpid: 1 client rule loaded
Feb  1 20:58:04 joe acpid: client connected from 14210[0:0]
Feb  1 20:58:04 joe acpid: 1 client rule loaded
Feb  1 20:58:04 joe acpid: client connected from 14209[0:0]
Feb  1 20:58:04 joe acpid: 1 client rule loaded
Feb  1 20:58:04 joe acpid: client connected from 14203[0:0]
Feb  1 20:58:04 joe acpid: 1 client rule loaded
Feb  1 20:58:05 joe pulseaudio[14275]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:09 joe pulseaudio[14423]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:10 joe pulseaudio[14483]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:12 joe acpid: client 14204[0:0] has disconnected
Feb  1 20:58:12 joe acpid: client 14201[0:0] has disconnected
Feb  1 20:58:12 joe acpid: client 14205[0:0] has disconnected
Feb  1 20:58:12 joe acpid: client 14206[0:0] has disconnected
Feb  1 20:58:12 joe acpid: client 14210[0:0] has disconnected
Feb  1 20:58:12 joe acpid: client 14209[0:0] has disconnected
Feb  1 20:58:12 joe acpid: client 14203[0:0] has disconnected
Feb  1 20:58:12 joe acpid: client connected from 14517[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:12 joe acpid: client connected from 14519[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:12 joe acpid: client connected from 14518[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:12 joe acpid: client connected from 14524[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:12 joe acpid: client connected from 14525[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:12 joe acpid: client connected from 14526[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:12 joe acpid: client connected from 14537[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:12 joe acpid: client connected from 14527[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:12 joe acpid: client connected from 14523[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:12 joe acpid: client connected from 14532[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:12 joe acpid: client connected from 14535[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:12 joe acpid: client connected from 14530[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:12 joe acpid: client connected from 14529[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:12 joe acpid: client connected from 14536[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:12 joe acpid: client connected from 14534[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:12 joe acpid: client connected from 14531[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:12 joe acpid: client connected from 14533[0:0]
Feb  1 20:58:12 joe acpid: 1 client rule loaded
Feb  1 20:58:15 joe pulseaudio[14633]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:16 joe pulseaudio[14721]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:18 joe acpid: client 14517[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client 14519[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client 14518[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client 14524[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client 14525[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client 14526[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client 14537[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client 14527[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client 14523[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client 14532[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client 14535[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client 14530[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client 14529[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client 14536[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client 14534[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client 14531[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client 14533[0:0] has disconnected
Feb  1 20:58:18 joe acpid: client connected from 14838[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14848[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14844[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14840[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14857[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14855[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14845[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14862[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14850[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14856[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14858[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14854[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14852[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14861[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14843[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14849[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14842[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14847[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14841[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14839[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14884[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14853[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14860[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14883[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:18 joe acpid: client connected from 14882[0:0]
Feb  1 20:58:18 joe acpid: 1 client rule loaded
Feb  1 20:58:23 joe pulseaudio[14940]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:23 joe pulseaudio[14984]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:24 joe acpid: client 14838[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14848[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14844[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14840[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14857[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14855[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14845[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14862[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14850[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14856[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14858[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14854[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14852[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14861[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14843[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14849[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14842[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14847[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14841[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14839[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14884[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14853[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14860[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14883[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client 14882[0:0] has disconnected
Feb  1 20:58:24 joe acpid: client connected from 15169[0:0]
Feb  1 20:58:24 joe acpid: 1 client rule loaded
Feb  1 20:58:24 joe acpid: client connected from 15171[0:0]
Feb  1 20:58:24 joe acpid: 1 client rule loaded
Feb  1 20:58:24 joe acpid: client connected from 15181[0:0]
Feb  1 20:58:24 joe acpid: 1 client rule loaded
Feb  1 20:58:24 joe acpid: client connected from 15170[0:0]
Feb  1 20:58:24 joe acpid: 1 client rule loaded
Feb  1 20:58:24 joe acpid: client connected from 15172[0:0]
Feb  1 20:58:24 joe acpid: 1 client rule loaded
Feb  1 20:58:25 joe pulseaudio[15232]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:25 joe pulseaudio[15233]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:30 joe pulseaudio[15467]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:30 joe pulseaudio[15468]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:30 joe acpid: client 15169[0:0] has disconnected
Feb  1 20:58:30 joe acpid: client 15171[0:0] has disconnected
Feb  1 20:58:30 joe acpid: client 15181[0:0] has disconnected
Feb  1 20:58:30 joe acpid: client 15170[0:0] has disconnected
Feb  1 20:58:30 joe acpid: client 15172[0:0] has disconnected
Feb  1 20:58:30 joe acpid: client connected from 15470[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15484[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15475[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15469[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15472[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15473[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15489[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15478[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15480[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15481[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15487[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15476[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15488[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15491[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15485[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15490[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15495[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15483[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15492[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15494[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15477[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15515[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15496[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15486[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15514[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:30 joe acpid: client connected from 15516[0:0]
Feb  1 20:58:30 joe acpid: 1 client rule loaded
Feb  1 20:58:31 joe acpid: client 15470[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15484[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15469[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15472[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15473[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15489[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15480[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15487[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15476[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15488[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15491[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15490[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15495[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15492[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15494[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15477[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15496[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15486[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client connected from 15523[0:0]
Feb  1 20:58:31 joe acpid: 1 client rule loaded
Feb  1 20:58:31 joe acpid: client 15514[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client connected from 15525[0:0]
Feb  1 20:58:31 joe acpid: 1 client rule loaded
Feb  1 20:58:31 joe acpid: client 15515[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client 15516[0:0] has disconnected
Feb  1 20:58:31 joe acpid: client connected from 15524[0:0]
Feb  1 20:58:31 joe acpid: 1 client rule loaded
Feb  1 20:58:31 joe acpid: client connected from 15526[0:0]
Feb  1 20:58:31 joe acpid: 1 client rule loaded
Feb  1 20:58:35 joe pulseaudio[15740]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:35 joe pulseaudio[15739]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:41 joe acpid: client 15475[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client 15478[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client 15481[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client 15485[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client 15483[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client 15523[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client 15525[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client 15524[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client 15526[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client connected from 15855[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe pulseaudio[16025]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:41 joe pulseaudio[16024]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:41 joe acpid: client 15855[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client connected from 15860[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client 15860[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client connected from 15859[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client 15859[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client connected from 15857[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client 15857[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client connected from 15863[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client 15863[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client connected from 15862[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client 15862[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client connected from 15864[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client 15864[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client connected from 15877[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client 15877[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client connected from 15871[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client 15871[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client connected from 15875[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client 15875[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client connected from 15872[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client 15872[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client connected from 15861[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client 15861[0:0] has disconnected
Feb  1 20:58:41 joe acpid: client connected from 15858[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15907[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15874[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15867[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15878[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15904[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15908[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15932[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15935[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15903[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15869[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15940[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15902[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15928[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15937[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15930[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15929[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15876[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15905[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15873[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15865[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15912[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15899[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15901[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15898[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15910[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15936[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15906[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15900[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15934[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15927[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15911[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15933[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15939[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15938[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15896[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15870[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:41 joe acpid: client connected from 15931[0:0]
Feb  1 20:58:41 joe acpid: 1 client rule loaded
Feb  1 20:58:48 joe pulseaudio[16278]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:48 joe pulseaudio[16276]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:54 joe pulseaudio[16508]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:54 joe pulseaudio[16510]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:54 joe acpid: client 15858[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15907[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15874[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15867[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15878[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15904[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15908[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15932[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15935[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15903[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15869[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15940[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15902[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15928[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15937[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15930[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15929[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15876[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15905[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15873[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15865[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15912[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15899[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15901[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15898[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15910[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15936[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15906[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15900[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15934[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15927[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15911[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15933[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15939[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15938[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15896[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15870[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client 15931[0:0] has disconnected
Feb  1 20:58:54 joe acpid: client connected from 16514[0:0]
Feb  1 20:58:54 joe acpid: 1 client rule loaded
Feb  1 20:58:58 joe pulseaudio[16737]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:58:58 joe pulseaudio[16739]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:00 joe acpid: client 16514[0:0] has disconnected
Feb  1 20:59:00 joe acpid: client connected from 16836[0:0]
Feb  1 20:59:00 joe acpid: 1 client rule loaded
Feb  1 20:59:00 joe acpid: client connected from 16841[0:0]
Feb  1 20:59:00 joe acpid: 1 client rule loaded
Feb  1 20:59:00 joe acpid: client connected from 16842[0:0]
Feb  1 20:59:00 joe acpid: 1 client rule loaded
Feb  1 20:59:00 joe acpid: client connected from 16840[0:0]
Feb  1 20:59:00 joe acpid: 1 client rule loaded
Feb  1 20:59:00 joe acpid: client connected from 16837[0:0]
Feb  1 20:59:00 joe acpid: 1 client rule loaded
Feb  1 20:59:00 joe acpid: client connected from 16839[0:0]
Feb  1 20:59:00 joe acpid: 1 client rule loaded
Feb  1 20:59:05 joe pulseaudio[16944]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:05 joe pulseaudio[16947]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:10 joe acpid: client 16836[0:0] has disconnected
Feb  1 20:59:10 joe acpid: client 16841[0:0] has disconnected
Feb  1 20:59:10 joe acpid: client 16842[0:0] has disconnected
Feb  1 20:59:10 joe acpid: client 16840[0:0] has disconnected
Feb  1 20:59:10 joe acpid: client 16837[0:0] has disconnected
Feb  1 20:59:10 joe acpid: client 16839[0:0] has disconnected
Feb  1 20:59:10 joe acpid: client connected from 17161[0:0]
Feb  1 20:59:10 joe acpid: 1 client rule loaded
Feb  1 20:59:10 joe pulseaudio[17156]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:10 joe pulseaudio[17155]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:10 joe acpid: client 17161[0:0] has disconnected
Feb  1 20:59:10 joe acpid: client connected from 17157[0:0]
Feb  1 20:59:10 joe acpid: 1 client rule loaded
Feb  1 20:59:10 joe acpid: client 17157[0:0] has disconnected
Feb  1 20:59:10 joe acpid: client connected from 17162[0:0]
Feb  1 20:59:10 joe acpid: 1 client rule loaded
Feb  1 20:59:10 joe acpid: client 17162[0:0] has disconnected
Feb  1 20:59:10 joe acpid: client connected from 17164[0:0]
Feb  1 20:59:10 joe acpid: 1 client rule loaded
Feb  1 20:59:11 joe acpid: client 17164[0:0] has disconnected
Feb  1 20:59:11 joe acpid: client connected from 17159[0:0]
Feb  1 20:59:11 joe acpid: 1 client rule loaded
Feb  1 20:59:11 joe acpid: client 17159[0:0] has disconnected
Feb  1 20:59:11 joe acpid: client connected from 17163[0:0]
Feb  1 20:59:11 joe acpid: 1 client rule loaded
Feb  1 20:59:11 joe acpid: client 17163[0:0] has disconnected
Feb  1 20:59:11 joe acpid: client connected from 17158[0:0]
Feb  1 20:59:11 joe acpid: 1 client rule loaded
Feb  1 20:59:14 joe pulseaudio[17414]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:14 joe pulseaudio[17415]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:17 joe acpid: client 17158[0:0] has disconnected
Feb  1 20:59:17 joe acpid: client connected from 17573[0:0]
Feb  1 20:59:17 joe acpid: 1 client rule loaded
Feb  1 20:59:17 joe acpid: client connected from 17570[0:0]
Feb  1 20:59:17 joe acpid: 1 client rule loaded
Feb  1 20:59:17 joe acpid: client connected from 17572[0:0]
Feb  1 20:59:17 joe acpid: 1 client rule loaded
Feb  1 20:59:17 joe acpid: client connected from 17571[0:0]
Feb  1 20:59:17 joe acpid: 1 client rule loaded
Feb  1 20:59:17 joe acpid: client connected from 17574[0:0]
Feb  1 20:59:17 joe acpid: 1 client rule loaded
Feb  1 20:59:17 joe acpid: client connected from 17582[0:0]
Feb  1 20:59:17 joe acpid: 1 client rule loaded
Feb  1 20:59:17 joe acpid: client connected from 17580[0:0]
Feb  1 20:59:17 joe acpid: 1 client rule loaded
Feb  1 20:59:17 joe acpid: client connected from 17581[0:0]
Feb  1 20:59:17 joe acpid: 1 client rule loaded
Feb  1 20:59:17 joe acpid: client connected from 17583[0:0]
Feb  1 20:59:17 joe acpid: 1 client rule loaded
Feb  1 20:59:18 joe acpid: client 17570[0:0] has disconnected
Feb  1 20:59:18 joe acpid: client connected from 17588[0:0]
Feb  1 20:59:18 joe acpid: 1 client rule loaded
Feb  1 20:59:18 joe acpid: client connected from 17589[0:0]
Feb  1 20:59:18 joe acpid: 1 client rule loaded
Feb  1 20:59:18 joe acpid: client 17574[0:0] has disconnected
Feb  1 20:59:18 joe acpid: client connected from 17596[0:0]
Feb  1 20:59:18 joe acpid: 1 client rule loaded
Feb  1 20:59:18 joe acpid: client connected from 17594[0:0]
Feb  1 20:59:18 joe acpid: 1 client rule loaded
Feb  1 20:59:18 joe acpid: client 17572[0:0] has disconnected
Feb  1 20:59:18 joe acpid: client connected from 17593[0:0]
Feb  1 20:59:18 joe acpid: 1 client rule loaded
Feb  1 20:59:18 joe acpid: client connected from 17595[0:0]
Feb  1 20:59:18 joe acpid: 1 client rule loaded
Feb  1 20:59:18 joe acpid: client connected from 17592[0:0]
Feb  1 20:59:18 joe acpid: 1 client rule loaded
Feb  1 20:59:18 joe acpid: client 17573[0:0] has disconnected
Feb  1 20:59:18 joe acpid: client connected from 17597[0:0]
Feb  1 20:59:18 joe acpid: 1 client rule loaded
Feb  1 20:59:18 joe acpid: client 17571[0:0] has disconnected
Feb  1 20:59:18 joe acpid: client 17582[0:0] has disconnected
Feb  1 20:59:18 joe acpid: client 17580[0:0] has disconnected
Feb  1 20:59:18 joe acpid: client 17581[0:0] has disconnected
Feb  1 20:59:18 joe acpid: client 17583[0:0] has disconnected
Feb  1 20:59:18 joe acpid: client connected from 17607[0:0]
Feb  1 20:59:18 joe acpid: 1 client rule loaded
Feb  1 20:59:18 joe acpid: client connected from 17608[0:0]
Feb  1 20:59:18 joe acpid: 1 client rule loaded
Feb  1 20:59:19 joe pulseaudio[17687]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:19 joe pulseaudio[17688]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:24 joe pulseaudio[17910]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:24 joe pulseaudio[17912]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:26 joe acpid: client 17588[0:0] has disconnected
Feb  1 20:59:26 joe acpid: client 17589[0:0] has disconnected
Feb  1 20:59:26 joe acpid: client 17596[0:0] has disconnected
Feb  1 20:59:26 joe acpid: client 17594[0:0] has disconnected
Feb  1 20:59:26 joe acpid: client 17593[0:0] has disconnected
Feb  1 20:59:26 joe acpid: client 17595[0:0] has disconnected
Feb  1 20:59:26 joe acpid: client 17592[0:0] has disconnected
Feb  1 20:59:26 joe acpid: client 17597[0:0] has disconnected
Feb  1 20:59:26 joe acpid: client 17607[0:0] has disconnected
Feb  1 20:59:26 joe acpid: client 17608[0:0] has disconnected
Feb  1 20:59:26 joe acpid: client connected from 17977[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 17986[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 17984[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 17982[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 17983[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 17981[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 17979[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 17985[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 17994[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 18004[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 17996[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 17997[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 18000[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 17998[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 18009[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 17999[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 18010[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 17995[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client connected from 18002[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client 17977[0:0] has disconnected
Feb  1 20:59:26 joe acpid: client 17982[0:0] has disconnected
Feb  1 20:59:26 joe acpid: client 17983[0:0] has disconnected
Feb  1 20:59:26 joe acpid: client 17979[0:0] has disconnected
Feb  1 20:59:26 joe acpid: client connected from 18026[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:26 joe acpid: client 17986[0:0] has disconnected
Feb  1 20:59:26 joe acpid: client 17984[0:0] has disconnected
Feb  1 20:59:26 joe acpid: client connected from 18024[0:0]
Feb  1 20:59:26 joe acpid: 1 client rule loaded
Feb  1 20:59:31 joe pulseaudio[18155]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:31 joe pulseaudio[18154]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:37 joe acpid: client 17981[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client 17985[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client 17994[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client 18004[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client 17996[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client 17997[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client 18000[0:0] has disconnected
Feb  1 20:59:37 joe pulseaudio[18435]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:37 joe pulseaudio[18477]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:37 joe acpid: client 17998[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client 18009[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client 17999[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client 18010[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client 17995[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client 18002[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client 18026[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client 18024[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client connected from 18411[0:0]
Feb  1 20:59:37 joe acpid: 1 client rule loaded
Feb  1 20:59:37 joe acpid: client 18411[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client connected from 18409[0:0]
Feb  1 20:59:37 joe acpid: 1 client rule loaded
Feb  1 20:59:37 joe acpid: client 18409[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client connected from 18417[0:0]
Feb  1 20:59:37 joe acpid: 1 client rule loaded
Feb  1 20:59:37 joe acpid: client 18417[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client connected from 18416[0:0]
Feb  1 20:59:37 joe acpid: 1 client rule loaded
Feb  1 20:59:37 joe acpid: client 18416[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client connected from 18421[0:0]
Feb  1 20:59:37 joe acpid: 1 client rule loaded
Feb  1 20:59:37 joe acpid: client 18421[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client connected from 18414[0:0]
Feb  1 20:59:37 joe acpid: 1 client rule loaded
Feb  1 20:59:37 joe acpid: client 18414[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client connected from 18423[0:0]
Feb  1 20:59:37 joe acpid: 1 client rule loaded
Feb  1 20:59:37 joe acpid: client 18423[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client connected from 18412[0:0]
Feb  1 20:59:37 joe acpid: 1 client rule loaded
Feb  1 20:59:37 joe acpid: client 18412[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client connected from 18410[0:0]
Feb  1 20:59:37 joe acpid: 1 client rule loaded
Feb  1 20:59:37 joe acpid: client 18410[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client connected from 18420[0:0]
Feb  1 20:59:37 joe acpid: 1 client rule loaded
Feb  1 20:59:37 joe acpid: client 18420[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client connected from 18422[0:0]
Feb  1 20:59:37 joe acpid: 1 client rule loaded
Feb  1 20:59:37 joe acpid: client 18422[0:0] has disconnected
Feb  1 20:59:37 joe acpid: client connected from 18413[0:0]
Feb  1 20:59:37 joe acpid: 1 client rule loaded
Feb  1 20:59:41 joe pulseaudio[18711]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:42 joe pulseaudio[18742]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:46 joe acpid: client 18413[0:0] has disconnected
Feb  1 20:59:46 joe acpid: client connected from 18877[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client connected from 18876[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client connected from 18878[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client connected from 18890[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client connected from 18891[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client connected from 18883[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client 18878[0:0] has disconnected
Feb  1 20:59:46 joe acpid: client connected from 18893[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client 18876[0:0] has disconnected
Feb  1 20:59:46 joe acpid: client connected from 18892[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client 18877[0:0] has disconnected
Feb  1 20:59:46 joe acpid: client connected from 18907[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client connected from 18908[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client connected from 18910[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client connected from 18913[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client connected from 18915[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client connected from 18914[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client connected from 18912[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client connected from 18909[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client connected from 18911[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client connected from 18905[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe acpid: client connected from 18906[0:0]
Feb  1 20:59:46 joe acpid: 1 client rule loaded
Feb  1 20:59:46 joe pulseaudio[18940]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:47 joe pulseaudio[18991]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:52 joe pulseaudio[19193]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:52 joe pulseaudio[19246]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:54 joe acpid: client 18890[0:0] has disconnected
Feb  1 20:59:54 joe acpid: client 18891[0:0] has disconnected
Feb  1 20:59:54 joe acpid: client 18883[0:0] has disconnected
Feb  1 20:59:54 joe acpid: client 18893[0:0] has disconnected
Feb  1 20:59:54 joe acpid: client 18892[0:0] has disconnected
Feb  1 20:59:54 joe acpid: client 18907[0:0] has disconnected
Feb  1 20:59:54 joe acpid: client 18908[0:0] has disconnected
Feb  1 20:59:54 joe acpid: client 18910[0:0] has disconnected
Feb  1 20:59:54 joe acpid: client 18913[0:0] has disconnected
Feb  1 20:59:54 joe acpid: client 18915[0:0] has disconnected
Feb  1 20:59:54 joe acpid: client 18914[0:0] has disconnected
Feb  1 20:59:54 joe acpid: client 18912[0:0] has disconnected
Feb  1 20:59:54 joe acpid: client 18909[0:0] has disconnected
Feb  1 20:59:54 joe acpid: client 18911[0:0] has disconnected
Feb  1 20:59:54 joe acpid: client 18905[0:0] has disconnected
Feb  1 20:59:54 joe acpid: client 18906[0:0] has disconnected
Feb  1 20:59:54 joe acpid: client connected from 19348[0:0]
Feb  1 20:59:54 joe acpid: 1 client rule loaded
Feb  1 20:59:54 joe acpid: client connected from 19350[0:0]
Feb  1 20:59:54 joe acpid: 1 client rule loaded
Feb  1 20:59:54 joe acpid: client connected from 19347[0:0]
Feb  1 20:59:54 joe acpid: 1 client rule loaded
Feb  1 20:59:54 joe acpid: client connected from 19349[0:0]
Feb  1 20:59:54 joe acpid: 1 client rule loaded
Feb  1 20:59:57 joe pulseaudio[19409]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 20:59:57 joe pulseaudio[19438]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:02 joe pulseaudio[19564]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:02 joe pulseaudio[19616]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:09 joe pulseaudio[19830]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:09 joe acpid: client 19348[0:0] has disconnected
Feb  1 21:00:09 joe acpid: client 19350[0:0] has disconnected
Feb  1 21:00:09 joe acpid: client 19347[0:0] has disconnected
Feb  1 21:00:09 joe acpid: client 19349[0:0] has disconnected
Feb  1 21:00:09 joe acpid: client connected from 19842[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client connected from 19846[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client 19842[0:0] has disconnected
Feb  1 21:00:09 joe pulseaudio[19950]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:09 joe acpid: client 19846[0:0] has disconnected
Feb  1 21:00:09 joe acpid: client connected from 19849[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client 19849[0:0] has disconnected
Feb  1 21:00:09 joe acpid: client connected from 19845[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client 19845[0:0] has disconnected
Feb  1 21:00:09 joe acpid: client connected from 19853[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client 19853[0:0] has disconnected
Feb  1 21:00:09 joe acpid: client connected from 19847[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client 19847[0:0] has disconnected
Feb  1 21:00:09 joe acpid: client connected from 19858[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client 19858[0:0] has disconnected
Feb  1 21:00:09 joe acpid: client connected from 19863[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client 19863[0:0] has disconnected
Feb  1 21:00:09 joe acpid: client connected from 19862[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client 19862[0:0] has disconnected
Feb  1 21:00:09 joe acpid: client connected from 19865[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client 19865[0:0] has disconnected
Feb  1 21:00:09 joe acpid: client connected from 19866[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client 19866[0:0] has disconnected
Feb  1 21:00:09 joe acpid: client connected from 19854[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client 19854[0:0] has disconnected
Feb  1 21:00:09 joe acpid: client connected from 19861[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client 19861[0:0] has disconnected
Feb  1 21:00:09 joe acpid: client connected from 19867[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client connected from 19860[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client connected from 19864[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client connected from 19844[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client connected from 19859[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client connected from 19919[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client connected from 19925[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client connected from 19923[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client connected from 19924[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client connected from 19930[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client connected from 19927[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client connected from 19929[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:09 joe acpid: client connected from 19921[0:0]
Feb  1 21:00:09 joe acpid: 1 client rule loaded
Feb  1 21:00:14 joe pulseaudio[20141]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:14 joe pulseaudio[20289]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:16 joe acpid: client 19867[0:0] has disconnected
Feb  1 21:00:16 joe acpid: client 19860[0:0] has disconnected
Feb  1 21:00:16 joe acpid: client 19864[0:0] has disconnected
Feb  1 21:00:16 joe acpid: client 19844[0:0] has disconnected
Feb  1 21:00:16 joe acpid: client 19859[0:0] has disconnected
Feb  1 21:00:16 joe acpid: client 19919[0:0] has disconnected
Feb  1 21:00:16 joe acpid: client 19925[0:0] has disconnected
Feb  1 21:00:16 joe acpid: client 19923[0:0] has disconnected
Feb  1 21:00:16 joe acpid: client 19924[0:0] has disconnected
Feb  1 21:00:16 joe acpid: client 19930[0:0] has disconnected
Feb  1 21:00:16 joe acpid: client 19927[0:0] has disconnected
Feb  1 21:00:16 joe acpid: client 19929[0:0] has disconnected
Feb  1 21:00:16 joe acpid: client 19921[0:0] has disconnected
Feb  1 21:00:16 joe acpid: client connected from 20354[0:0]
Feb  1 21:00:16 joe acpid: 1 client rule loaded
Feb  1 21:00:19 joe pulseaudio[20441]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:19 joe pulseaudio[20520]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:24 joe pulseaudio[20618]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:24 joe pulseaudio[20718]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:29 joe pulseaudio[20824]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:29 joe acpid: client 20354[0:0] has disconnected
Feb  1 21:00:29 joe acpid: client connected from 20857[0:0]
Feb  1 21:00:29 joe acpid: 1 client rule loaded
Feb  1 21:00:29 joe acpid: client connected from 20859[0:0]
Feb  1 21:00:29 joe acpid: 1 client rule loaded
Feb  1 21:00:29 joe acpid: client connected from 20856[0:0]
Feb  1 21:00:29 joe acpid: 1 client rule loaded
Feb  1 21:00:29 joe acpid: client connected from 20862[0:0]
Feb  1 21:00:29 joe acpid: 1 client rule loaded
Feb  1 21:00:29 joe acpid: client 20857[0:0] has disconnected
Feb  1 21:00:29 joe acpid: client 20859[0:0] has disconnected
Feb  1 21:00:29 joe acpid: client 20856[0:0] has disconnected
Feb  1 21:00:29 joe acpid: client 20862[0:0] has disconnected
Feb  1 21:00:29 joe acpid: client connected from 20861[0:0]
Feb  1 21:00:29 joe acpid: 1 client rule loaded
Feb  1 21:00:29 joe acpid: client 20861[0:0] has disconnected
Feb  1 21:00:29 joe acpid: client connected from 20858[0:0]
Feb  1 21:00:29 joe acpid: 1 client rule loaded
Feb  1 21:00:29 joe pulseaudio[20920]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:34 joe pulseaudio[21087]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:35 joe pulseaudio[21184]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:40 joe acpid: client 20858[0:0] has disconnected
Feb  1 21:00:40 joe acpid: client connected from 21354[0:0]
Feb  1 21:00:40 joe acpid: 1 client rule loaded
Feb  1 21:00:40 joe acpid: client connected from 21359[0:0]
Feb  1 21:00:40 joe acpid: 1 client rule loaded
Feb  1 21:00:40 joe acpid: client connected from 21357[0:0]
Feb  1 21:00:40 joe acpid: 1 client rule loaded
Feb  1 21:00:40 joe acpid: client connected from 21360[0:0]
Feb  1 21:00:40 joe pulseaudio[21388]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:40 joe acpid: 1 client rule loaded
Feb  1 21:00:40 joe acpid: client 21354[0:0] has disconnected
Feb  1 21:00:40 joe acpid: client 21359[0:0] has disconnected
Feb  1 21:00:40 joe acpid: client 21357[0:0] has disconnected
Feb  1 21:00:40 joe acpid: client 21360[0:0] has disconnected
Feb  1 21:00:40 joe acpid: client connected from 21361[0:0]
Feb  1 21:00:40 joe acpid: 1 client rule loaded
Feb  1 21:00:40 joe pulseaudio[21438]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:40 joe acpid: client 21361[0:0] has disconnected
Feb  1 21:00:40 joe acpid: client connected from 21358[0:0]
Feb  1 21:00:40 joe acpid: 1 client rule loaded
Feb  1 21:00:44 joe pulseaudio[21654]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:47 joe pulseaudio[21709]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:48 joe acpid: client 21358[0:0] has disconnected
Feb  1 21:00:48 joe acpid: client connected from 21829[0:0]
Feb  1 21:00:48 joe acpid: 1 client rule loaded
Feb  1 21:00:48 joe acpid: client 21829[0:0] has disconnected
Feb  1 21:00:48 joe acpid: client connected from 21833[0:0]
Feb  1 21:00:48 joe acpid: 1 client rule loaded
Feb  1 21:00:48 joe acpid: client connected from 21832[0:0]
Feb  1 21:00:48 joe acpid: 1 client rule loaded
Feb  1 21:00:48 joe acpid: client connected from 21834[0:0]
Feb  1 21:00:48 joe acpid: 1 client rule loaded
Feb  1 21:00:49 joe pulseaudio[21906]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:50 joe pulseaudio[21963]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:54 joe pulseaudio[22171]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:55 joe pulseaudio[22221]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:00:59 joe acpid: client 21833[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client 21832[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client 21834[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client connected from 22331[0:0]
Feb  1 21:00:59 joe acpid: 1 client rule loaded
Feb  1 21:00:59 joe acpid: client connected from 22338[0:0]
Feb  1 21:00:59 joe acpid: 1 client rule loaded
Feb  1 21:00:59 joe acpid: client connected from 22347[0:0]
Feb  1 21:00:59 joe acpid: 1 client rule loaded
Feb  1 21:00:59 joe acpid: client connected from 22350[0:0]
Feb  1 21:00:59 joe acpid: 1 client rule loaded
Feb  1 21:00:59 joe acpid: client 22331[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client 22338[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client 22347[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client 22350[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client connected from 22333[0:0]
Feb  1 21:00:59 joe acpid: 1 client rule loaded
Feb  1 21:00:59 joe acpid: client 22333[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client connected from 22348[0:0]
Feb  1 21:00:59 joe acpid: 1 client rule loaded
Feb  1 21:00:59 joe acpid: client 22348[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client connected from 22352[0:0]
Feb  1 21:00:59 joe acpid: 1 client rule loaded
Feb  1 21:00:59 joe acpid: client 22352[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client connected from 22337[0:0]
Feb  1 21:00:59 joe acpid: 1 client rule loaded
Feb  1 21:00:59 joe acpid: client 22337[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client connected from 22354[0:0]
Feb  1 21:00:59 joe acpid: 1 client rule loaded
Feb  1 21:00:59 joe acpid: client 22354[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client connected from 22332[0:0]
Feb  1 21:00:59 joe acpid: 1 client rule loaded
Feb  1 21:00:59 joe acpid: client 22332[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client connected from 22357[0:0]
Feb  1 21:00:59 joe acpid: 1 client rule loaded
Feb  1 21:00:59 joe acpid: client 22357[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client connected from 22346[0:0]
Feb  1 21:00:59 joe acpid: 1 client rule loaded
Feb  1 21:00:59 joe acpid: client 22346[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client connected from 22356[0:0]
Feb  1 21:00:59 joe acpid: 1 client rule loaded
Feb  1 21:00:59 joe acpid: client 22356[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client connected from 22339[0:0]
Feb  1 21:00:59 joe acpid: 1 client rule loaded
Feb  1 21:00:59 joe acpid: client 22339[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client connected from 22335[0:0]
Feb  1 21:00:59 joe acpid: 1 client rule loaded
Feb  1 21:00:59 joe acpid: client 22335[0:0] has disconnected
Feb  1 21:00:59 joe acpid: client connected from 22353[0:0]
Feb  1 21:00:59 joe acpid: 1 client rule loaded
Feb  1 21:00:59 joe pulseaudio[22440]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:00 joe pulseaudio[22490]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:04 joe pulseaudio[22666]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:05 joe pulseaudio[22717]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:09 joe acpid: client 22353[0:0] has disconnected
Feb  1 21:01:09 joe acpid: client connected from 22864[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client connected from 22866[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client connected from 22868[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client connected from 22872[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client connected from 22875[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client 22864[0:0] has disconnected
Feb  1 21:01:09 joe acpid: client 22866[0:0] has disconnected
Feb  1 21:01:09 joe acpid: client 22868[0:0] has disconnected
Feb  1 21:01:09 joe acpid: client 22872[0:0] has disconnected
Feb  1 21:01:09 joe acpid: client 22875[0:0] has disconnected
Feb  1 21:01:09 joe acpid: client connected from 22882[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client 22882[0:0] has disconnected
Feb  1 21:01:09 joe acpid: client connected from 22876[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client 22876[0:0] has disconnected
Feb  1 21:01:09 joe pulseaudio[22973]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:09 joe acpid: client connected from 22879[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client 22879[0:0] has disconnected
Feb  1 21:01:09 joe acpid: client connected from 22874[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client 22874[0:0] has disconnected
Feb  1 21:01:09 joe acpid: client connected from 22889[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client 22889[0:0] has disconnected
Feb  1 21:01:09 joe acpid: client connected from 22884[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client 22884[0:0] has disconnected
Feb  1 21:01:09 joe acpid: client connected from 22865[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client 22865[0:0] has disconnected
Feb  1 21:01:09 joe acpid: client connected from 22881[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client 22881[0:0] has disconnected
Feb  1 21:01:09 joe acpid: client connected from 22885[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client 22885[0:0] has disconnected
Feb  1 21:01:09 joe acpid: client connected from 22890[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client 22890[0:0] has disconnected
Feb  1 21:01:09 joe acpid: client connected from 22869[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client 22869[0:0] has disconnected
Feb  1 21:01:09 joe acpid: client connected from 22873[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client connected from 22886[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client connected from 22880[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client connected from 22893[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client connected from 22877[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client connected from 22892[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:09 joe acpid: client connected from 22883[0:0]
Feb  1 21:01:09 joe acpid: 1 client rule loaded
Feb  1 21:01:10 joe pulseaudio[23039]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:15 joe pulseaudio[23300]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:15 joe pulseaudio[23338]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:20 joe pulseaudio[23529]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:20 joe acpid: client 22873[0:0] has disconnected
Feb  1 21:01:20 joe acpid: client 22886[0:0] has disconnected
Feb  1 21:01:20 joe acpid: client 22880[0:0] has disconnected
Feb  1 21:01:20 joe acpid: client 22893[0:0] has disconnected
Feb  1 21:01:20 joe acpid: client 22877[0:0] has disconnected
Feb  1 21:01:20 joe acpid: client 22892[0:0] has disconnected
Feb  1 21:01:20 joe acpid: client 22883[0:0] has disconnected
Feb  1 21:01:20 joe acpid: client connected from 23557[0:0]
Feb  1 21:01:20 joe acpid: 1 client rule loaded
Feb  1 21:01:20 joe acpid: client connected from 23558[0:0]
Feb  1 21:01:20 joe acpid: 1 client rule loaded
Feb  1 21:01:20 joe acpid: client connected from 23554[0:0]
Feb  1 21:01:20 joe acpid: 1 client rule loaded
Feb  1 21:01:20 joe acpid: client connected from 23555[0:0]
Feb  1 21:01:20 joe acpid: 1 client rule loaded
Feb  1 21:01:20 joe acpid: client connected from 23556[0:0]
Feb  1 21:01:20 joe acpid: 1 client rule loaded
Feb  1 21:01:20 joe acpid: client connected from 23551[0:0]
Feb  1 21:01:20 joe acpid: 1 client rule loaded
Feb  1 21:01:20 joe acpid: client connected from 23549[0:0]
Feb  1 21:01:20 joe acpid: 1 client rule loaded
Feb  1 21:01:20 joe acpid: client connected from 23560[0:0]
Feb  1 21:01:20 joe acpid: 1 client rule loaded
Feb  1 21:01:20 joe acpid: client connected from 23550[0:0]
Feb  1 21:01:20 joe acpid: 1 client rule loaded
Feb  1 21:01:20 joe acpid: client connected from 23559[0:0]
Feb  1 21:01:20 joe acpid: 1 client rule loaded
Feb  1 21:01:20 joe acpid: client connected from 23553[0:0]
Feb  1 21:01:20 joe acpid: 1 client rule loaded
Feb  1 21:01:20 joe acpid: client connected from 23552[0:0]
Feb  1 21:01:20 joe acpid: 1 client rule loaded
Feb  1 21:01:20 joe pulseaudio[23575]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:26 joe pulseaudio[23763]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:26 joe pulseaudio[23810]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:32 joe pulseaudio[24006]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:32 joe acpid: client 23557[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client 23558[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client 23554[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client 23555[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client 23556[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client 23551[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client 23549[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client 23560[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client 23550[0:0] has disconnected
Feb  1 21:01:32 joe pulseaudio[24086]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:32 joe acpid: client 23559[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client 23553[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client 23552[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client connected from 24027[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client 24027[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client connected from 24028[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client 24028[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client connected from 24026[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client 24026[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client connected from 24049[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client 24049[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client connected from 24033[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client 24033[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client connected from 24036[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client 24036[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client connected from 24037[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client 24037[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client connected from 24038[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client 24038[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client connected from 24034[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client 24034[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client connected from 24039[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client 24039[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client connected from 24043[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client 24043[0:0] has disconnected
Feb  1 21:01:32 joe acpid: client connected from 24044[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client connected from 24040[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client connected from 24047[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client connected from 24050[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client connected from 24042[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client connected from 24048[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client connected from 24051[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client connected from 24041[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client connected from 24029[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client connected from 24046[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client connected from 24032[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client connected from 24030[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:32 joe acpid: client connected from 24035[0:0]
Feb  1 21:01:32 joe acpid: 1 client rule loaded
Feb  1 21:01:37 joe pulseaudio[24238]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:37 joe pulseaudio[24291]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:42 joe pulseaudio[24439]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:42 joe acpid: client 24044[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client 24040[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client 24047[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client 24050[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client 24042[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client 24048[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client 24051[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client 24041[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client 24029[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client 24046[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client 24032[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client 24030[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client 24035[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client connected from 24520[0:0]
Feb  1 21:01:42 joe acpid: 1 client rule loaded
Feb  1 21:01:42 joe acpid: client connected from 24519[0:0]
Feb  1 21:01:42 joe acpid: 1 client rule loaded
Feb  1 21:01:42 joe acpid: client connected from 24522[0:0]
Feb  1 21:01:42 joe acpid: 1 client rule loaded
Feb  1 21:01:42 joe acpid: client connected from 24523[0:0]
Feb  1 21:01:42 joe acpid: 1 client rule loaded
Feb  1 21:01:42 joe pulseaudio[24530]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:42 joe acpid: client 24520[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client 24519[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client 24522[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client 24523[0:0] has disconnected
Feb  1 21:01:42 joe acpid: client connected from 24532[0:0]
Feb  1 21:01:42 joe acpid: 1 client rule loaded
Feb  1 21:01:47 joe pulseaudio[24678]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:47 joe pulseaudio[24722]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:50 joe pulseaudio[24798]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:53 joe pulseaudio[24887]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:01:55 joe acpid: client 24532[0:0] has disconnected
Feb  1 21:01:55 joe acpid: client connected from 25012[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25011[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25028[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25021[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25045[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25049[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25024[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25047[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25030[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25035[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25031[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25029[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25025[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25034[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25043[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25044[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25023[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25032[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25018[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25072[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25026[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25019[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25013[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25046[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25077[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25070[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25080[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25075[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25020[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25048[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25036[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25041[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25069[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25095[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25073[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25074[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25097[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25079[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25078[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25100[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25099[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe acpid: client connected from 25098[0:0]
Feb  1 21:01:55 joe acpid: 1 client rule loaded
Feb  1 21:01:55 joe pulseaudio[25101]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:00 joe pulseaudio[25174]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:01 joe pulseaudio[25341]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:03 joe pulseaudio[25434]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:06 joe acpid: client 25012[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25011[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25028[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25021[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25045[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25049[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25024[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25047[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25030[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25035[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25031[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25029[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25025[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25034[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25043[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25044[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25023[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25032[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25018[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25072[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25026[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25019[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25013[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25046[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25077[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25070[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25080[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25075[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25020[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25048[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25036[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25041[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25069[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25095[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25073[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25074[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25097[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25079[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25078[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25100[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25099[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client 25098[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client connected from 25513[0:0]
Feb  1 21:02:06 joe acpid: 1 client rule loaded
Feb  1 21:02:06 joe acpid: client 25513[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client connected from 25514[0:0]
Feb  1 21:02:06 joe acpid: 1 client rule loaded
Feb  1 21:02:06 joe acpid: client 25514[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client connected from 25521[0:0]
Feb  1 21:02:06 joe acpid: 1 client rule loaded
Feb  1 21:02:06 joe acpid: client 25521[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client connected from 25519[0:0]
Feb  1 21:02:06 joe acpid: 1 client rule loaded
Feb  1 21:02:06 joe acpid: client 25519[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client connected from 25522[0:0]
Feb  1 21:02:06 joe acpid: 1 client rule loaded
Feb  1 21:02:06 joe acpid: client 25522[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client connected from 25520[0:0]
Feb  1 21:02:06 joe acpid: 1 client rule loaded
Feb  1 21:02:06 joe acpid: client 25520[0:0] has disconnected
Feb  1 21:02:06 joe acpid: client connected from 25524[0:0]
Feb  1 21:02:06 joe acpid: 1 client rule loaded
Feb  1 21:02:06 joe pulseaudio[25577]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:08 joe pulseaudio[25671]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:11 joe pulseaudio[25787]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:13 joe pulseaudio[25838]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:16 joe pulseaudio[25966]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:17 joe acpid: client 25524[0:0] has disconnected
Feb  1 21:02:17 joe acpid: client connected from 26019[0:0]
Feb  1 21:02:17 joe acpid: 1 client rule loaded
Feb  1 21:02:18 joe acpid: client connected from 26017[0:0]
Feb  1 21:02:18 joe acpid: 1 client rule loaded
Feb  1 21:02:18 joe acpid: client connected from 26016[0:0]
Feb  1 21:02:18 joe acpid: 1 client rule loaded
Feb  1 21:02:18 joe acpid: client connected from 26018[0:0]
Feb  1 21:02:18 joe acpid: 1 client rule loaded
Feb  1 21:02:18 joe acpid: client connected from 26020[0:0]
Feb  1 21:02:18 joe acpid: 1 client rule loaded
Feb  1 21:02:18 joe acpid: client connected from 26021[0:0]
Feb  1 21:02:18 joe acpid: 1 client rule loaded
Feb  1 21:02:18 joe pulseaudio[26055]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:22 joe pulseaudio[26198]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:23 joe pulseaudio[26289]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:27 joe pulseaudio[26432]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:28 joe acpid: client 26019[0:0] has disconnected
Feb  1 21:02:28 joe acpid: client 26017[0:0] has disconnected
Feb  1 21:02:28 joe acpid: client 26016[0:0] has disconnected
Feb  1 21:02:28 joe acpid: client 26018[0:0] has disconnected
Feb  1 21:02:28 joe acpid: client 26020[0:0] has disconnected
Feb  1 21:02:28 joe acpid: client 26021[0:0] has disconnected
Feb  1 21:02:28 joe acpid: client connected from 26504[0:0]
Feb  1 21:02:28 joe acpid: 1 client rule loaded
Feb  1 21:02:28 joe acpid: client connected from 26502[0:0]
Feb  1 21:02:28 joe acpid: 1 client rule loaded
Feb  1 21:02:28 joe acpid: client connected from 26503[0:0]
Feb  1 21:02:28 joe acpid: 1 client rule loaded
Feb  1 21:02:28 joe acpid: client connected from 26501[0:0]
Feb  1 21:02:28 joe acpid: 1 client rule loaded
Feb  1 21:02:28 joe acpid: client 26504[0:0] has disconnected
Feb  1 21:02:28 joe acpid: client 26502[0:0] has disconnected
Feb  1 21:02:28 joe acpid: client 26503[0:0] has disconnected
Feb  1 21:02:28 joe acpid: client 26501[0:0] has disconnected
Feb  1 21:02:28 joe acpid: client connected from 26510[0:0]
Feb  1 21:02:28 joe acpid: 1 client rule loaded
Feb  1 21:02:28 joe acpid: client connected from 26512[0:0]
Feb  1 21:02:28 joe acpid: 1 client rule loaded
Feb  1 21:02:28 joe acpid: client connected from 26511[0:0]
Feb  1 21:02:28 joe acpid: 1 client rule loaded
Feb  1 21:02:28 joe pulseaudio[26521]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:32 joe pulseaudio[26647]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:33 joe pulseaudio[26696]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:37 joe pulseaudio[26794]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:38 joe pulseaudio[26883]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:43 joe acpid: client 26510[0:0] has disconnected
Feb  1 21:02:43 joe acpid: client 26512[0:0] has disconnected
Feb  1 21:02:43 joe acpid: client 26511[0:0] has disconnected
Feb  1 21:02:43 joe acpid: client connected from 27001[0:0]
Feb  1 21:02:43 joe acpid: 1 client rule loaded
Feb  1 21:02:43 joe acpid: client connected from 27000[0:0]
Feb  1 21:02:43 joe pulseaudio[27035]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:43 joe acpid: 1 client rule loaded
Feb  1 21:02:43 joe acpid: client 27001[0:0] has disconnected
Feb  1 21:02:43 joe acpid: client 27000[0:0] has disconnected
Feb  1 21:02:43 joe acpid: client connected from 27006[0:0]
Feb  1 21:02:43 joe acpid: 1 client rule loaded
Feb  1 21:02:43 joe acpid: client 27006[0:0] has disconnected
Feb  1 21:02:43 joe acpid: client connected from 27007[0:0]
Feb  1 21:02:43 joe acpid: 1 client rule loaded
Feb  1 21:02:43 joe acpid: client 27007[0:0] has disconnected
Feb  1 21:02:43 joe acpid: client connected from 27003[0:0]
Feb  1 21:02:43 joe acpid: 1 client rule loaded
Feb  1 21:02:43 joe acpid: client 27003[0:0] has disconnected
Feb  1 21:02:43 joe acpid: client connected from 27002[0:0]
Feb  1 21:02:43 joe acpid: 1 client rule loaded
Feb  1 21:02:43 joe pulseaudio[27120]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:43 joe acpid: client 27002[0:0] has disconnected
Feb  1 21:02:43 joe acpid: client connected from 27008[0:0]
Feb  1 21:02:43 joe acpid: 1 client rule loaded
Feb  1 21:02:43 joe acpid: client 27008[0:0] has disconnected
Feb  1 21:02:43 joe acpid: client connected from 27009[0:0]
Feb  1 21:02:43 joe acpid: 1 client rule loaded
Feb  1 21:02:43 joe acpid: client 27009[0:0] has disconnected
Feb  1 21:02:43 joe acpid: client connected from 26999[0:0]
Feb  1 21:02:43 joe acpid: 1 client rule loaded
Feb  1 21:02:43 joe acpid: client 26999[0:0] has disconnected
Feb  1 21:02:43 joe acpid: client connected from 27019[0:0]
Feb  1 21:02:43 joe acpid: 1 client rule loaded
Feb  1 21:02:43 joe acpid: client 27019[0:0] has disconnected
Feb  1 21:02:43 joe acpid: client connected from 27017[0:0]
Feb  1 21:02:43 joe acpid: 1 client rule loaded
Feb  1 21:02:43 joe acpid: client 27017[0:0] has disconnected
Feb  1 21:02:43 joe acpid: client connected from 27018[0:0]
Feb  1 21:02:43 joe acpid: 1 client rule loaded
Feb  1 21:02:43 joe acpid: client 27018[0:0] has disconnected
Feb  1 21:02:43 joe acpid: client connected from 27020[0:0]
Feb  1 21:02:43 joe acpid: 1 client rule loaded
Feb  1 21:02:43 joe acpid: client 27020[0:0] has disconnected
Feb  1 21:02:43 joe acpid: client connected from 27022[0:0]
Feb  1 21:02:43 joe acpid: 1 client rule loaded
Feb  1 21:02:48 joe pulseaudio[27287]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:49 joe pulseaudio[27376]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:54 joe acpid: client 27022[0:0] has disconnected
Feb  1 21:02:54 joe acpid: client connected from 27495[0:0]
Feb  1 21:02:54 joe acpid: 1 client rule loaded
Feb  1 21:02:54 joe acpid: client connected from 27500[0:0]
Feb  1 21:02:54 joe acpid: 1 client rule loaded
Feb  1 21:02:54 joe acpid: client connected from 27497[0:0]
Feb  1 21:02:54 joe acpid: 1 client rule loaded
Feb  1 21:02:54 joe pulseaudio[27546]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:54 joe acpid: client 27495[0:0] has disconnected
Feb  1 21:02:54 joe acpid: client 27500[0:0] has disconnected
Feb  1 21:02:54 joe acpid: client 27497[0:0] has disconnected
Feb  1 21:02:54 joe acpid: client connected from 27521[0:0]
Feb  1 21:02:54 joe acpid: 1 client rule loaded
Feb  1 21:02:54 joe acpid: client 27521[0:0] has disconnected
Feb  1 21:02:54 joe acpid: client connected from 27519[0:0]
Feb  1 21:02:54 joe acpid: 1 client rule loaded
Feb  1 21:02:54 joe acpid: client 27519[0:0] has disconnected
Feb  1 21:02:54 joe acpid: client connected from 27496[0:0]
Feb  1 21:02:54 joe acpid: 1 client rule loaded
Feb  1 21:02:54 joe acpid: client 27496[0:0] has disconnected
Feb  1 21:02:54 joe acpid: client connected from 27516[0:0]
Feb  1 21:02:54 joe acpid: 1 client rule loaded
Feb  1 21:02:54 joe acpid: client 27516[0:0] has disconnected
Feb  1 21:02:54 joe acpid: client connected from 27498[0:0]
Feb  1 21:02:54 joe acpid: 1 client rule loaded
Feb  1 21:02:54 joe acpid: client 27498[0:0] has disconnected
Feb  1 21:02:54 joe acpid: client connected from 27518[0:0]
Feb  1 21:02:54 joe acpid: 1 client rule loaded
Feb  1 21:02:54 joe pulseaudio[27628]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:58 joe pulseaudio[27812]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:02:59 joe pulseaudio[27857]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:04 joe pulseaudio[28039]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:04 joe pulseaudio[28057]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:04 joe acpid: client 27518[0:0] has disconnected
Feb  1 21:03:04 joe acpid: client connected from 28068[0:0]
Feb  1 21:03:04 joe acpid: 1 client rule loaded
Feb  1 21:03:04 joe acpid: client connected from 28059[0:0]
Feb  1 21:03:04 joe acpid: 1 client rule loaded
Feb  1 21:03:04 joe acpid: client connected from 28066[0:0]
Feb  1 21:03:04 joe acpid: 1 client rule loaded
Feb  1 21:03:04 joe acpid: client connected from 28064[0:0]
Feb  1 21:03:04 joe acpid: 1 client rule loaded
Feb  1 21:03:04 joe acpid: client connected from 28058[0:0]
Feb  1 21:03:04 joe acpid: 1 client rule loaded
Feb  1 21:03:04 joe acpid: client connected from 28069[0:0]
Feb  1 21:03:04 joe acpid: 1 client rule loaded
Feb  1 21:03:04 joe acpid: client connected from 28060[0:0]
Feb  1 21:03:04 joe acpid: 1 client rule loaded
Feb  1 21:03:04 joe acpid: client connected from 28070[0:0]
Feb  1 21:03:04 joe acpid: 1 client rule loaded
Feb  1 21:03:04 joe acpid: client connected from 28065[0:0]
Feb  1 21:03:04 joe acpid: 1 client rule loaded
Feb  1 21:03:04 joe acpid: client connected from 28063[0:0]
Feb  1 21:03:04 joe acpid: 1 client rule loaded
Feb  1 21:03:04 joe acpid: client connected from 28061[0:0]
Feb  1 21:03:04 joe acpid: 1 client rule loaded
Feb  1 21:03:04 joe acpid: client connected from 28062[0:0]
Feb  1 21:03:04 joe acpid: 1 client rule loaded
Feb  1 21:03:10 joe pulseaudio[28249]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:10 joe pulseaudio[28294]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:14 joe pulseaudio[28480]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:14 joe pulseaudio[28523]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:15 joe acpid: client 28068[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28059[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28066[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28064[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28058[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28069[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28060[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28070[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28065[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28063[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28061[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28062[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client connected from 28552[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28556[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28554[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28558[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28562[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28553[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28567[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28581[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28570[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28572[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28574[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28576[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28580[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28579[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28577[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28578[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28551[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28568[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28564[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28565[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client 28552[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client connected from 28566[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client 28556[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28554[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28558[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28562[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28553[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28567[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28581[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28570[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28572[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28574[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28576[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28580[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28579[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28577[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28578[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28551[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28568[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28564[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28565[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client 28566[0:0] has disconnected
Feb  1 21:03:15 joe acpid: client connected from 28598[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:15 joe acpid: client connected from 28599[0:0]
Feb  1 21:03:15 joe acpid: 1 client rule loaded
Feb  1 21:03:21 joe pulseaudio[28725]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:21 joe pulseaudio[28764]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:25 joe pulseaudio[28888]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:25 joe pulseaudio[28913]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:30 joe pulseaudio[29017]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:32 joe pulseaudio[29059]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:32 joe acpid: client 28598[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client 28599[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client connected from 29060[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client 29060[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client connected from 29065[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client connected from 29063[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client connected from 29064[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client 29065[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client 29063[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client 29064[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client connected from 29062[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client 29062[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client connected from 29067[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client 29067[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client connected from 29081[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client 29081[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client connected from 29079[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client 29079[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client connected from 29075[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client 29075[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client connected from 29077[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client 29077[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client connected from 29073[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client 29073[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client connected from 29083[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client 29083[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client connected from 29080[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client 29080[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client connected from 29074[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client 29074[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client connected from 29085[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client 29085[0:0] has disconnected
Feb  1 21:03:32 joe acpid: client connected from 29082[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client connected from 29084[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:32 joe acpid: client connected from 29076[0:0]
Feb  1 21:03:32 joe acpid: 1 client rule loaded
Feb  1 21:03:34 joe pulseaudio[29242]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:36 joe pulseaudio[29283]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:39 joe pulseaudio[29375]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:42 joe pulseaudio[29410]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:44 joe acpid: client 29082[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29084[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29076[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client connected from 29556[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29558[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29555[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29560[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29562[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29559[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29561[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29567[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29570[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29569[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29576[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29557[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29554[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29596[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29594[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29571[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29573[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29575[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29566[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29574[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29572[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29564[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29597[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client connected from 29595[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client 29556[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29558[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29555[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29560[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29562[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29559[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29561[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29567[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29570[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29569[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29557[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29554[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29596[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29594[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29571[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29573[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29566[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29574[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29572[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client 29597[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client connected from 29610[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client 29595[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client connected from 29609[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client 29564[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client connected from 29607[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe acpid: client 29575[0:0] has disconnected
Feb  1 21:03:44 joe acpid: client connected from 29606[0:0]
Feb  1 21:03:44 joe acpid: 1 client rule loaded
Feb  1 21:03:44 joe pulseaudio[29617]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:49 joe pulseaudio[29661]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:50 joe pulseaudio[29801]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:53 joe pulseaudio[29849]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:54 joe pulseaudio[29971]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:56 joe acpid: client 29576[0:0] has disconnected
Feb  1 21:03:56 joe acpid: client 29610[0:0] has disconnected
Feb  1 21:03:56 joe acpid: client 29609[0:0] has disconnected
Feb  1 21:03:56 joe acpid: client 29607[0:0] has disconnected
Feb  1 21:03:56 joe acpid: client 29606[0:0] has disconnected
Feb  1 21:03:56 joe acpid: client connected from 30038[0:0]
Feb  1 21:03:56 joe acpid: 1 client rule loaded
Feb  1 21:03:56 joe acpid: client connected from 30039[0:0]
Feb  1 21:03:56 joe acpid: 1 client rule loaded
Feb  1 21:03:56 joe acpid: client connected from 30042[0:0]
Feb  1 21:03:56 joe acpid: 1 client rule loaded
Feb  1 21:03:56 joe acpid: client connected from 30040[0:0]
Feb  1 21:03:56 joe acpid: 1 client rule loaded
Feb  1 21:03:56 joe acpid: client connected from 30041[0:0]
Feb  1 21:03:56 joe acpid: 1 client rule loaded
Feb  1 21:03:56 joe pulseaudio[30050]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:03:56 joe acpid: client 30038[0:0] has disconnected
Feb  1 21:03:56 joe acpid: client 30039[0:0] has disconnected
Feb  1 21:03:56 joe acpid: client 30042[0:0] has disconnected
Feb  1 21:03:56 joe acpid: client 30040[0:0] has disconnected
Feb  1 21:03:56 joe acpid: client 30041[0:0] has disconnected
Feb  1 21:03:56 joe acpid: client connected from 30052[0:0]
Feb  1 21:03:56 joe acpid: 1 client rule loaded
Feb  1 21:03:56 joe acpid: client connected from 30051[0:0]
Feb  1 21:03:56 joe acpid: 1 client rule loaded
Feb  1 21:03:56 joe acpid: client connected from 30062[0:0]
Feb  1 21:03:56 joe acpid: 1 client rule loaded
Feb  1 21:03:56 joe acpid: client connected from 30056[0:0]
Feb  1 21:03:56 joe acpid: 1 client rule loaded
Feb  1 21:03:56 joe acpid: client connected from 30061[0:0]
Feb  1 21:03:56 joe acpid: 1 client rule loaded
Feb  1 21:04:02 joe pulseaudio[30186]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:02 joe pulseaudio[30221]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:05 joe pulseaudio[30303]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:06 joe pulseaudio[30338]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:06 joe pulseaudio[30344]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:06 joe pulseaudio[30367]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:09 joe pulseaudio[30479]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:11 joe acpid: client 30052[0:0] has disconnected
Feb  1 21:04:11 joe acpid: client 30051[0:0] has disconnected
Feb  1 21:04:11 joe acpid: client 30062[0:0] has disconnected
Feb  1 21:04:11 joe acpid: client 30056[0:0] has disconnected
Feb  1 21:04:11 joe acpid: client 30061[0:0] has disconnected
Feb  1 21:04:11 joe acpid: client connected from 30532[0:0]
Feb  1 21:04:11 joe acpid: 1 client rule loaded
Feb  1 21:04:11 joe acpid: client connected from 30530[0:0]
Feb  1 21:04:11 joe acpid: 1 client rule loaded
Feb  1 21:04:11 joe acpid: client connected from 30534[0:0]
Feb  1 21:04:11 joe acpid: 1 client rule loaded
Feb  1 21:04:11 joe acpid: client connected from 30533[0:0]
Feb  1 21:04:11 joe acpid: 1 client rule loaded
Feb  1 21:04:11 joe acpid: client connected from 30529[0:0]
Feb  1 21:04:11 joe acpid: 1 client rule loaded
Feb  1 21:04:11 joe pulseaudio[30544]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:16 joe pulseaudio[30643]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:17 joe pulseaudio[30696]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:21 joe pulseaudio[30772]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:22 joe pulseaudio[30878]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:27 joe acpid: client 30532[0:0] has disconnected
Feb  1 21:04:27 joe acpid: client 30530[0:0] has disconnected
Feb  1 21:04:27 joe acpid: client 30534[0:0] has disconnected
Feb  1 21:04:27 joe acpid: client 30533[0:0] has disconnected
Feb  1 21:04:27 joe acpid: client 30529[0:0] has disconnected
Feb  1 21:04:27 joe acpid: client connected from 30939[0:0]
Feb  1 21:04:27 joe acpid: 1 client rule loaded
Feb  1 21:04:27 joe acpid: client connected from 30940[0:0]
Feb  1 21:04:27 joe pulseaudio[30952]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:27 joe acpid: 1 client rule loaded
Feb  1 21:04:27 joe acpid: client 30939[0:0] has disconnected
Feb  1 21:04:27 joe acpid: client 30940[0:0] has disconnected
Feb  1 21:04:27 joe acpid: client connected from 30938[0:0]
Feb  1 21:04:27 joe acpid: 1 client rule loaded
Feb  1 21:04:27 joe acpid: client 30938[0:0] has disconnected
Feb  1 21:04:27 joe acpid: client connected from 30941[0:0]
Feb  1 21:04:27 joe acpid: 1 client rule loaded
Feb  1 21:04:27 joe acpid: client 30941[0:0] has disconnected
Feb  1 21:04:27 joe acpid: client connected from 30936[0:0]
Feb  1 21:04:27 joe acpid: 1 client rule loaded
Feb  1 21:04:27 joe acpid: client 30936[0:0] has disconnected
Feb  1 21:04:27 joe acpid: client connected from 30937[0:0]
Feb  1 21:04:27 joe acpid: 1 client rule loaded
Feb  1 21:04:27 joe acpid: client 30937[0:0] has disconnected
Feb  1 21:04:27 joe acpid: client connected from 30942[0:0]
Feb  1 21:04:27 joe acpid: 1 client rule loaded
Feb  1 21:04:27 joe pulseaudio[31059]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:31 joe pulseaudio[31173]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:34 joe pulseaudio[31222]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:36 joe acpid: client 30942[0:0] has disconnected
Feb  1 21:04:36 joe acpid: client connected from 31360[0:0]
Feb  1 21:04:36 joe acpid: 1 client rule loaded
Feb  1 21:04:36 joe acpid: client connected from 31362[0:0]
Feb  1 21:04:36 joe acpid: 1 client rule loaded
Feb  1 21:04:36 joe acpid: client 31360[0:0] has disconnected
Feb  1 21:04:36 joe acpid: client connected from 31364[0:0]
Feb  1 21:04:36 joe acpid: 1 client rule loaded
Feb  1 21:04:36 joe acpid: client connected from 31363[0:0]
Feb  1 21:04:36 joe acpid: 1 client rule loaded
Feb  1 21:04:36 joe acpid: client connected from 31368[0:0]
Feb  1 21:04:36 joe acpid: 1 client rule loaded
Feb  1 21:04:36 joe acpid: client connected from 31375[0:0]
Feb  1 21:04:36 joe acpid: 1 client rule loaded
Feb  1 21:04:36 joe acpid: client connected from 31373[0:0]
Feb  1 21:04:36 joe acpid: 1 client rule loaded
Feb  1 21:04:36 joe acpid: client connected from 31383[0:0]
Feb  1 21:04:36 joe acpid: 1 client rule loaded
Feb  1 21:04:36 joe acpid: client connected from 31380[0:0]
Feb  1 21:04:36 joe acpid: 1 client rule loaded
Feb  1 21:04:36 joe acpid: client connected from 31374[0:0]
Feb  1 21:04:36 joe acpid: 1 client rule loaded
Feb  1 21:04:36 joe acpid: client connected from 31372[0:0]
Feb  1 21:04:36 joe acpid: 1 client rule loaded
Feb  1 21:04:36 joe acpid: client connected from 31371[0:0]
Feb  1 21:04:36 joe acpid: 1 client rule loaded
Feb  1 21:04:36 joe acpid: client connected from 31370[0:0]
Feb  1 21:04:36 joe acpid: 1 client rule loaded
Feb  1 21:04:36 joe acpid: client connected from 31381[0:0]
Feb  1 21:04:36 joe acpid: 1 client rule loaded
Feb  1 21:04:36 joe pulseaudio[31392]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:37 joe pulseaudio[31431]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:41 joe pulseaudio[31596]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:42 joe pulseaudio[31637]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:46 joe pulseaudio[31785]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:47 joe pulseaudio[31810]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:50 joe acpid: client 31362[0:0] has disconnected
Feb  1 21:04:50 joe acpid: client 31364[0:0] has disconnected
Feb  1 21:04:50 joe acpid: client 31363[0:0] has disconnected
Feb  1 21:04:50 joe acpid: client 31368[0:0] has disconnected
Feb  1 21:04:50 joe acpid: client 31375[0:0] has disconnected
Feb  1 21:04:50 joe acpid: client 31373[0:0] has disconnected
Feb  1 21:04:50 joe acpid: client 31383[0:0] has disconnected
Feb  1 21:04:50 joe acpid: client 31380[0:0] has disconnected
Feb  1 21:04:51 joe acpid: client 31374[0:0] has disconnected
Feb  1 21:04:51 joe acpid: client 31372[0:0] has disconnected
Feb  1 21:04:51 joe acpid: client 31371[0:0] has disconnected
Feb  1 21:04:51 joe acpid: client 31370[0:0] has disconnected
Feb  1 21:04:51 joe acpid: client 31381[0:0] has disconnected
Feb  1 21:04:51 joe acpid: client connected from 31855[0:0]
Feb  1 21:04:51 joe acpid: 1 client rule loaded
Feb  1 21:04:51 joe acpid: client 31855[0:0] has disconnected
Feb  1 21:04:51 joe acpid: client connected from 31859[0:0]
Feb  1 21:04:51 joe acpid: 1 client rule loaded
Feb  1 21:04:51 joe acpid: client 31859[0:0] has disconnected
Feb  1 21:04:51 joe acpid: client connected from 31861[0:0]
Feb  1 21:04:51 joe acpid: 1 client rule loaded
Feb  1 21:04:51 joe acpid: client 31861[0:0] has disconnected
Feb  1 21:04:51 joe acpid: client connected from 31860[0:0]
Feb  1 21:04:51 joe acpid: 1 client rule loaded
Feb  1 21:04:51 joe pulseaudio[31954]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:52 joe pulseaudio[31990]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:57 joe pulseaudio[32120]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:04:58 joe pulseaudio[32136]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:01 joe pulseaudio[32285]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:04 joe acpid: client 31860[0:0] has disconnected
Feb  1 21:05:04 joe acpid: client connected from 32298[0:0]
Feb  1 21:05:04 joe acpid: 1 client rule loaded
Feb  1 21:05:04 joe acpid: client connected from 32303[0:0]
Feb  1 21:05:04 joe acpid: 1 client rule loaded
Feb  1 21:05:04 joe acpid: client connected from 32299[0:0]
Feb  1 21:05:04 joe acpid: 1 client rule loaded
Feb  1 21:05:04 joe acpid: client connected from 32309[0:0]
Feb  1 21:05:04 joe acpid: 1 client rule loaded
Feb  1 21:05:04 joe pulseaudio[32356]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:04 joe acpid: client 32298[0:0] has disconnected
Feb  1 21:05:04 joe acpid: client 32303[0:0] has disconnected
Feb  1 21:05:04 joe acpid: client 32299[0:0] has disconnected
Feb  1 21:05:04 joe acpid: client 32309[0:0] has disconnected
Feb  1 21:05:04 joe acpid: client connected from 32297[0:0]
Feb  1 21:05:04 joe acpid: 1 client rule loaded
Feb  1 21:05:05 joe acpid: client 32297[0:0] has disconnected
Feb  1 21:05:05 joe acpid: client connected from 32319[0:0]
Feb  1 21:05:05 joe acpid: 1 client rule loaded
Feb  1 21:05:05 joe acpid: client 32319[0:0] has disconnected
Feb  1 21:05:05 joe acpid: client connected from 32315[0:0]
Feb  1 21:05:05 joe acpid: 1 client rule loaded
Feb  1 21:05:05 joe acpid: client 32315[0:0] has disconnected
Feb  1 21:05:05 joe acpid: client connected from 32296[0:0]
Feb  1 21:05:05 joe acpid: 1 client rule loaded
Feb  1 21:05:05 joe acpid: client 32296[0:0] has disconnected
Feb  1 21:05:05 joe acpid: client connected from 32321[0:0]
Feb  1 21:05:05 joe acpid: 1 client rule loaded
Feb  1 21:05:05 joe acpid: client 32321[0:0] has disconnected
Feb  1 21:05:05 joe acpid: client connected from 32312[0:0]
Feb  1 21:05:05 joe acpid: 1 client rule loaded
Feb  1 21:05:05 joe acpid: client 32312[0:0] has disconnected
Feb  1 21:05:05 joe acpid: client connected from 32304[0:0]
Feb  1 21:05:05 joe acpid: 1 client rule loaded
Feb  1 21:05:05 joe acpid: client 32304[0:0] has disconnected
Feb  1 21:05:05 joe acpid: client connected from 32310[0:0]
Feb  1 21:05:05 joe acpid: 1 client rule loaded
Feb  1 21:05:05 joe acpid: client 32310[0:0] has disconnected
Feb  1 21:05:05 joe acpid: client connected from 32318[0:0]
Feb  1 21:05:05 joe acpid: 1 client rule loaded
Feb  1 21:05:05 joe acpid: client 32318[0:0] has disconnected
Feb  1 21:05:05 joe acpid: client connected from 32300[0:0]
Feb  1 21:05:05 joe acpid: 1 client rule loaded
Feb  1 21:05:05 joe acpid: client 32300[0:0] has disconnected
Feb  1 21:05:05 joe acpid: client connected from 32316[0:0]
Feb  1 21:05:05 joe acpid: 1 client rule loaded
Feb  1 21:05:05 joe acpid: client 32316[0:0] has disconnected
Feb  1 21:05:05 joe acpid: client connected from 32320[0:0]
Feb  1 21:05:05 joe acpid: 1 client rule loaded
Feb  1 21:05:05 joe acpid: client 32320[0:0] has disconnected
Feb  1 21:05:05 joe acpid: client connected from 32313[0:0]
Feb  1 21:05:05 joe acpid: 1 client rule loaded
Feb  1 21:05:05 joe acpid: client 32313[0:0] has disconnected
Feb  1 21:05:05 joe acpid: client connected from 32311[0:0]
Feb  1 21:05:05 joe acpid: 1 client rule loaded
Feb  1 21:05:05 joe acpid: client 32311[0:0] has disconnected
Feb  1 21:05:05 joe acpid: client connected from 32314[0:0]
Feb  1 21:05:05 joe acpid: 1 client rule loaded
Feb  1 21:05:05 joe acpid: client 32314[0:0] has disconnected
Feb  1 21:05:05 joe acpid: client connected from 32302[0:0]
Feb  1 21:05:05 joe acpid: 1 client rule loaded
Feb  1 21:05:05 joe acpid: client 32302[0:0] has disconnected
Feb  1 21:05:05 joe acpid: client connected from 32322[0:0]
Feb  1 21:05:05 joe acpid: 1 client rule loaded
Feb  1 21:05:06 joe pulseaudio[32471]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:11 joe pulseaudio[32587]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:12 joe pulseaudio[32649]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:14 joe pulseaudio[32753]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:18 joe acpid: client 32322[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client connected from 306[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client connected from 304[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client connected from 305[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client connected from 316[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe pulseaudio[385]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:18 joe acpid: client 306[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client 304[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client 305[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client 316[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client connected from 321[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client 321[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client connected from 318[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client 318[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client connected from 303[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client 303[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client connected from 325[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client 325[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client connected from 326[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client 326[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client connected from 309[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client 309[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client connected from 313[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client 313[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client connected from 328[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client 328[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client connected from 347[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client 347[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client connected from 335[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client 335[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client connected from 338[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client 338[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client connected from 340[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client 340[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client connected from 337[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client 337[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client connected from 339[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client 339[0:0] has disconnected
Feb  1 21:05:18 joe acpid: client connected from 342[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client connected from 343[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client connected from 344[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client connected from 345[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client connected from 346[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:18 joe acpid: client connected from 334[0:0]
Feb  1 21:05:18 joe acpid: 1 client rule loaded
Feb  1 21:05:19 joe pulseaudio[496]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:25 joe pulseaudio[644]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:26 joe pulseaudio[683]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:31 joe pulseaudio[809]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:31 joe pulseaudio[811]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:31 joe acpid: client 342[0:0] has disconnected
Feb  1 21:05:31 joe acpid: client 343[0:0] has disconnected
Feb  1 21:05:31 joe acpid: client 344[0:0] has disconnected
Feb  1 21:05:31 joe acpid: client 345[0:0] has disconnected
Feb  1 21:05:31 joe acpid: client 346[0:0] has disconnected
Feb  1 21:05:31 joe acpid: client 334[0:0] has disconnected
Feb  1 21:05:31 joe acpid: client connected from 814[0:0]
Feb  1 21:05:31 joe acpid: 1 client rule loaded
Feb  1 21:05:31 joe acpid: client 814[0:0] has disconnected
Feb  1 21:05:31 joe acpid: client connected from 813[0:0]
Feb  1 21:05:31 joe acpid: 1 client rule loaded
Feb  1 21:05:31 joe acpid: client 813[0:0] has disconnected
Feb  1 21:05:31 joe acpid: client connected from 812[0:0]
Feb  1 21:05:31 joe acpid: 1 client rule loaded
Feb  1 21:05:31 joe acpid: client 812[0:0] has disconnected
Feb  1 21:05:31 joe acpid: client connected from 822[0:0]
Feb  1 21:05:31 joe acpid: 1 client rule loaded
Feb  1 21:05:31 joe acpid: client 822[0:0] has disconnected
Feb  1 21:05:31 joe acpid: client connected from 832[0:0]
Feb  1 21:05:31 joe acpid: 1 client rule loaded
Feb  1 21:05:31 joe acpid: client 832[0:0] has disconnected
Feb  1 21:05:31 joe acpid: client connected from 820[0:0]
Feb  1 21:05:31 joe acpid: 1 client rule loaded
Feb  1 21:05:31 joe acpid: client 820[0:0] has disconnected
Feb  1 21:05:31 joe acpid: client connected from 823[0:0]
Feb  1 21:05:31 joe acpid: 1 client rule loaded
Feb  1 21:05:31 joe acpid: client 823[0:0] has disconnected
Feb  1 21:05:31 joe acpid: client connected from 819[0:0]
Feb  1 21:05:31 joe acpid: 1 client rule loaded
Feb  1 21:05:36 joe pulseaudio[1022]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:36 joe pulseaudio[1021]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:41 joe pulseaudio[1216]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:41 joe pulseaudio[1217]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:43 joe acpid: client 819[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client connected from 1309[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1311[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1307[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1318[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1304[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1320[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1305[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1308[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1313[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1319[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1324[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1306[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1323[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1314[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1312[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1317[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1322[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1316[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client 1309[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1311[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1307[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1318[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1304[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1320[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1305[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1308[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1313[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1319[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1324[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1306[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1323[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1314[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1312[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1317[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1322[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client 1316[0:0] has disconnected
Feb  1 21:05:43 joe acpid: client connected from 1345[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1343[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1362[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1355[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1344[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1341[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1354[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1349[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1348[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1357[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1353[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1361[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1360[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1350[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1346[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1358[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1352[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1351[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1364[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1363[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:43 joe acpid: client connected from 1356[0:0]
Feb  1 21:05:43 joe acpid: 1 client rule loaded
Feb  1 21:05:44 joe acpid: client connected from 1384[0:0]
Feb  1 21:05:44 joe acpid: 1 client rule loaded
Feb  1 21:05:44 joe acpid: client connected from 1386[0:0]
Feb  1 21:05:44 joe acpid: 1 client rule loaded
Feb  1 21:05:44 joe acpid: client connected from 1385[0:0]
Feb  1 21:05:44 joe acpid: 1 client rule loaded
Feb  1 21:05:47 joe pulseaudio[1406]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:47 joe pulseaudio[1407]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:49 joe acpid: client 1345[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1343[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1362[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1355[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1344[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1341[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1354[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1349[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1348[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1357[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1353[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1361[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1360[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1350[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1346[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1358[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1352[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1351[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1364[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1363[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1356[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1384[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1386[0:0] has disconnected
Feb  1 21:05:49 joe acpid: client 1385[0:0] has disconnected
Feb  1 21:05:50 joe pulseaudio[1642]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:50 joe pulseaudio[1640]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:55 joe acpid: client connected from 1827[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1828[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1826[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1834[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1832[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1833[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe pulseaudio[1840]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:55 joe pulseaudio[1841]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:05:55 joe acpid: client 1827[0:0] has disconnected
Feb  1 21:05:55 joe acpid: client 1828[0:0] has disconnected
Feb  1 21:05:55 joe acpid: client 1826[0:0] has disconnected
Feb  1 21:05:55 joe acpid: client 1834[0:0] has disconnected
Feb  1 21:05:55 joe acpid: client 1832[0:0] has disconnected
Feb  1 21:05:55 joe acpid: client 1833[0:0] has disconnected
Feb  1 21:05:55 joe acpid: client connected from 1843[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1845[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1842[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1851[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1848[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1859[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1858[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1857[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1853[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1850[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1849[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1847[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:05:55 joe acpid: client connected from 1855[0:0]
Feb  1 21:05:55 joe acpid: 1 client rule loaded
Feb  1 21:06:00 joe acpid: client 1843[0:0] has disconnected
Feb  1 21:06:00 joe acpid: client 1845[0:0] has disconnected
Feb  1 21:06:00 joe acpid: client 1842[0:0] has disconnected
Feb  1 21:06:00 joe acpid: client 1851[0:0] has disconnected
Feb  1 21:06:00 joe acpid: client 1848[0:0] has disconnected
Feb  1 21:06:00 joe acpid: client 1859[0:0] has disconnected
Feb  1 21:06:00 joe acpid: client 1858[0:0] has disconnected
Feb  1 21:06:00 joe acpid: client 1857[0:0] has disconnected
Feb  1 21:06:00 joe acpid: client 1853[0:0] has disconnected
Feb  1 21:06:00 joe acpid: client 1850[0:0] has disconnected
Feb  1 21:06:00 joe acpid: client 1849[0:0] has disconnected
Feb  1 21:06:00 joe acpid: client 1847[0:0] has disconnected
Feb  1 21:06:00 joe acpid: client 1855[0:0] has disconnected
Feb  1 21:06:00 joe pulseaudio[2049]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:00 joe pulseaudio[2047]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:07 joe pulseaudio[2280]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:07 joe pulseaudio[2305]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:07 joe acpid: client connected from 2399[0:0]
Feb  1 21:06:07 joe acpid: 1 client rule loaded
Feb  1 21:06:07 joe acpid: client connected from 2398[0:0]
Feb  1 21:06:07 joe acpid: 1 client rule loaded
Feb  1 21:06:07 joe acpid: client connected from 2397[0:0]
Feb  1 21:06:07 joe acpid: 1 client rule loaded
Feb  1 21:06:07 joe acpid: client connected from 2401[0:0]
Feb  1 21:06:07 joe acpid: 1 client rule loaded
Feb  1 21:06:07 joe acpid: client connected from 2400[0:0]
Feb  1 21:06:07 joe acpid: 1 client rule loaded
Feb  1 21:06:07 joe acpid: client connected from 2402[0:0]
Feb  1 21:06:07 joe acpid: 1 client rule loaded
Feb  1 21:06:08 joe acpid: client 2399[0:0] has disconnected
Feb  1 21:06:08 joe acpid: client 2398[0:0] has disconnected
Feb  1 21:06:08 joe acpid: client 2397[0:0] has disconnected
Feb  1 21:06:08 joe acpid: client 2401[0:0] has disconnected
Feb  1 21:06:08 joe acpid: client 2400[0:0] has disconnected
Feb  1 21:06:08 joe acpid: client 2402[0:0] has disconnected
Feb  1 21:06:12 joe pulseaudio[2523]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:12 joe pulseaudio[2527]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:18 joe pulseaudio[2645]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:18 joe pulseaudio[2644]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:23 joe pulseaudio[2846]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:23 joe pulseaudio[2847]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:24 joe acpid: client connected from 2897[0:0]
Feb  1 21:06:24 joe acpid: 1 client rule loaded
Feb  1 21:06:24 joe acpid: client connected from 2896[0:0]
Feb  1 21:06:24 joe acpid: 1 client rule loaded
Feb  1 21:06:24 joe acpid: client connected from 2894[0:0]
Feb  1 21:06:24 joe acpid: 1 client rule loaded
Feb  1 21:06:24 joe acpid: client connected from 2893[0:0]
Feb  1 21:06:24 joe acpid: 1 client rule loaded
Feb  1 21:06:24 joe acpid: client 2897[0:0] has disconnected
Feb  1 21:06:24 joe acpid: client 2896[0:0] has disconnected
Feb  1 21:06:24 joe acpid: client 2894[0:0] has disconnected
Feb  1 21:06:24 joe acpid: client 2893[0:0] has disconnected
Feb  1 21:06:24 joe acpid: client connected from 2904[0:0]
Feb  1 21:06:24 joe acpid: 1 client rule loaded
Feb  1 21:06:25 joe acpid: client 2904[0:0] has disconnected
Feb  1 21:06:26 joe pulseaudio[2980]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:26 joe pulseaudio[2983]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:31 joe pulseaudio[3174]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:31 joe pulseaudio[3175]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:36 joe pulseaudio[3371]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:36 joe pulseaudio[3372]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:37 joe acpid: client connected from 3390[0:0]
Feb  1 21:06:37 joe acpid: 1 client rule loaded
Feb  1 21:06:37 joe acpid: client 3390[0:0] has disconnected
Feb  1 21:06:37 joe acpid: client connected from 3396[0:0]
Feb  1 21:06:37 joe acpid: 1 client rule loaded
Feb  1 21:06:37 joe acpid: client connected from 3397[0:0]
Feb  1 21:06:37 joe acpid: 1 client rule loaded
Feb  1 21:06:37 joe acpid: client connected from 3395[0:0]
Feb  1 21:06:37 joe acpid: 1 client rule loaded
Feb  1 21:06:37 joe acpid: client connected from 3393[0:0]
Feb  1 21:06:37 joe acpid: 1 client rule loaded
Feb  1 21:06:37 joe acpid: client connected from 3402[0:0]
Feb  1 21:06:37 joe acpid: 1 client rule loaded
Feb  1 21:06:37 joe acpid: client connected from 3394[0:0]
Feb  1 21:06:37 joe acpid: 1 client rule loaded
Feb  1 21:06:37 joe acpid: client 3397[0:0] has disconnected
Feb  1 21:06:37 joe acpid: client 3395[0:0] has disconnected
Feb  1 21:06:39 joe acpid: client 3396[0:0] has disconnected
Feb  1 21:06:39 joe acpid: client 3393[0:0] has disconnected
Feb  1 21:06:39 joe acpid: client 3402[0:0] has disconnected
Feb  1 21:06:39 joe acpid: client 3394[0:0] has disconnected
Feb  1 21:06:41 joe pulseaudio[3576]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:41 joe pulseaudio[3574]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:46 joe pulseaudio[3772]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:46 joe pulseaudio[3771]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:50 joe acpid: client connected from 3897[0:0]
Feb  1 21:06:50 joe acpid: 1 client rule loaded
Feb  1 21:06:50 joe acpid: client connected from 3896[0:0]
Feb  1 21:06:50 joe acpid: 1 client rule loaded
Feb  1 21:06:50 joe acpid: client connected from 3901[0:0]
Feb  1 21:06:50 joe acpid: 1 client rule loaded
Feb  1 21:06:50 joe acpid: client connected from 3898[0:0]
Feb  1 21:06:50 joe acpid: 1 client rule loaded
Feb  1 21:06:50 joe acpid: client connected from 3899[0:0]
Feb  1 21:06:50 joe acpid: 1 client rule loaded
Feb  1 21:06:50 joe acpid: client connected from 3903[0:0]
Feb  1 21:06:50 joe acpid: 1 client rule loaded
Feb  1 21:06:50 joe acpid: client connected from 3900[0:0]
Feb  1 21:06:50 joe acpid: 1 client rule loaded
Feb  1 21:06:51 joe acpid: client 3897[0:0] has disconnected
Feb  1 21:06:51 joe acpid: client 3896[0:0] has disconnected
Feb  1 21:06:51 joe acpid: client 3901[0:0] has disconnected
Feb  1 21:06:51 joe acpid: client 3898[0:0] has disconnected
Feb  1 21:06:51 joe acpid: client 3899[0:0] has disconnected
Feb  1 21:06:51 joe acpid: client 3903[0:0] has disconnected
Feb  1 21:06:51 joe acpid: client 3900[0:0] has disconnected
Feb  1 21:06:51 joe pulseaudio[3940]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:51 joe pulseaudio[3941]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:56 joe pulseaudio[4131]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:06:56 joe pulseaudio[4132]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:01 joe pulseaudio[4325]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:01 joe pulseaudio[4326]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:03 joe acpid: client connected from 4389[0:0]
Feb  1 21:07:03 joe acpid: 1 client rule loaded
Feb  1 21:07:03 joe acpid: client connected from 4393[0:0]
Feb  1 21:07:03 joe acpid: 1 client rule loaded
Feb  1 21:07:03 joe acpid: client connected from 4391[0:0]
Feb  1 21:07:03 joe acpid: 1 client rule loaded
Feb  1 21:07:03 joe acpid: client 4389[0:0] has disconnected
Feb  1 21:07:03 joe acpid: client connected from 4392[0:0]
Feb  1 21:07:03 joe acpid: 1 client rule loaded
Feb  1 21:07:03 joe acpid: client 4393[0:0] has disconnected
Feb  1 21:07:03 joe acpid: client 4391[0:0] has disconnected
Feb  1 21:07:03 joe acpid: client 4392[0:0] has disconnected
Feb  1 21:07:03 joe acpid: client connected from 4398[0:0]
Feb  1 21:07:03 joe acpid: 1 client rule loaded
Feb  1 21:07:03 joe acpid: client connected from 4399[0:0]
Feb  1 21:07:03 joe acpid: 1 client rule loaded
Feb  1 21:07:03 joe acpid: client 4398[0:0] has disconnected
Feb  1 21:07:03 joe acpid: client 4399[0:0] has disconnected
Feb  1 21:07:06 joe pulseaudio[4522]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:06 joe pulseaudio[4523]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:11 joe pulseaudio[4717]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:11 joe pulseaudio[4715]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:16 joe acpid: client connected from 4896[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4900[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4906[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4898[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client 4896[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client connected from 4915[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4911[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client 4900[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4911[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client connected from 4918[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4910[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4914[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4908[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4901[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4899[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4904[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4916[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4903[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4907[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4930[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4932[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4931[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client 4906[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4898[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4915[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4918[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4910[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4914[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4908[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4901[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4899[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4904[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4916[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4903[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4907[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4930[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4932[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4931[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client connected from 4945[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4948[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe pulseaudio[4940]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:16 joe acpid: client connected from 4944[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4955[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4962[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4947[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4946[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4959[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4943[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4949[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe pulseaudio[4941]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:16 joe acpid: client connected from 4956[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4960[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4953[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4951[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4942[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4958[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client connected from 4952[0:0]
Feb  1 21:07:16 joe acpid: 1 client rule loaded
Feb  1 21:07:16 joe acpid: client 4947[0:0] has disconnected
Feb  1 21:07:16 joe acpid: client 4946[0:0] has disconnected
Feb  1 21:07:17 joe acpid: client 4945[0:0] has disconnected
Feb  1 21:07:17 joe acpid: client 4948[0:0] has disconnected
Feb  1 21:07:17 joe acpid: client 4944[0:0] has disconnected
Feb  1 21:07:17 joe acpid: client 4955[0:0] has disconnected
Feb  1 21:07:17 joe acpid: client 4962[0:0] has disconnected
Feb  1 21:07:17 joe acpid: client 4959[0:0] has disconnected
Feb  1 21:07:17 joe acpid: client 4943[0:0] has disconnected
Feb  1 21:07:17 joe acpid: client 4949[0:0] has disconnected
Feb  1 21:07:17 joe acpid: client 4956[0:0] has disconnected
Feb  1 21:07:17 joe acpid: client 4960[0:0] has disconnected
Feb  1 21:07:17 joe acpid: client 4953[0:0] has disconnected
Feb  1 21:07:17 joe acpid: client 4951[0:0] has disconnected
Feb  1 21:07:17 joe acpid: client 4942[0:0] has disconnected
Feb  1 21:07:17 joe acpid: client 4958[0:0] has disconnected
Feb  1 21:07:17 joe acpid: client 4952[0:0] has disconnected
Feb  1 21:07:24 joe pulseaudio[5139]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:24 joe pulseaudio[5138]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:27 joe pulseaudio[5222]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:27 joe pulseaudio[5223]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:31 joe pulseaudio[5402]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:31 joe pulseaudio[5401]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:31 joe acpid: client connected from 5403[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5404[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5405[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5409[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5410[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5406[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client 5403[0:0] has disconnected
Feb  1 21:07:31 joe acpid: client 5404[0:0] has disconnected
Feb  1 21:07:31 joe acpid: client 5405[0:0] has disconnected
Feb  1 21:07:31 joe acpid: client 5409[0:0] has disconnected
Feb  1 21:07:31 joe acpid: client 5410[0:0] has disconnected
Feb  1 21:07:31 joe acpid: client 5406[0:0] has disconnected
Feb  1 21:07:31 joe acpid: client connected from 5428[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5416[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5421[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5422[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5418[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5423[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5419[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5420[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5425[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5429[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5426[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5424[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:31 joe acpid: client connected from 5417[0:0]
Feb  1 21:07:31 joe acpid: 1 client rule loaded
Feb  1 21:07:34 joe acpid: client 5418[0:0] has disconnected
Feb  1 21:07:35 joe acpid: client 5428[0:0] has disconnected
Feb  1 21:07:35 joe acpid: client 5416[0:0] has disconnected
Feb  1 21:07:35 joe acpid: client 5421[0:0] has disconnected
Feb  1 21:07:35 joe acpid: client 5422[0:0] has disconnected
Feb  1 21:07:35 joe acpid: client 5423[0:0] has disconnected
Feb  1 21:07:35 joe acpid: client 5419[0:0] has disconnected
Feb  1 21:07:35 joe acpid: client 5420[0:0] has disconnected
Feb  1 21:07:35 joe acpid: client 5425[0:0] has disconnected
Feb  1 21:07:35 joe acpid: client 5429[0:0] has disconnected
Feb  1 21:07:35 joe acpid: client 5426[0:0] has disconnected
Feb  1 21:07:35 joe acpid: client 5424[0:0] has disconnected
Feb  1 21:07:35 joe acpid: client 5417[0:0] has disconnected
Feb  1 21:07:36 joe pulseaudio[5586]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:36 joe pulseaudio[5587]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:41 joe pulseaudio[5785]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:41 joe pulseaudio[5788]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:45 joe acpid: client connected from 5941[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client connected from 5949[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client connected from 5945[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client connected from 5946[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client connected from 5940[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client connected from 5944[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client connected from 5951[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client connected from 5942[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client connected from 5952[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client connected from 5947[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client connected from 5948[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client connected from 5954[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client connected from 5943[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client 5941[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client 5945[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client 5940[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client 5944[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client 5952[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client 5947[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client 5954[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client connected from 5967[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client connected from 5969[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client 5951[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client connected from 5968[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client 5949[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client 5946[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client 5942[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client 5948[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client 5943[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client connected from 5974[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client connected from 5973[0:0]
Feb  1 21:07:45 joe acpid: 1 client rule loaded
Feb  1 21:07:45 joe acpid: client 5967[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client 5969[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client 5968[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client 5974[0:0] has disconnected
Feb  1 21:07:45 joe acpid: client 5973[0:0] has disconnected
Feb  1 21:07:46 joe pulseaudio[6004]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:46 joe pulseaudio[6002]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:51 joe pulseaudio[6171]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:51 joe pulseaudio[6169]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:56 joe pulseaudio[6359]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:56 joe pulseaudio[6360]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:07:58 joe acpid: client connected from 6428[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6432[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6437[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6438[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6443[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6447[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6449[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6455[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6440[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6442[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6454[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6450[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6459[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6458[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6463[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6461[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6451[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client 6432[0:0] has disconnected
Feb  1 21:07:58 joe acpid: client connected from 6445[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6452[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:58 joe acpid: client connected from 6439[0:0]
Feb  1 21:07:58 joe acpid: 1 client rule loaded
Feb  1 21:07:59 joe acpid: client 6428[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6437[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6438[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6443[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6447[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6449[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6455[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6440[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6442[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6454[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6450[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6459[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6458[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6463[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6461[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6451[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6445[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6452[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6439[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client connected from 6482[0:0]
Feb  1 21:07:59 joe acpid: 1 client rule loaded
Feb  1 21:07:59 joe acpid: client connected from 6479[0:0]
Feb  1 21:07:59 joe acpid: 1 client rule loaded
Feb  1 21:07:59 joe acpid: client connected from 6481[0:0]
Feb  1 21:07:59 joe acpid: 1 client rule loaded
Feb  1 21:07:59 joe acpid: client connected from 6485[0:0]
Feb  1 21:07:59 joe acpid: 1 client rule loaded
Feb  1 21:07:59 joe acpid: client connected from 6480[0:0]
Feb  1 21:07:59 joe acpid: 1 client rule loaded
Feb  1 21:07:59 joe acpid: client 6482[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6479[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6481[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6485[0:0] has disconnected
Feb  1 21:07:59 joe acpid: client 6480[0:0] has disconnected
Feb  1 21:08:03 joe pulseaudio[6583]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:03 joe pulseaudio[6584]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:08 joe pulseaudio[6751]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:08 joe pulseaudio[6750]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:15 joe pulseaudio[6938]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:15 joe pulseaudio[6940]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:15 joe acpid: client connected from 6961[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client connected from 6963[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client connected from 6962[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client connected from 6975[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client 6961[0:0] has disconnected
Feb  1 21:08:15 joe acpid: client 6963[0:0] has disconnected
Feb  1 21:08:15 joe acpid: client 6962[0:0] has disconnected
Feb  1 21:08:15 joe acpid: client 6975[0:0] has disconnected
Feb  1 21:08:15 joe acpid: client connected from 6971[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client 6971[0:0] has disconnected
Feb  1 21:08:15 joe acpid: client connected from 6965[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client 6965[0:0] has disconnected
Feb  1 21:08:15 joe acpid: client connected from 6970[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client 6970[0:0] has disconnected
Feb  1 21:08:15 joe acpid: client connected from 6978[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client 6978[0:0] has disconnected
Feb  1 21:08:15 joe acpid: client connected from 6980[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client 6980[0:0] has disconnected
Feb  1 21:08:15 joe acpid: client connected from 6968[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client 6968[0:0] has disconnected
Feb  1 21:08:15 joe acpid: client connected from 6979[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client 6979[0:0] has disconnected
Feb  1 21:08:15 joe acpid: client connected from 6977[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client 6977[0:0] has disconnected
Feb  1 21:08:15 joe acpid: client connected from 6983[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client 6983[0:0] has disconnected
Feb  1 21:08:15 joe acpid: client connected from 6982[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client 6982[0:0] has disconnected
Feb  1 21:08:15 joe acpid: client connected from 6981[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client 6981[0:0] has disconnected
Feb  1 21:08:15 joe acpid: client connected from 6995[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client connected from 6991[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client connected from 6993[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client connected from 6996[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client connected from 6994[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:15 joe acpid: client connected from 6992[0:0]
Feb  1 21:08:15 joe acpid: 1 client rule loaded
Feb  1 21:08:16 joe acpid: client 6995[0:0] has disconnected
Feb  1 21:08:16 joe acpid: client 6991[0:0] has disconnected
Feb  1 21:08:16 joe acpid: client 6993[0:0] has disconnected
Feb  1 21:08:16 joe acpid: client 6996[0:0] has disconnected
Feb  1 21:08:16 joe acpid: client 6994[0:0] has disconnected
Feb  1 21:08:16 joe acpid: client 6992[0:0] has disconnected
Feb  1 21:08:19 joe pulseaudio[7147]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:19 joe pulseaudio[7145]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:23 joe pulseaudio[7328]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:24 joe pulseaudio[7354]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:27 joe pulseaudio[7489]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:27 joe acpid: client connected from 7490[0:0]
Feb  1 21:08:27 joe acpid: 1 client rule loaded
Feb  1 21:08:27 joe acpid: client connected from 7492[0:0]
Feb  1 21:08:27 joe acpid: 1 client rule loaded
Feb  1 21:08:27 joe acpid: client connected from 7494[0:0]
Feb  1 21:08:27 joe acpid: 1 client rule loaded
Feb  1 21:08:27 joe acpid: client connected from 7495[0:0]
Feb  1 21:08:27 joe acpid: 1 client rule loaded
Feb  1 21:08:27 joe acpid: client connected from 7496[0:0]
Feb  1 21:08:27 joe acpid: 1 client rule loaded
Feb  1 21:08:27 joe acpid: client connected from 7491[0:0]
Feb  1 21:08:27 joe acpid: 1 client rule loaded
Feb  1 21:08:30 joe acpid: client 7490[0:0] has disconnected
Feb  1 21:08:30 joe acpid: client 7492[0:0] has disconnected
Feb  1 21:08:30 joe acpid: client 7494[0:0] has disconnected
Feb  1 21:08:30 joe acpid: client 7495[0:0] has disconnected
Feb  1 21:08:30 joe acpid: client 7496[0:0] has disconnected
Feb  1 21:08:30 joe acpid: client 7491[0:0] has disconnected
Feb  1 21:08:30 joe acpid: client connected from 7515[0:0]
Feb  1 21:08:30 joe acpid: 1 client rule loaded
Feb  1 21:08:31 joe pulseaudio[7551]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:31 joe acpid: client 7515[0:0] has disconnected
Feb  1 21:08:31 joe acpid: client connected from 7516[0:0]
Feb  1 21:08:31 joe acpid: 1 client rule loaded
Feb  1 21:08:31 joe acpid: client 7516[0:0] has disconnected
Feb  1 21:08:31 joe acpid: client connected from 7514[0:0]
Feb  1 21:08:31 joe acpid: 1 client rule loaded
Feb  1 21:08:31 joe acpid: client 7514[0:0] has disconnected
Feb  1 21:08:31 joe acpid: client connected from 7509[0:0]
Feb  1 21:08:31 joe acpid: 1 client rule loaded
Feb  1 21:08:31 joe acpid: client 7509[0:0] has disconnected
Feb  1 21:08:31 joe acpid: client connected from 7510[0:0]
Feb  1 21:08:31 joe acpid: 1 client rule loaded
Feb  1 21:08:31 joe acpid: client 7510[0:0] has disconnected
Feb  1 21:08:31 joe acpid: client connected from 7512[0:0]
Feb  1 21:08:31 joe acpid: 1 client rule loaded
Feb  1 21:08:31 joe acpid: client 7512[0:0] has disconnected
Feb  1 21:08:32 joe pulseaudio[7667]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:35 joe pulseaudio[7772]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:37 joe pulseaudio[7850]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:40 joe pulseaudio[7956]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:43 joe acpid: client connected from 7994[0:0]
Feb  1 21:08:43 joe acpid: 1 client rule loaded
Feb  1 21:08:43 joe acpid: client connected from 7990[0:0]
Feb  1 21:08:43 joe acpid: 1 client rule loaded
Feb  1 21:08:43 joe acpid: client connected from 7989[0:0]
Feb  1 21:08:43 joe acpid: 1 client rule loaded
Feb  1 21:08:43 joe acpid: client 7994[0:0] has disconnected
Feb  1 21:08:43 joe acpid: client 7990[0:0] has disconnected
Feb  1 21:08:43 joe pulseaudio[8037]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:43 joe acpid: client 7989[0:0] has disconnected
Feb  1 21:08:43 joe acpid: client connected from 7991[0:0]
Feb  1 21:08:43 joe acpid: 1 client rule loaded
Feb  1 21:08:43 joe acpid: client 7991[0:0] has disconnected
Feb  1 21:08:43 joe acpid: client connected from 7995[0:0]
Feb  1 21:08:43 joe acpid: 1 client rule loaded
Feb  1 21:08:43 joe acpid: client 7995[0:0] has disconnected
Feb  1 21:08:43 joe acpid: client connected from 7993[0:0]
Feb  1 21:08:43 joe acpid: 1 client rule loaded
Feb  1 21:08:43 joe acpid: client 7993[0:0] has disconnected
Feb  1 21:08:43 joe acpid: client connected from 7992[0:0]
Feb  1 21:08:43 joe acpid: 1 client rule loaded
Feb  1 21:08:43 joe acpid: client 7992[0:0] has disconnected
Feb  1 21:08:43 joe acpid: client connected from 7988[0:0]
Feb  1 21:08:43 joe acpid: 1 client rule loaded
Feb  1 21:08:43 joe acpid: client 7988[0:0] has disconnected
Feb  1 21:08:45 joe pulseaudio[8142]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:48 joe pulseaudio[8242]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:50 joe pulseaudio[8280]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:53 joe pulseaudio[8384]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:55 joe pulseaudio[8454]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:08:58 joe acpid: client connected from 8502[0:0]
Feb  1 21:08:58 joe acpid: 1 client rule loaded
Feb  1 21:08:58 joe acpid: client connected from 8503[0:0]
Feb  1 21:08:58 joe acpid: 1 client rule loaded
Feb  1 21:08:58 joe acpid: client connected from 8505[0:0]
Feb  1 21:08:58 joe acpid: 1 client rule loaded
Feb  1 21:08:58 joe acpid: client 8502[0:0] has disconnected
Feb  1 21:08:58 joe acpid: client 8503[0:0] has disconnected
Feb  1 21:08:58 joe acpid: client 8505[0:0] has disconnected
Feb  1 21:08:58 joe acpid: client connected from 8500[0:0]
Feb  1 21:08:58 joe acpid: 1 client rule loaded
Feb  1 21:08:58 joe acpid: client 8500[0:0] has disconnected
Feb  1 21:08:58 joe acpid: client connected from 8501[0:0]
Feb  1 21:08:58 joe acpid: 1 client rule loaded
Feb  1 21:08:58 joe acpid: client 8501[0:0] has disconnected
Feb  1 21:08:58 joe acpid: client connected from 8504[0:0]
Feb  1 21:08:58 joe acpid: 1 client rule loaded
Feb  1 21:08:58 joe acpid: client 8504[0:0] has disconnected
Feb  1 21:08:58 joe pulseaudio[8566]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:00 joe pulseaudio[8636]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:02 joe /USR/SBIN/CRON[8671]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \; -delete)
Feb  1 21:09:04 joe pulseaudio[8713]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:05 joe pulseaudio[8752]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:08 joe pulseaudio[8845]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:10 joe pulseaudio[8915]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:14 joe acpid: client connected from 9016[0:0]
Feb  1 21:09:14 joe acpid: 1 client rule loaded
Feb  1 21:09:14 joe acpid: client connected from 9015[0:0]
Feb  1 21:09:14 joe acpid: 1 client rule loaded
Feb  1 21:09:14 joe acpid: client connected from 9020[0:0]
Feb  1 21:09:14 joe acpid: 1 client rule loaded
Feb  1 21:09:14 joe acpid: client connected from 9018[0:0]
Feb  1 21:09:14 joe acpid: 1 client rule loaded
Feb  1 21:09:14 joe acpid: client connected from 9017[0:0]
Feb  1 21:09:14 joe acpid: 1 client rule loaded
Feb  1 21:09:14 joe pulseaudio[9039]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:14 joe acpid: client 9016[0:0] has disconnected
Feb  1 21:09:14 joe acpid: client 9015[0:0] has disconnected
Feb  1 21:09:14 joe acpid: client 9020[0:0] has disconnected
Feb  1 21:09:14 joe acpid: client 9018[0:0] has disconnected
Feb  1 21:09:14 joe acpid: client 9017[0:0] has disconnected
Feb  1 21:09:14 joe acpid: client connected from 9028[0:0]
Feb  1 21:09:14 joe acpid: 1 client rule loaded
Feb  1 21:09:14 joe acpid: client 9028[0:0] has disconnected
Feb  1 21:09:14 joe acpid: client connected from 9026[0:0]
Feb  1 21:09:14 joe acpid: 1 client rule loaded
Feb  1 21:09:14 joe acpid: client 9026[0:0] has disconnected
Feb  1 21:09:14 joe acpid: client connected from 9027[0:0]
Feb  1 21:09:14 joe acpid: 1 client rule loaded
Feb  1 21:09:14 joe acpid: client 9027[0:0] has disconnected
Feb  1 21:09:14 joe acpid: client connected from 9030[0:0]
Feb  1 21:09:14 joe acpid: 1 client rule loaded
Feb  1 21:09:14 joe acpid: client 9030[0:0] has disconnected
Feb  1 21:09:14 joe acpid: client connected from 9029[0:0]
Feb  1 21:09:14 joe acpid: 1 client rule loaded
Feb  1 21:09:14 joe acpid: client 9029[0:0] has disconnected
Feb  1 21:09:15 joe pulseaudio[9107]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:19 joe pulseaudio[9249]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:20 joe pulseaudio[9284]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:24 joe pulseaudio[9426]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:25 joe pulseaudio[9461]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:27 joe acpid: client connected from 9524[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client connected from 9517[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client connected from 9525[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client connected from 9521[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client connected from 9519[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client connected from 9515[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client connected from 9520[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client connected from 9518[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client connected from 9526[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client connected from 9522[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client connected from 9516[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client connected from 9537[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client connected from 9538[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client 9524[0:0] has disconnected
Feb  1 21:09:27 joe acpid: client 9517[0:0] has disconnected
Feb  1 21:09:27 joe acpid: client 9525[0:0] has disconnected
Feb  1 21:09:27 joe acpid: client 9521[0:0] has disconnected
Feb  1 21:09:27 joe acpid: client 9519[0:0] has disconnected
Feb  1 21:09:27 joe acpid: client 9515[0:0] has disconnected
Feb  1 21:09:27 joe acpid: client 9520[0:0] has disconnected
Feb  1 21:09:27 joe acpid: client 9518[0:0] has disconnected
Feb  1 21:09:27 joe acpid: client 9526[0:0] has disconnected
Feb  1 21:09:27 joe acpid: client 9522[0:0] has disconnected
Feb  1 21:09:27 joe acpid: client 9516[0:0] has disconnected
Feb  1 21:09:27 joe acpid: client connected from 9545[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client 9537[0:0] has disconnected
Feb  1 21:09:27 joe acpid: client 9538[0:0] has disconnected
Feb  1 21:09:27 joe acpid: client connected from 9544[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client connected from 9543[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client connected from 9542[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:27 joe acpid: client connected from 9550[0:0]
Feb  1 21:09:27 joe acpid: 1 client rule loaded
Feb  1 21:09:29 joe acpid: client 9545[0:0] has disconnected
Feb  1 21:09:29 joe acpid: client 9544[0:0] has disconnected
Feb  1 21:09:29 joe acpid: client 9543[0:0] has disconnected
Feb  1 21:09:29 joe acpid: client 9542[0:0] has disconnected
Feb  1 21:09:29 joe acpid: client 9550[0:0] has disconnected
Feb  1 21:09:30 joe pulseaudio[9627]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:30 joe pulseaudio[9656]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:34 joe pulseaudio[9769]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:35 joe pulseaudio[9804]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:40 joe pulseaudio[9947]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:40 joe pulseaudio[9983]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:42 joe acpid: client connected from 10031[0:0]
Feb  1 21:09:42 joe acpid: 1 client rule loaded
Feb  1 21:09:42 joe acpid: client connected from 10034[0:0]
Feb  1 21:09:42 joe acpid: 1 client rule loaded
Feb  1 21:09:42 joe acpid: client connected from 10032[0:0]
Feb  1 21:09:42 joe acpid: 1 client rule loaded
Feb  1 21:09:42 joe acpid: client connected from 10029[0:0]
Feb  1 21:09:42 joe acpid: 1 client rule loaded
Feb  1 21:09:42 joe acpid: client connected from 10040[0:0]
Feb  1 21:09:42 joe acpid: 1 client rule loaded
Feb  1 21:09:42 joe acpid: client connected from 10039[0:0]
Feb  1 21:09:42 joe acpid: 1 client rule loaded
Feb  1 21:09:42 joe acpid: client connected from 10030[0:0]
Feb  1 21:09:42 joe acpid: 1 client rule loaded
Feb  1 21:09:42 joe acpid: client connected from 10036[0:0]
Feb  1 21:09:42 joe acpid: 1 client rule loaded
Feb  1 21:09:42 joe acpid: client connected from 10042[0:0]
Feb  1 21:09:42 joe acpid: 1 client rule loaded
Feb  1 21:09:42 joe acpid: client connected from 10043[0:0]
Feb  1 21:09:42 joe acpid: 1 client rule loaded
Feb  1 21:09:42 joe acpid: client 10031[0:0] has disconnected
Feb  1 21:09:42 joe acpid: client 10034[0:0] has disconnected
Feb  1 21:09:42 joe acpid: client 10032[0:0] has disconnected
Feb  1 21:09:42 joe acpid: client 10029[0:0] has disconnected
Feb  1 21:09:42 joe acpid: client 10040[0:0] has disconnected
Feb  1 21:09:42 joe acpid: client 10039[0:0] has disconnected
Feb  1 21:09:42 joe acpid: client 10030[0:0] has disconnected
Feb  1 21:09:42 joe acpid: client 10036[0:0] has disconnected
Feb  1 21:09:42 joe acpid: client 10042[0:0] has disconnected
Feb  1 21:09:42 joe acpid: client 10043[0:0] has disconnected
Feb  1 21:09:46 joe pulseaudio[10131]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:46 joe pulseaudio[10146]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:51 joe pulseaudio[10257]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:51 joe pulseaudio[10255]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:56 joe pulseaudio[10435]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:56 joe pulseaudio[10436]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:09:58 joe acpid: client connected from 10529[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10535[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10532[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10530[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10537[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10533[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10546[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10542[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10554[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10543[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10552[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10551[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10549[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10555[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10553[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10541[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10548[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client 10529[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client connected from 10547[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client 10535[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client 10532[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client 10530[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client 10537[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client 10533[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client 10546[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client 10542[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client 10554[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client 10543[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client 10552[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client 10551[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client 10549[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client 10555[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client 10553[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client 10541[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client 10548[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client 10547[0:0] has disconnected
Feb  1 21:09:58 joe acpid: client connected from 10568[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10572[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:58 joe acpid: client connected from 10567[0:0]
Feb  1 21:09:58 joe acpid: 1 client rule loaded
Feb  1 21:09:59 joe acpid: client connected from 10586[0:0]
Feb  1 21:09:59 joe acpid: 1 client rule loaded
Feb  1 21:09:59 joe acpid: client connected from 10573[0:0]
Feb  1 21:09:59 joe acpid: 1 client rule loaded
Feb  1 21:09:59 joe acpid: client connected from 10580[0:0]
Feb  1 21:09:59 joe acpid: 1 client rule loaded
Feb  1 21:09:59 joe acpid: client connected from 10589[0:0]
Feb  1 21:09:59 joe acpid: 1 client rule loaded
Feb  1 21:09:59 joe acpid: client connected from 10574[0:0]
Feb  1 21:09:59 joe acpid: 1 client rule loaded
Feb  1 21:09:59 joe acpid: client connected from 10582[0:0]
Feb  1 21:09:59 joe acpid: 1 client rule loaded
Feb  1 21:09:59 joe acpid: client connected from 10588[0:0]
Feb  1 21:09:59 joe acpid: 1 client rule loaded
Feb  1 21:09:59 joe acpid: client connected from 10585[0:0]
Feb  1 21:09:59 joe acpid: 1 client rule loaded
Feb  1 21:09:59 joe acpid: client connected from 10577[0:0]
Feb  1 21:09:59 joe acpid: 1 client rule loaded
Feb  1 21:09:59 joe acpid: client connected from 10587[0:0]
Feb  1 21:09:59 joe acpid: 1 client rule loaded
Feb  1 21:09:59 joe acpid: client connected from 10570[0:0]
Feb  1 21:09:59 joe acpid: 1 client rule loaded
Feb  1 21:09:59 joe acpid: client connected from 10581[0:0]
Feb  1 21:09:59 joe acpid: 1 client rule loaded
Feb  1 21:09:59 joe acpid: client connected from 10590[0:0]
Feb  1 21:09:59 joe acpid: 1 client rule loaded
Feb  1 21:09:59 joe acpid: client connected from 10571[0:0]
Feb  1 21:09:59 joe acpid: 1 client rule loaded
Feb  1 21:09:59 joe acpid: client connected from 10584[0:0]
Feb  1 21:09:59 joe acpid: 1 client rule loaded
Feb  1 21:10:04 joe pulseaudio[10662]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:04 joe pulseaudio[10661]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:07 joe pulseaudio[10869]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:07 joe pulseaudio[10871]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:12 joe pulseaudio[11041]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:12 joe pulseaudio[11042]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:12 joe acpid: client 10568[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10572[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10567[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10586[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10573[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10580[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10589[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10574[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10582[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10588[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10585[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10577[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10587[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10570[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10581[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10590[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10571[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client 10584[0:0] has disconnected
Feb  1 21:10:12 joe acpid: client connected from 11043[0:0]
Feb  1 21:10:12 joe acpid: 1 client rule loaded
Feb  1 21:10:12 joe acpid: client connected from 11046[0:0]
Feb  1 21:10:12 joe acpid: 1 client rule loaded
Feb  1 21:10:12 joe acpid: client connected from 11047[0:0]
Feb  1 21:10:12 joe acpid: 1 client rule loaded
Feb  1 21:10:12 joe acpid: client connected from 11044[0:0]
Feb  1 21:10:12 joe acpid: 1 client rule loaded
Feb  1 21:10:12 joe acpid: client connected from 11048[0:0]
Feb  1 21:10:12 joe acpid: 1 client rule loaded
Feb  1 21:10:12 joe acpid: client connected from 11045[0:0]
Feb  1 21:10:12 joe acpid: 1 client rule loaded
Feb  1 21:10:17 joe pulseaudio[11223]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:17 joe pulseaudio[11225]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:22 joe pulseaudio[11334]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:22 joe pulseaudio[11336]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:27 joe pulseaudio[11484]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:27 joe pulseaudio[11483]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:32 joe acpid: client 11043[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client 11046[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client 11047[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client 11044[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client 11048[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client 11045[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client connected from 11557[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client 11557[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client connected from 11558[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client 11558[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client connected from 11560[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client 11560[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client connected from 11559[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client 11559[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client connected from 11567[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client 11567[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client connected from 11563[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client 11563[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client connected from 11566[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client 11566[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client connected from 11561[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client 11561[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client connected from 11575[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client 11575[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client connected from 11569[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client 11569[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client connected from 11583[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client 11583[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client connected from 11571[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client 11571[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client connected from 11579[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client 11579[0:0] has disconnected
Feb  1 21:10:32 joe acpid: client connected from 11586[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client connected from 11585[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client connected from 11572[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client connected from 11584[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client connected from 11573[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client connected from 11574[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client connected from 11581[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client connected from 11578[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client connected from 11580[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client connected from 11577[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client connected from 11604[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe acpid: client connected from 11605[0:0]
Feb  1 21:10:32 joe acpid: 1 client rule loaded
Feb  1 21:10:32 joe pulseaudio[11661]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:32 joe pulseaudio[11663]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:37 joe pulseaudio[11833]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:37 joe pulseaudio[11836]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:38 joe acpid: client 11586[0:0] has disconnected
Feb  1 21:10:38 joe acpid: client 11585[0:0] has disconnected
Feb  1 21:10:38 joe acpid: client 11572[0:0] has disconnected
Feb  1 21:10:38 joe acpid: client 11584[0:0] has disconnected
Feb  1 21:10:38 joe acpid: client 11573[0:0] has disconnected
Feb  1 21:10:38 joe acpid: client 11574[0:0] has disconnected
Feb  1 21:10:38 joe acpid: client 11581[0:0] has disconnected
Feb  1 21:10:38 joe acpid: client 11578[0:0] has disconnected
Feb  1 21:10:38 joe acpid: client 11580[0:0] has disconnected
Feb  1 21:10:38 joe acpid: client 11577[0:0] has disconnected
Feb  1 21:10:38 joe acpid: client 11604[0:0] has disconnected
Feb  1 21:10:38 joe acpid: client 11605[0:0] has disconnected
Feb  1 21:10:42 joe pulseaudio[11999]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:42 joe pulseaudio[12001]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:44 joe acpid: client connected from 12054[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12055[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12059[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12053[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12058[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12068[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12067[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12063[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12070[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12061[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12066[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12065[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12062[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12069[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12057[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12056[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client 12054[0:0] has disconnected
Feb  1 21:10:44 joe acpid: client 12055[0:0] has disconnected
Feb  1 21:10:44 joe acpid: client 12059[0:0] has disconnected
Feb  1 21:10:44 joe acpid: client 12053[0:0] has disconnected
Feb  1 21:10:44 joe acpid: client 12058[0:0] has disconnected
Feb  1 21:10:44 joe acpid: client 12067[0:0] has disconnected
Feb  1 21:10:44 joe acpid: client 12063[0:0] has disconnected
Feb  1 21:10:44 joe acpid: client 12070[0:0] has disconnected
Feb  1 21:10:44 joe acpid: client 12061[0:0] has disconnected
Feb  1 21:10:44 joe acpid: client 12066[0:0] has disconnected
Feb  1 21:10:44 joe acpid: client 12069[0:0] has disconnected
Feb  1 21:10:44 joe acpid: client 12057[0:0] has disconnected
Feb  1 21:10:44 joe acpid: client connected from 12101[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client 12062[0:0] has disconnected
Feb  1 21:10:44 joe acpid: client connected from 12093[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client 12068[0:0] has disconnected
Feb  1 21:10:44 joe acpid: client connected from 12094[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client 12065[0:0] has disconnected
Feb  1 21:10:44 joe acpid: client 12056[0:0] has disconnected
Feb  1 21:10:44 joe acpid: client connected from 12095[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12096[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12097[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12099[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12103[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12102[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12100[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12092[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12091[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client connected from 12098[0:0]
Feb  1 21:10:44 joe acpid: 1 client rule loaded
Feb  1 21:10:44 joe acpid: client 12101[0:0] has disconnected
Feb  1 21:10:48 joe acpid: client 12093[0:0] has disconnected
Feb  1 21:10:48 joe acpid: client 12094[0:0] has disconnected
Feb  1 21:10:48 joe acpid: client 12095[0:0] has disconnected
Feb  1 21:10:48 joe acpid: client 12096[0:0] has disconnected
Feb  1 21:10:48 joe acpid: client 12097[0:0] has disconnected
Feb  1 21:10:48 joe acpid: client 12099[0:0] has disconnected
Feb  1 21:10:48 joe acpid: client 12103[0:0] has disconnected
Feb  1 21:10:48 joe acpid: client 12102[0:0] has disconnected
Feb  1 21:10:48 joe acpid: client 12100[0:0] has disconnected
Feb  1 21:10:48 joe pulseaudio[12213]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:48 joe pulseaudio[12215]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:48 joe acpid: client 12092[0:0] has disconnected
Feb  1 21:10:48 joe acpid: client 12091[0:0] has disconnected
Feb  1 21:10:48 joe acpid: client 12098[0:0] has disconnected
Feb  1 21:10:54 joe pulseaudio[12424]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:10:54 joe pulseaudio[12422]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:00 joe acpid: client connected from 12586[0:0]
Feb  1 21:11:00 joe acpid: 1 client rule loaded
Feb  1 21:11:00 joe acpid: client connected from 12587[0:0]
Feb  1 21:11:00 joe acpid: 1 client rule loaded
Feb  1 21:11:00 joe acpid: client connected from 12591[0:0]
Feb  1 21:11:00 joe acpid: 1 client rule loaded
Feb  1 21:11:00 joe pulseaudio[12600]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:00 joe pulseaudio[12601]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:00 joe acpid: client 12586[0:0] has disconnected
Feb  1 21:11:00 joe acpid: client 12587[0:0] has disconnected
Feb  1 21:11:00 joe acpid: client 12591[0:0] has disconnected
Feb  1 21:11:00 joe acpid: client connected from 12588[0:0]
Feb  1 21:11:00 joe acpid: 1 client rule loaded
Feb  1 21:11:00 joe acpid: client 12588[0:0] has disconnected
Feb  1 21:11:00 joe acpid: client connected from 12590[0:0]
Feb  1 21:11:00 joe acpid: 1 client rule loaded
Feb  1 21:11:00 joe acpid: client 12590[0:0] has disconnected
Feb  1 21:11:00 joe acpid: client connected from 12589[0:0]
Feb  1 21:11:00 joe acpid: 1 client rule loaded
Feb  1 21:11:05 joe pulseaudio[12804]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:05 joe pulseaudio[12826]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:10 joe pulseaudio[12921]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:10 joe pulseaudio[12955]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:10 joe acpid: client 12589[0:0] has disconnected
Feb  1 21:11:15 joe pulseaudio[13094]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:15 joe acpid: client connected from 13102[0:0]
Feb  1 21:11:15 joe acpid: 1 client rule loaded
Feb  1 21:11:15 joe acpid: client connected from 13103[0:0]
Feb  1 21:11:15 joe acpid: 1 client rule loaded
Feb  1 21:11:15 joe acpid: client 13102[0:0] has disconnected
Feb  1 21:11:15 joe acpid: client 13103[0:0] has disconnected
Feb  1 21:11:15 joe acpid: client connected from 13106[0:0]
Feb  1 21:11:15 joe acpid: 1 client rule loaded
Feb  1 21:11:15 joe acpid: client connected from 13108[0:0]
Feb  1 21:11:15 joe acpid: 1 client rule loaded
Feb  1 21:11:15 joe acpid: client connected from 13107[0:0]
Feb  1 21:11:15 joe acpid: 1 client rule loaded
Feb  1 21:11:15 joe pulseaudio[13126]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:18 joe acpid: client 13106[0:0] has disconnected
Feb  1 21:11:18 joe acpid: client 13108[0:0] has disconnected
Feb  1 21:11:18 joe acpid: client 13107[0:0] has disconnected
Feb  1 21:11:20 joe pulseaudio[13264]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:20 joe pulseaudio[13298]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:25 joe pulseaudio[13411]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:25 joe pulseaudio[13444]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:31 joe pulseaudio[13585]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:31 joe pulseaudio[13616]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:31 joe acpid: client connected from 13617[0:0]
Feb  1 21:11:31 joe acpid: 1 client rule loaded
Feb  1 21:11:31 joe acpid: client connected from 13625[0:0]
Feb  1 21:11:31 joe acpid: 1 client rule loaded
Feb  1 21:11:31 joe acpid: client connected from 13618[0:0]
Feb  1 21:11:31 joe acpid: 1 client rule loaded
Feb  1 21:11:31 joe acpid: client connected from 13619[0:0]
Feb  1 21:11:31 joe acpid: 1 client rule loaded
Feb  1 21:11:31 joe acpid: client connected from 13624[0:0]
Feb  1 21:11:31 joe acpid: 1 client rule loaded
Feb  1 21:11:33 joe acpid: client 13617[0:0] has disconnected
Feb  1 21:11:33 joe acpid: client 13625[0:0] has disconnected
Feb  1 21:11:33 joe acpid: client 13618[0:0] has disconnected
Feb  1 21:11:33 joe acpid: client 13619[0:0] has disconnected
Feb  1 21:11:33 joe acpid: client 13624[0:0] has disconnected
Feb  1 21:11:36 joe pulseaudio[13755]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:36 joe pulseaudio[13786]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:42 joe pulseaudio[13956]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:42 joe pulseaudio[13955]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:46 joe pulseaudio[14061]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:46 joe pulseaudio[14094]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:47 joe acpid: client connected from 14128[0:0]
Feb  1 21:11:47 joe acpid: 1 client rule loaded
Feb  1 21:11:47 joe acpid: client connected from 14120[0:0]
Feb  1 21:11:47 joe acpid: 1 client rule loaded
Feb  1 21:11:47 joe acpid: client connected from 14125[0:0]
Feb  1 21:11:47 joe acpid: 1 client rule loaded
Feb  1 21:11:47 joe acpid: client connected from 14130[0:0]
Feb  1 21:11:47 joe acpid: 1 client rule loaded
Feb  1 21:11:47 joe acpid: client connected from 14121[0:0]
Feb  1 21:11:47 joe acpid: 1 client rule loaded
Feb  1 21:11:47 joe acpid: client connected from 14124[0:0]
Feb  1 21:11:47 joe acpid: 1 client rule loaded
Feb  1 21:11:47 joe acpid: client connected from 14122[0:0]
Feb  1 21:11:47 joe acpid: 1 client rule loaded
Feb  1 21:11:47 joe acpid: client connected from 14123[0:0]
Feb  1 21:11:47 joe acpid: 1 client rule loaded
Feb  1 21:11:48 joe acpid: client 14128[0:0] has disconnected
Feb  1 21:11:48 joe acpid: client 14120[0:0] has disconnected
Feb  1 21:11:48 joe acpid: client 14125[0:0] has disconnected
Feb  1 21:11:48 joe acpid: client 14130[0:0] has disconnected
Feb  1 21:11:48 joe acpid: client 14121[0:0] has disconnected
Feb  1 21:11:48 joe acpid: client 14124[0:0] has disconnected
Feb  1 21:11:48 joe acpid: client 14122[0:0] has disconnected
Feb  1 21:11:48 joe acpid: client 14123[0:0] has disconnected
Feb  1 21:11:52 joe pulseaudio[14237]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:52 joe pulseaudio[14269]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:55 joe pulseaudio[14397]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:11:58 joe pulseaudio[14441]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:00 joe pulseaudio[14517]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:02 joe pulseaudio[14559]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:04 joe acpid: client connected from 14630[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14629[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14640[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14634[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14635[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14633[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14646[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14649[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14642[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14645[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14638[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14628[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14639[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14652[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14651[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14648[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14644[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client 14630[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client 14629[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client 14640[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client 14634[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client 14635[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client 14633[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client 14646[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client 14649[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client 14642[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client 14645[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client 14638[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client 14628[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client 14639[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client 14652[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client 14651[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client 14648[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client 14644[0:0] has disconnected
Feb  1 21:12:04 joe acpid: client connected from 14669[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14664[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14666[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14668[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14671[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14672[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14674[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14667[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14677[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:04 joe acpid: client connected from 14676[0:0]
Feb  1 21:12:04 joe acpid: 1 client rule loaded
Feb  1 21:12:05 joe pulseaudio[14724]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:09 joe pulseaudio[14765]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:10 joe pulseaudio[14836]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:12 joe acpid: client 14669[0:0] has disconnected
Feb  1 21:12:12 joe acpid: client 14664[0:0] has disconnected
Feb  1 21:12:12 joe acpid: client 14666[0:0] has disconnected
Feb  1 21:12:12 joe acpid: client 14668[0:0] has disconnected
Feb  1 21:12:12 joe acpid: client 14671[0:0] has disconnected
Feb  1 21:12:12 joe acpid: client 14672[0:0] has disconnected
Feb  1 21:12:12 joe acpid: client 14674[0:0] has disconnected
Feb  1 21:12:12 joe acpid: client 14667[0:0] has disconnected
Feb  1 21:12:12 joe acpid: client 14677[0:0] has disconnected
Feb  1 21:12:12 joe acpid: client 14676[0:0] has disconnected
Feb  1 21:12:14 joe pulseaudio[14900]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:15 joe pulseaudio[14965]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:19 joe pulseaudio[15069]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:20 joe pulseaudio[15104]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:21 joe acpid: client connected from 15133[0:0]
Feb  1 21:12:21 joe acpid: 1 client rule loaded
Feb  1 21:12:21 joe acpid: client connected from 15134[0:0]
Feb  1 21:12:21 joe acpid: 1 client rule loaded
Feb  1 21:12:21 joe acpid: client connected from 15139[0:0]
Feb  1 21:12:21 joe acpid: 1 client rule loaded
Feb  1 21:12:21 joe acpid: client connected from 15137[0:0]
Feb  1 21:12:21 joe acpid: 1 client rule loaded
Feb  1 21:12:21 joe acpid: client connected from 15138[0:0]
Feb  1 21:12:21 joe acpid: 1 client rule loaded
Feb  1 21:12:21 joe acpid: client connected from 15136[0:0]
Feb  1 21:12:21 joe acpid: 1 client rule loaded
Feb  1 21:12:21 joe acpid: client connected from 15135[0:0]
Feb  1 21:12:21 joe acpid: 1 client rule loaded
Feb  1 21:12:23 joe pulseaudio[15199]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:25 joe pulseaudio[15273]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:26 joe acpid: client 15133[0:0] has disconnected
Feb  1 21:12:26 joe acpid: client 15134[0:0] has disconnected
Feb  1 21:12:26 joe acpid: client 15139[0:0] has disconnected
Feb  1 21:12:26 joe acpid: client 15137[0:0] has disconnected
Feb  1 21:12:26 joe acpid: client 15138[0:0] has disconnected
Feb  1 21:12:26 joe acpid: client 15136[0:0] has disconnected
Feb  1 21:12:26 joe acpid: client 15135[0:0] has disconnected
Feb  1 21:12:28 joe pulseaudio[15369]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:30 joe pulseaudio[15441]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:33 joe pulseaudio[15529]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:35 joe pulseaudio[15592]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:37 joe acpid: client connected from 15656[0:0]
Feb  1 21:12:37 joe acpid: 1 client rule loaded
Feb  1 21:12:37 joe acpid: client connected from 15657[0:0]
Feb  1 21:12:37 joe acpid: 1 client rule loaded
Feb  1 21:12:37 joe acpid: client connected from 15661[0:0]
Feb  1 21:12:37 joe acpid: 1 client rule loaded
Feb  1 21:12:37 joe acpid: client connected from 15659[0:0]
Feb  1 21:12:37 joe acpid: 1 client rule loaded
Feb  1 21:12:37 joe acpid: client connected from 15665[0:0]
Feb  1 21:12:37 joe acpid: 1 client rule loaded
Feb  1 21:12:37 joe acpid: client connected from 15655[0:0]
Feb  1 21:12:37 joe acpid: 1 client rule loaded
Feb  1 21:12:37 joe acpid: client connected from 15667[0:0]
Feb  1 21:12:37 joe acpid: 1 client rule loaded
Feb  1 21:12:37 joe acpid: client connected from 15677[0:0]
Feb  1 21:12:37 joe acpid: 1 client rule loaded
Feb  1 21:12:37 joe acpid: client connected from 15654[0:0]
Feb  1 21:12:37 joe acpid: 1 client rule loaded
Feb  1 21:12:37 joe acpid: client connected from 15694[0:0]
Feb  1 21:12:37 joe acpid: 1 client rule loaded
Feb  1 21:12:37 joe acpid: client connected from 15670[0:0]
Feb  1 21:12:37 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15697[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15669[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15675[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15704[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15674[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15668[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15671[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15676[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15679[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15672[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15678[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15680[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15695[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15699[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15696[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15700[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client 15656[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15657[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15661[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15659[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15665[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15655[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15667[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15677[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15654[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15697[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15669[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15675[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15704[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15674[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15671[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15676[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15672[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15678[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15680[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15670[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15668[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15679[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15699[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15696[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client connected from 15715[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client 15694[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15695[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client 15700[0:0] has disconnected
Feb  1 21:12:38 joe acpid: client connected from 15718[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15717[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15716[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15714[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe acpid: client connected from 15724[0:0]
Feb  1 21:12:38 joe acpid: 1 client rule loaded
Feb  1 21:12:38 joe pulseaudio[15736]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:42 joe acpid: client 15715[0:0] has disconnected
Feb  1 21:12:42 joe acpid: client 15718[0:0] has disconnected
Feb  1 21:12:42 joe acpid: client 15717[0:0] has disconnected
Feb  1 21:12:42 joe acpid: client 15716[0:0] has disconnected
Feb  1 21:12:42 joe acpid: client 15714[0:0] has disconnected
Feb  1 21:12:42 joe acpid: client 15724[0:0] has disconnected
Feb  1 21:12:42 joe pulseaudio[15802]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:43 joe pulseaudio[15886]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:46 joe pulseaudio[15981]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:49 joe pulseaudio[16051]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:51 joe pulseaudio[16146]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:52 joe acpid: client connected from 16162[0:0]
Feb  1 21:12:52 joe acpid: 1 client rule loaded
Feb  1 21:12:52 joe acpid: client 16162[0:0] has disconnected
Feb  1 21:12:52 joe acpid: client connected from 16165[0:0]
Feb  1 21:12:52 joe acpid: 1 client rule loaded
Feb  1 21:12:52 joe acpid: client connected from 16173[0:0]
Feb  1 21:12:52 joe acpid: 1 client rule loaded
Feb  1 21:12:52 joe acpid: client connected from 16169[0:0]
Feb  1 21:12:52 joe acpid: 1 client rule loaded
Feb  1 21:12:52 joe acpid: client connected from 16180[0:0]
Feb  1 21:12:52 joe acpid: 1 client rule loaded
Feb  1 21:12:52 joe acpid: client connected from 16166[0:0]
Feb  1 21:12:52 joe acpid: 1 client rule loaded
Feb  1 21:12:52 joe acpid: client connected from 16177[0:0]
Feb  1 21:12:52 joe acpid: 1 client rule loaded
Feb  1 21:12:52 joe acpid: client connected from 16179[0:0]
Feb  1 21:12:52 joe acpid: 1 client rule loaded
Feb  1 21:12:52 joe acpid: client connected from 16171[0:0]
Feb  1 21:12:52 joe acpid: 1 client rule loaded
Feb  1 21:12:52 joe acpid: client connected from 16170[0:0]
Feb  1 21:12:52 joe acpid: 1 client rule loaded
Feb  1 21:12:52 joe acpid: client connected from 16168[0:0]
Feb  1 21:12:52 joe acpid: 1 client rule loaded
Feb  1 21:12:52 joe acpid: client connected from 16178[0:0]
Feb  1 21:12:52 joe acpid: 1 client rule loaded
Feb  1 21:12:52 joe acpid: client connected from 16174[0:0]
Feb  1 21:12:52 joe acpid: 1 client rule loaded
Feb  1 21:12:52 joe acpid: client connected from 16167[0:0]
Feb  1 21:12:52 joe acpid: 1 client rule loaded
Feb  1 21:12:55 joe acpid: client 16165[0:0] has disconnected
Feb  1 21:12:55 joe acpid: client 16173[0:0] has disconnected
Feb  1 21:12:55 joe acpid: client 16169[0:0] has disconnected
Feb  1 21:12:55 joe acpid: client 16180[0:0] has disconnected
Feb  1 21:12:55 joe acpid: client 16166[0:0] has disconnected
Feb  1 21:12:55 joe acpid: client 16177[0:0] has disconnected
Feb  1 21:12:55 joe acpid: client 16171[0:0] has disconnected
Feb  1 21:12:55 joe acpid: client 16168[0:0] has disconnected
Feb  1 21:12:55 joe pulseaudio[16235]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:12:55 joe acpid: client 16178[0:0] has disconnected
Feb  1 21:12:55 joe acpid: client 16174[0:0] has disconnected
Feb  1 21:12:55 joe acpid: client 16167[0:0] has disconnected
Feb  1 21:12:55 joe acpid: client 16179[0:0] has disconnected
Feb  1 21:12:55 joe acpid: client 16170[0:0] has disconnected
Feb  1 21:12:56 joe pulseaudio[16307]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:02 joe pulseaudio[16441]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:02 joe pulseaudio[16473]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:07 joe pulseaudio[16601]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:07 joe pulseaudio[16603]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:09 joe acpid: client connected from 16677[0:0]
Feb  1 21:13:09 joe acpid: 1 client rule loaded
Feb  1 21:13:09 joe acpid: client connected from 16678[0:0]
Feb  1 21:13:09 joe acpid: 1 client rule loaded
Feb  1 21:13:09 joe acpid: client connected from 16680[0:0]
Feb  1 21:13:09 joe acpid: 1 client rule loaded
Feb  1 21:13:09 joe acpid: client connected from 16684[0:0]
Feb  1 21:13:09 joe acpid: 1 client rule loaded
Feb  1 21:13:09 joe acpid: client connected from 16682[0:0]
Feb  1 21:13:09 joe acpid: 1 client rule loaded
Feb  1 21:13:09 joe acpid: client connected from 16679[0:0]
Feb  1 21:13:09 joe acpid: 1 client rule loaded
Feb  1 21:13:09 joe acpid: client connected from 16681[0:0]
Feb  1 21:13:09 joe acpid: 1 client rule loaded
Feb  1 21:13:09 joe acpid: client connected from 16691[0:0]
Feb  1 21:13:09 joe acpid: 1 client rule loaded
Feb  1 21:13:09 joe acpid: client connected from 16688[0:0]
Feb  1 21:13:09 joe acpid: 1 client rule loaded
Feb  1 21:13:09 joe acpid: client connected from 16687[0:0]
Feb  1 21:13:09 joe acpid: 1 client rule loaded
Feb  1 21:13:09 joe acpid: client connected from 16690[0:0]
Feb  1 21:13:09 joe acpid: 1 client rule loaded
Feb  1 21:13:09 joe acpid: client 16677[0:0] has disconnected
Feb  1 21:13:09 joe acpid: client 16678[0:0] has disconnected
Feb  1 21:13:09 joe acpid: client 16680[0:0] has disconnected
Feb  1 21:13:09 joe acpid: client 16684[0:0] has disconnected
Feb  1 21:13:09 joe acpid: client 16682[0:0] has disconnected
Feb  1 21:13:09 joe acpid: client 16679[0:0] has disconnected
Feb  1 21:13:09 joe acpid: client 16681[0:0] has disconnected
Feb  1 21:13:09 joe acpid: client 16691[0:0] has disconnected
Feb  1 21:13:09 joe acpid: client 16688[0:0] has disconnected
Feb  1 21:13:09 joe acpid: client 16687[0:0] has disconnected
Feb  1 21:13:09 joe acpid: client 16690[0:0] has disconnected
Feb  1 21:13:13 joe pulseaudio[16773]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:13 joe pulseaudio[16774]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:16 joe pulseaudio[16886]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:16 joe pulseaudio[16885]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:21 joe pulseaudio[17049]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:21 joe pulseaudio[17050]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:25 joe acpid: client connected from 17184[0:0]
Feb  1 21:13:25 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17188[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17190[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17185[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17191[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17187[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17217[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17203[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17189[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17209[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17235[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17201[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17211[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17237[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17204[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17238[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17239[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17236[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17202[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client 17184[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client connected from 17197[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17216[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17200[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17199[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17212[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17196[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17214[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17208[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17213[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17206[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17234[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client 17188[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client connected from 17207[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client 17190[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17203[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client connected from 17240[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client 17185[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17191[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17187[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17217[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17189[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17209[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17235[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17201[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17211[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17237[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17204[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17238[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17239[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17236[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17202[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17197[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17216[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17200[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17199[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17212[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17196[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17214[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17208[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17213[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17206[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17234[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client 17207[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client connected from 17249[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17252[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17251[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client 17240[0:0] has disconnected
Feb  1 21:13:26 joe acpid: client connected from 17248[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe acpid: client connected from 17250[0:0]
Feb  1 21:13:26 joe acpid: 1 client rule loaded
Feb  1 21:13:26 joe pulseaudio[17266]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:26 joe pulseaudio[17265]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:30 joe acpid: client 17249[0:0] has disconnected
Feb  1 21:13:30 joe acpid: client 17252[0:0] has disconnected
Feb  1 21:13:30 joe acpid: client 17251[0:0] has disconnected
Feb  1 21:13:30 joe acpid: client 17248[0:0] has disconnected
Feb  1 21:13:30 joe acpid: client 17250[0:0] has disconnected
Feb  1 21:13:31 joe pulseaudio[17411]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:31 joe pulseaudio[17409]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:36 joe pulseaudio[17573]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:36 joe pulseaudio[17575]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:41 joe acpid: client connected from 17718[0:0]
Feb  1 21:13:41 joe acpid: 1 client rule loaded
Feb  1 21:13:41 joe acpid: client 17718[0:0] has disconnected
Feb  1 21:13:41 joe acpid: client connected from 17722[0:0]
Feb  1 21:13:41 joe acpid: 1 client rule loaded
Feb  1 21:13:41 joe acpid: client connected from 17726[0:0]
Feb  1 21:13:41 joe acpid: 1 client rule loaded
Feb  1 21:13:41 joe acpid: client connected from 17721[0:0]
Feb  1 21:13:41 joe acpid: 1 client rule loaded
Feb  1 21:13:41 joe acpid: client connected from 17724[0:0]
Feb  1 21:13:41 joe acpid: 1 client rule loaded
Feb  1 21:13:41 joe acpid: client connected from 17725[0:0]
Feb  1 21:13:41 joe acpid: 1 client rule loaded
Feb  1 21:13:41 joe pulseaudio[17737]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:41 joe pulseaudio[17739]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:46 joe pulseaudio[17879]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:46 joe pulseaudio[17877]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:51 joe pulseaudio[18043]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:51 joe pulseaudio[18044]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:57 joe pulseaudio[18207]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:57 joe pulseaudio[18208]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:13:58 joe acpid: client 17722[0:0] has disconnected
Feb  1 21:13:58 joe acpid: client 17726[0:0] has disconnected
Feb  1 21:13:58 joe acpid: client 17721[0:0] has disconnected
Feb  1 21:13:58 joe acpid: client 17724[0:0] has disconnected
Feb  1 21:13:58 joe acpid: client 17725[0:0] has disconnected
Feb  1 21:13:58 joe acpid: client connected from 18243[0:0]
Feb  1 21:13:58 joe acpid: 1 client rule loaded
Feb  1 21:13:58 joe acpid: client connected from 18245[0:0]
Feb  1 21:13:58 joe acpid: 1 client rule loaded
Feb  1 21:13:58 joe acpid: client connected from 18246[0:0]
Feb  1 21:13:58 joe acpid: 1 client rule loaded
Feb  1 21:13:58 joe acpid: client connected from 18244[0:0]
Feb  1 21:13:58 joe acpid: 1 client rule loaded
Feb  1 21:13:58 joe acpid: client connected from 18247[0:0]
Feb  1 21:13:58 joe acpid: 1 client rule loaded
Feb  1 21:14:02 joe pulseaudio[18350]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:02 joe pulseaudio[18351]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:08 joe pulseaudio[18517]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:08 joe pulseaudio[18516]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:13 joe pulseaudio[18694]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:13 joe pulseaudio[18695]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:15 joe acpid: client 18243[0:0] has disconnected
Feb  1 21:14:15 joe acpid: client 18245[0:0] has disconnected
Feb  1 21:14:15 joe acpid: client 18246[0:0] has disconnected
Feb  1 21:14:15 joe acpid: client 18244[0:0] has disconnected
Feb  1 21:14:15 joe acpid: client 18247[0:0] has disconnected
Feb  1 21:14:15 joe acpid: client connected from 18747[0:0]
Feb  1 21:14:15 joe acpid: 1 client rule loaded
Feb  1 21:14:15 joe acpid: client connected from 18749[0:0]
Feb  1 21:14:15 joe acpid: 1 client rule loaded
Feb  1 21:14:15 joe acpid: client connected from 18756[0:0]
Feb  1 21:14:15 joe acpid: 1 client rule loaded
Feb  1 21:14:15 joe acpid: client connected from 18754[0:0]
Feb  1 21:14:15 joe acpid: 1 client rule loaded
Feb  1 21:14:15 joe acpid: client connected from 18755[0:0]
Feb  1 21:14:15 joe acpid: 1 client rule loaded
Feb  1 21:14:15 joe acpid: client connected from 18750[0:0]
Feb  1 21:14:15 joe acpid: 1 client rule loaded
Feb  1 21:14:15 joe acpid: client connected from 18752[0:0]
Feb  1 21:14:15 joe acpid: 1 client rule loaded
Feb  1 21:14:15 joe acpid: client connected from 18753[0:0]
Feb  1 21:14:15 joe acpid: 1 client rule loaded
Feb  1 21:14:15 joe acpid: client connected from 18757[0:0]
Feb  1 21:14:15 joe acpid: 1 client rule loaded
Feb  1 21:14:19 joe pulseaudio[18847]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:19 joe pulseaudio[18848]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:24 joe pulseaudio[19018]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:24 joe pulseaudio[19020]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:25 joe kernel: [25093.355277] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
Feb  1 21:14:29 joe pulseaudio[19168]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:29 joe pulseaudio[19169]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:30 joe acpid: client 18747[0:0] has disconnected
Feb  1 21:14:30 joe acpid: client 18749[0:0] has disconnected
Feb  1 21:14:30 joe acpid: client 18756[0:0] has disconnected
Feb  1 21:14:30 joe acpid: client 18754[0:0] has disconnected
Feb  1 21:14:30 joe acpid: client 18755[0:0] has disconnected
Feb  1 21:14:30 joe acpid: client 18750[0:0] has disconnected
Feb  1 21:14:30 joe acpid: client 18752[0:0] has disconnected
Feb  1 21:14:30 joe acpid: client 18753[0:0] has disconnected
Feb  1 21:14:30 joe acpid: client 18757[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client connected from 19267[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19269[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19282[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19268[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19270[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19274[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19275[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19278[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19280[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19279[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19277[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19283[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19284[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19299[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19298[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19297[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19285[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19293[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19295[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19296[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19308[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19310[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19311[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19314[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client 19298[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client connected from 19313[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client connected from 19312[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client 19278[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client 19279[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client 19285[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client connected from 19322[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:32 joe acpid: client 19267[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client 19269[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client 19282[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client 19268[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client 19270[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client 19274[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client 19275[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client 19280[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client 19277[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client 19284[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client 19297[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client 19296[0:0] has disconnected
Feb  1 21:14:32 joe acpid: client connected from 19309[0:0]
Feb  1 21:14:32 joe acpid: 1 client rule loaded
Feb  1 21:14:36 joe pulseaudio[19392]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:36 joe pulseaudio[19394]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:40 joe pulseaudio[19538]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:40 joe pulseaudio[19537]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:40 joe acpid: client 19283[0:0] has disconnected
Feb  1 21:14:40 joe acpid: client 19299[0:0] has disconnected
Feb  1 21:14:40 joe acpid: client 19293[0:0] has disconnected
Feb  1 21:14:40 joe acpid: client 19295[0:0] has disconnected
Feb  1 21:14:40 joe acpid: client 19308[0:0] has disconnected
Feb  1 21:14:40 joe acpid: client 19310[0:0] has disconnected
Feb  1 21:14:40 joe acpid: client 19311[0:0] has disconnected
Feb  1 21:14:40 joe acpid: client 19314[0:0] has disconnected
Feb  1 21:14:40 joe acpid: client 19313[0:0] has disconnected
Feb  1 21:14:40 joe acpid: client 19312[0:0] has disconnected
Feb  1 21:14:40 joe acpid: client 19322[0:0] has disconnected
Feb  1 21:14:40 joe acpid: client 19309[0:0] has disconnected
Feb  1 21:14:46 joe pulseaudio[19719]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:46 joe pulseaudio[19717]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:48 joe acpid: client connected from 19803[0:0]
Feb  1 21:14:48 joe acpid: 1 client rule loaded
Feb  1 21:14:48 joe acpid: client connected from 19804[0:0]
Feb  1 21:14:48 joe acpid: 1 client rule loaded
Feb  1 21:14:48 joe acpid: client connected from 19805[0:0]
Feb  1 21:14:48 joe acpid: 1 client rule loaded
Feb  1 21:14:48 joe acpid: client connected from 19810[0:0]
Feb  1 21:14:48 joe acpid: 1 client rule loaded
Feb  1 21:14:48 joe acpid: client connected from 19812[0:0]
Feb  1 21:14:48 joe acpid: 1 client rule loaded
Feb  1 21:14:48 joe acpid: client connected from 19809[0:0]
Feb  1 21:14:48 joe acpid: 1 client rule loaded
Feb  1 21:14:48 joe acpid: client connected from 19811[0:0]
Feb  1 21:14:48 joe acpid: 1 client rule loaded
Feb  1 21:14:48 joe acpid: client 19803[0:0] has disconnected
Feb  1 21:14:48 joe acpid: client 19804[0:0] has disconnected
Feb  1 21:14:48 joe acpid: client 19805[0:0] has disconnected
Feb  1 21:14:48 joe acpid: client 19810[0:0] has disconnected
Feb  1 21:14:48 joe acpid: client 19812[0:0] has disconnected
Feb  1 21:14:48 joe acpid: client 19809[0:0] has disconnected
Feb  1 21:14:48 joe acpid: client 19811[0:0] has disconnected
Feb  1 21:14:51 joe pulseaudio[19882]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:51 joe pulseaudio[19883]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:56 joe pulseaudio[20043]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:14:56 joe pulseaudio[20041]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:15:02 joe pulseaudio[20202]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:15:02 joe pulseaudio[20203]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:15:04 joe acpid: client connected from 20318[0:0]
Feb  1 21:15:04 joe acpid: 1 client rule loaded
Feb  1 21:15:04 joe acpid: client connected from 20316[0:0]
Feb  1 21:15:04 joe acpid: 1 client rule loaded
Feb  1 21:15:04 joe acpid: client connected from 20319[0:0]
Feb  1 21:15:04 joe acpid: 1 client rule loaded
Feb  1 21:15:04 joe acpid: client connected from 20317[0:0]
Feb  1 21:15:04 joe acpid: 1 client rule loaded
Feb  1 21:15:04 joe acpid: client connected from 20324[0:0]
Feb  1 21:15:04 joe acpid: 1 client rule loaded
Feb  1 21:15:04 joe acpid: client connected from 20327[0:0]
Feb  1 21:15:04 joe acpid: 1 client rule loaded
Feb  1 21:15:04 joe acpid: client connected from 20329[0:0]
Feb  1 21:15:04 joe acpid: 1 client rule loaded
Feb  1 21:15:04 joe acpid: client connected from 20326[0:0]
Feb  1 21:15:04 joe acpid: 1 client rule loaded
Feb  1 21:15:04 joe acpid: client connected from 20325[0:0]
Feb  1 21:15:04 joe acpid: 1 client rule loaded
Feb  1 21:15:04 joe acpid: client connected from 20328[0:0]
Feb  1 21:15:04 joe acpid: 1 client rule loaded
Feb  1 21:15:04 joe acpid: client 20318[0:0] has disconnected
Feb  1 21:15:04 joe acpid: client 20316[0:0] has disconnected
Feb  1 21:15:04 joe acpid: client 20319[0:0] has disconnected
Feb  1 21:15:04 joe acpid: client 20317[0:0] has disconnected
Feb  1 21:15:04 joe acpid: client 20324[0:0] has disconnected
Feb  1 21:15:04 joe acpid: client 20327[0:0] has disconnected
Feb  1 21:15:04 joe acpid: client 20329[0:0] has disconnected
Feb  1 21:15:04 joe acpid: client 20326[0:0] has disconnected
Feb  1 21:15:04 joe acpid: client 20325[0:0] has disconnected
Feb  1 21:15:04 joe acpid: client 20328[0:0] has disconnected
Feb  1 21:15:07 joe pulseaudio[20367]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:15:08 joe pulseaudio[20381]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:15:12 joe pulseaudio[20495]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:15:12 joe pulseaudio[20498]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:15:16 joe pulseaudio[20583]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:15:16 joe pulseaudio[20582]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:15:21 joe pulseaudio[20742]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:15:21 joe pulseaudio[20743]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:15:24 joe acpid: client connected from 20844[0:0]
Feb  1 21:15:24 joe acpid: 1 client rule loaded
Feb  1 21:15:24 joe acpid: client connected from 20842[0:0]
Feb  1 21:15:24 joe acpid: 1 client rule loaded
Feb  1 21:15:24 joe acpid: client connected from 20843[0:0]
Feb  1 21:15:24 joe acpid: 1 client rule loaded
Feb  1 21:15:24 joe acpid: client connected from 20858[0:0]
Feb  1 21:15:24 joe acpid: 1 client rule loaded
Feb  1 21:15:24 joe acpid: client connected from 20841[0:0]
Feb  1 21:15:24 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20849[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20854[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20855[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20851[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20864[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20850[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20847[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20861[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20856[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20859[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20852[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20884[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20865[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20878[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20863[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20879[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20883[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20881[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20862[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20880[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:25 joe acpid: client connected from 20882[0:0]
Feb  1 21:15:25 joe acpid: 1 client rule loaded
Feb  1 21:15:26 joe pulseaudio[20926]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
Feb  1 21:15:26 joe pulseaudio[20929]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn.
