MinimServer Forum

Full Version: MinimWatch startup error
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
This is happening regularly since I reinstated my main desktop pc with a new power supply. Almost every time I boot up (running Ubuntu 12.04 with Classic Gnome) I get this pop-up: "MinimWatch startup error. MinimWatch: unable to create tray icon." I have desktop integration enabled, and clicking on the desktop icon then does create the tray icon and all proceeds as normal. There have been three occasions in the last week or two when I haven't had the error pop-up and MinimWatch has shown up in the notification bar as it always did. This is a very minor glitch which I can easily live with, but I'm curious as much as anything to find what's causing it. After it had happened a few times I activated ' debug level' in the MinimWatch log. I can't make much sense of the log, but here's what I saved of it the other day:

Quote:16:18:15.935 main: setFile: logFileName=minimwatch.log append=false
16:18:15.943 main: setFile: logFile is /home/nick/minimwatch/data/minimwatch.log
16:18:15.947 main: setFile: logDir is /home/nick/minimwatch/data
16:18:15.968 main: active packages: [/home/nick/minimwatch/minimwatch-0.8.3d/lib/minimwatch-0.8.3.jmpkg, /home/nick/minimwatch/minimwatch-0.8.3d/lib/minimwatch-0.8-update-30.jmpkg, /home/nick/minimwatch/libext/minimwatch-0.8-update-32.jmpkg]
16:18:15.983 main: validating extension package minimwatch-0.8-update-32
16:18:15.983 main: adding package minimwatch-0.8-update-32 to packageList
16:18:15.986 main: completed package conflict checking
16:18:15.986 main: adding extension packages to packageList
16:18:15.986 main: merging update information into base packages
16:18:15.995 main: RuntimeImpl: completed init processing
MinimWatch 0.8.3 update 32, Copyright © 2012-2015 Simon Nash. All rights reserved.
OpenJDK Runtime Environment (build 1.7.0_79-b14)
OpenJDK Client VM (build 24.79-b02, mixed mode, sharing)
Platform default charset is UTF-8
16:18:16.000 main: classpath: /home/nick/minimwatch/lib/mwatch.jar
16:18:16.002 main: creating component: --context
16:18:16.002 main: Context: setting property context0.type to value org.jminim.core.ContextImpl
16:18:16.007 main: creating component: --start type=com.minimserver.watch.MinimWatch name=minimwatch
16:18:16.008 main: Context: setting property minimwatch.type to value com.minimserver.watch.MinimWatch
16:18:16.026 main: Context: setting property minimwatch.name to value minimwatch
16:18:16.055 main: Context: setting property consoleContext.type to value org.jminim.core.ContextImpl
16:18:16.055 main: Context: setting property consoleContext.name to value consoleContext
16:18:16.056 main: Context: setting property console.name to value console
16:18:16.057 main: setProperty: compName=console propName=interactive propValue=false
16:18:16.057 main: starting context consoleContext
16:18:16.063 main: >>> EVENT >>> contextStarting: consoleContext
16:18:16.063 main: starting component console in context consoleContext
16:18:16.067 main: >>> EVENT >>> componentStarting: console
16:18:16.067 main: started component console in context consoleContext
16:18:16.068 main: >>> EVENT >>> componentRunning: console
16:18:16.069 main: started context consoleContext
16:18:16.069 main: >>> EVENT >>> contextRunning: consoleContext
16:18:16.090 main: Context: setting property runtimeContext.type to value org.jminim.core.ContextImpl
16:18:16.090 main: Context: setting property runtimeContext.name to value runtimeContext
16:18:16.092 main: Context: setting property runtime.name to value runtime
16:18:16.092 main: starting context runtimeContext
16:18:16.092 main: >>> EVENT >>> contextStarting: runtimeContext
16:18:16.093 main: starting component runtime in context runtimeContext
16:18:16.094 main: >>> EVENT >>> componentStarting: runtime
16:18:16.094 main: started component runtime in context runtimeContext
16:18:16.094 main: >>> EVENT >>> componentRunning: runtime
16:18:16.094 main: started context runtimeContext
16:18:16.095 main: >>> EVENT >>> contextRunning: runtimeContext
16:18:16.102 main: ConsoleService: listenerAdded called with RuntimeActions
16:18:16.104 main: ConsoleService: listenerAdded called with RuntimeProxy
16:18:16.104 main: setProperty: compName=console propName=interactive propValue=false
16:18:16.111 main: starting context rootContext
16:18:16.111 main: starting context context0
16:18:16.113 main: >>> EVENT >>> contextStarting: context0
16:18:16.113 main: ConsoleService: contextStarting event for context0
16:18:16.113 main: starting component minimwatch in context context0
16:18:16.114 main: >>> EVENT >>> componentStarting: minimwatch
16:18:16.115 main: starting MinimWatch
16:18:16.115 main: setProperty: compName=minimwatch propName=propNames propValue=.autoUpdate,delayStart,.logFile,.logLevel,.logPrefix,ohnet.debug,ohnet​.subnet,.updateReminder
16:18:16.117 main: setProperty: compName=minimwatch propName=advancedPropNames propValue=
16:18:16.144 main: Context: setting property observerContext.type to value org.jminim.core.ContextImpl
16:18:16.144 main: Context: setting property observerContext.name to value observerContext
16:18:16.144 main: Context: setting property observer.name to value observer
16:18:16.146 main: starting context observerContext
16:18:16.146 main: >>> EVENT >>> contextStarting: observerContext
16:18:16.146 main: ConsoleService: contextStarting event for observerContext
16:18:16.146 main: starting component observer in context observerContext
16:18:16.148 main: >>> EVENT >>> componentStarting: observer
16:18:16.148 main: starting ObserverService
16:18:16.150 main: started component observer in context observerContext
16:18:16.150 main: >>> EVENT >>> componentRunning: observer
16:18:16.150 main: started context observerContext
16:18:16.152 main: >>> EVENT >>> contextRunning: observerContext
16:18:16.152 main: ConsoleService: contextRunning event for observerContext
16:18:16.166 main: Context: setting property watchContext.type to value org.jminim.core.ContextImpl
16:18:16.168 main: Context: setting property watchContext.name to value watchContext
16:18:16.168 main: Context: setting property watch.name to value watch
16:18:16.168 main: starting context watchContext
16:18:16.170 main: >>> EVENT >>> contextStarting: watchContext
16:18:16.170 main: ConsoleService: contextStarting event for watchContext
16:18:16.170 main: starting component watch in context watchContext
16:18:16.170 main: >>> EVENT >>> componentStarting: watch
16:18:16.171 main: started component watch in context watchContext
16:18:16.172 main: >>> EVENT >>> componentRunning: watch
16:18:16.172 main: started context watchContext
16:18:16.172 main: >>> EVENT >>> contextRunning: watchContext
16:18:16.172 main: ConsoleService: contextRunning event for watchContext
16:18:16.182 main: WatchService: creating watch console 1
16:18:16.204 main: DefaultConsole: dispose
16:18:16.204 main: ConsoleService: listenerRemoved event
16:18:16.206 main: ServerConsole: init call
16:18:16.326 main: ServerControl: listenerAdded called with RuntimeActions
16:18:16.328 main: ServerControl: listenerAdded called with RuntimeProxy
16:18:16.330 main: ServerControl: runtime version is 0.6.206
16:18:16.362 main: ServerConsole: running checkUpdates
16:18:16.363 main: ServerConsole.checkUpdates: adding update view for MinimWatch
16:18:16.367 main: setProperty: compName=console propName=interactive propValue=false
16:18:16.367 main: WatchService: creating watch tray icon
16:18:16.379 Thread-5: ServerConsole: running doCheckUpdates
16:18:16.379 Thread-5: ServerConsole.doCheckUpdates: checking update offers for MinimWatch
16:18:16.387 Thread-5: ServerControl.doCheckUpdateOffer: allPackages=minimwatch-0.8-update-30,Active+Original,MinimWatch 0.8 update,30,,minimwatch-*,minimwatch-0.8-update-32,Active,MinimWatch 0.8 update,32,,minimwatch-*,minimwatch-0.8.3,Active+Original,MinimWatch,0.8.3,minimwatch-0.8.3.jmupd,
16:18:16.387 Thread-5: ServerControl.readCheckedUpdates: checkedUpdates=minimwatch-0.8.3.jmupd
minimwatch-0.8-update-32;1436973848767
16:18:16.391 Thread-5: found checkedUpdates entry for minimwatch-0.8.3.jmupd
16:18:16.393 Thread-5: adding update to checkedUpdatesMap: updFile=minimwatch-0.8.3.jmupd lastOffer=minimwatch-0.8-update-32;1436973848767
16:18:16.399 Thread-5: ServerControl.checkOffer: updateFile=minimwatch-0.8.3.jmupd
16:18:16.400 Thread-5: getUpdatePackages: updateFile=minimwatch-0.8.3.jmupd
System look and feel is com.sun.java.swing.plaf.gtk.GTKLookAndFeel
16:18:17.170 Thread-5: ServerControl.isPackageRequired: packageName=minimwatch-0.8-update-32
16:18:17.172 Thread-5: isPackageRequired: minimwatch-0.8-update-32 is already installed
16:18:17.172 Thread-5: ServerConsole.doCheckUpdates: removing update view for MinimWatch
16:18:17.172 Thread-5: ServerConsole.doCheckUpdates: updateViews is empty
16:18:19.143 AWT-EventQueue-0: TrayView: creating tray icon
16:18:19.145 AWT-EventQueue-0: TrayView classloader is org.jminim.core.ComponentClassLoader@b4d39c
16:18:19.147 AWT-EventQueue-0: ComponentClassLoader: added jar file entry for /home/nick/minimwatch/libext/minimui-0.8.205.jar
16:18:19.218 AWT-EventQueue-0: TrayView: created tray icon
16:18:19.218 main: TrayView: adding tray icon
16:18:20.179 main: TrayView: added tray icon
16:18:20.179 main: ServerControl: listenerAdded called with RuntimeActions
16:18:20.179 main: ServerControl: listenerAdded called with RuntimeProxy
16:18:20.179 main: ServerControl: runtime version is 0.6.206
16:18:20.331 main: TrayControl: running checkUpdates
16:18:20.331 main: TrayControl.checkUpdates: adding update view for MinimWatch
16:18:20.335 main: setProperty: compName=null propName=autoUpdate propValue=true
16:18:20.335 main: ServerControl.doCheckUpdateOffer: allPackages=minimwatch-0.8-update-30,Active+Original,MinimWatch 0.8 update,30,,minimwatch-*,minimwatch-0.8-update-32,Active,MinimWatch 0.8 update,32,,minimwatch-*,minimwatch-0.8.3,Active+Original,MinimWatch,0.8.3,minimwatch-0.8.3.jmupd,
16:18:20.337 main: ServerControl.checkOffer: updateFile=minimwatch-0.8.3.jmupd
16:18:20.340 main: getUpdatePackages: updateFile=minimwatch-0.8.3.jmupd
16:18:20.346 Thread-8: TrayControl: running doCheckUpdates
16:18:20.347 Thread-8: TrayControl.doCheckUpdates: checking update offers for MinimWatch
16:18:20.348 Thread-8: ServerControl.doCheckUpdateOffer: allPackages=minimwatch-0.8-update-30,Active+Original,MinimWatch 0.8 update,30,,minimwatch-*,minimwatch-0.8-update-32,Active,MinimWatch 0.8 update,32,,minimwatch-*,minimwatch-0.8.3,Active+Original,MinimWatch,0.8.3,minimwatch-0.8.3.jmupd,
16:18:20.348 Thread-8: ServerControl.readCheckedUpdates: checkedUpdates=minimwatch-0.8.3.jmupd
minimwatch-0.8-update-32;1436973848767
16:18:20.348 Thread-8: found checkedUpdates entry for minimwatch-0.8.3.jmupd
16:18:20.350 Thread-8: adding update to checkedUpdatesMap: updFile=minimwatch-0.8.3.jmupd lastOffer=minimwatch-0.8-update-32;1436973848767
16:18:20.350 Thread-8: ServerControl.checkOffer: updateFile=minimwatch-0.8.3.jmupd
16:18:20.350 Thread-8: getUpdatePackages: updateFile=minimwatch-0.8.3.jmupd
16:18:20.476 main: ServerControl.isPackageRequired: packageName=minimwatch-0.8-update-32
16:18:20.477 main: isPackageRequired: minimwatch-0.8-update-32 is already installed
16:18:20.483 Thread-8: ServerControl.isPackageRequired: packageName=minimwatch-0.8-update-32
16:18:20.483 Thread-8: isPackageRequired: minimwatch-0.8-update-32 is already installed
16:18:20.485 Thread-8: TrayControl.doCheckUpdates: removing update view for MinimWatch
16:18:20.485 Thread-8: TrayControl.doCheckUpdates: updateViews is empty
16:18:20.491 main: setProperty: compName=null propName=updateReminder propValue=1
16:18:20.491 main: .updateReminder setting is 1
16:18:20.525 main: Context: setting property httpContext.type to value org.jminim.core.ContextImpl
16:18:20.525 main: Context: setting property httpContext.name to value httpContext
16:18:20.526 main: Context: setting property http.name to value http
16:18:20.527 main: starting context httpContext
16:18:20.527 main: >>> EVENT >>> contextStarting: httpContext
16:18:20.527 main: starting component http in context httpContext
16:18:20.528 main: >>> EVENT >>> componentStarting: http
16:18:20.529 main: starting HTTPService
16:18:20.529 main: setLocalProperty: compName=http propName=port propValue=9790
16:18:20.529 main: HTTPService: using port 9790
16:18:20.531 main: started component http in context httpContext
16:18:20.531 main: >>> EVENT >>> componentRunning: http
16:18:20.531 main: started context httpContext
16:18:20.531 main: >>> EVENT >>> contextRunning: httpContext
16:18:20.535 main: disposing HTTPContext
16:18:20.535 main: ObserverService: starting ohNet
16:18:20.590 main: Context: setting property ohnetContext.type to value org.jminim.core.ContextImpl
16:18:20.593 main: Context: setting property ohnetContext.name to value ohnetContext
16:18:20.593 main: Context: setting property ohnet.name to value ohnet
16:18:20.595 main: starting context ohnetContext
16:18:20.595 main: >>> EVENT >>> contextStarting: ohnetContext
16:18:20.595 main: starting component ohnet in context ohnetContext
16:18:20.595 main: >>> EVENT >>> componentStarting: ohnet
16:18:20.596 main: setLocalProperty: compName=ohnet propName=port propValue=9791
16:18:20.597 main: OhNetService: using UPnP port 9791
16:18:20.597 main: setLocalProperty: compName=ohnet propName=debug propValue=Default
16:18:20.617 main: OhNetService: adding debugValue 0x7FFFFF47
16:18:20.619 main: OhNetService: ohNet debug setting is 0x7FFFFF47
16:18:20.646 main: started component ohnet in context ohnetContext
16:18:20.647 main: >>> EVENT >>> componentRunning: ohnet
16:18:20.647 main: started context ohnetContext
16:18:20.647 main: >>> EVENT >>> contextRunning: ohnetContext
16:18:20.650 main: OhNetService: creating device list factory
16:18:20.652 main: OhNetService: creating library
16:18:20.652 main: classloader is org.jminim.core.ComponentClassLoader@b4d39c
16:18:20.658 main: InitParams classloader is org.jminim.core.ComponentClassLoader@b4d39c
16:18:20.660 main: ComponentClassLoader: added jar file entry for /home/nick/minimwatch/libext/ohnet(linux-x86)-1.1.1452.zip
16:18:20.816 main: OhNetService: InitParams created
16:18:20.816 main: OhNetService: including loopback network adapter
16:18:20.877 main: OhNetService: library created
16:18:20.889 main: OhNetService: library initialized
16:18:20.891 main: OhNetService: creating ControlPointStack
16:18:20.917 main: OhNetService: control point stack subnet is 192.168.1.0
Active subnet is 192.168.1.0
16:18:20.941 main: OhNetService: device list factory created
16:18:20.963 main: OhNetService: creating device type device list
16:18:21.005 main: OhNetService: adding device list and listener to HashMap
16:18:21.009 main: OhNetService: creating service type device list
16:18:21.021 main: OhNetService: adding device list and listener to HashMap
16:18:21.021 main: OhNetService: creating service type device list
16:18:21.023 main: OhNetService: adding device list and listener to HashMap
16:18:21.024 main: OhNetService: disposing device list factory
16:18:21.024 main: OhNetService: device list factory disposed
16:18:21.024 main: ObserverService: started ohNet
16:18:21.024 main: started component minimwatch in context context0
16:18:21.024 main: >>> EVENT >>> componentRunning: minimwatch
16:18:21.024 main: ServerControl: monitoring minimwatch component, context context0
16:18:21.026 main: ServerControl: monitoring minimwatch component, context context0
16:18:21.026 main: started context context0
16:18:21.026 main: >>> EVENT >>> contextRunning: context0
16:18:21.026 main: context already started: consoleContext
16:18:21.026 main: context already started: runtimeContext
16:18:21.026 main: context already started: observerContext
16:18:21.027 main: context already started: watchContext
16:18:21.028 main: context already started: httpContext
16:18:21.030 main: context already started: ohnetContext
16:18:21.030 main: started context rootContext
16:18:21.030 main: >>> EVENT >>> startupComplete
16:18:21.030 main: ServerControl: startupComplete event
16:18:21.031 main: ServerControl: startupComplete event
16:18:22.330 Thread-15: ListServiceType:jminim.org:Monitor1: device added for udn d9e2ea95-b62a-4ed3-9c63-0db24028e2cc: org.openhome.net.controlpoint.CpDevice@e596c9
16:18:22.332 Thread-15: Upnp.Location: http://192.168.1.20:9791/d9e2ea95-b62a-4...device.xml
16:18:22.332 Thread-15: Upnp.DeviceXml: <?xml version="1.0" encoding="utf-8"?><root xmlns="urn:schemas-upnp-org:device-1-0"><specVersion><major>1</major><minor>1</minor></specVersion><device><deviceType>urn:jminim-org:device:Monitor:1</deviceType><friendlyName>Monitor Service</friendlyName><manufacturer>jMinim</manufacturer><modelName>MonitorService</modelName><UDN>uuid:d9e2ea95-b62a-4ed3-9c63-0db24028e2cc</UDN><serviceList><service><serviceType>urn:jminim-org:service:Monitor:1</serviceType><serviceId>urn:jminim-org:serviceId:Monitor</serviceId><SCPDURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/Upnp/jminim.org-Monitor-1/service.xml</SCPDURL><controlURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/jminim.org-Monitor-1/control</controlURL><eventSubURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/jminim.org-Monitor-1/event</eventSubURL></service><service><serviceType>urn:jminim-org:service:Log:1</serviceType><serviceId>urn:jminim-org:serviceId:Log</serviceId><SCPDURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/Upnp/jminim.org-Log-1/service.xml</SCPDURL><controlURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/jminim.org-Log-1/control</controlURL><eventSubURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/jminim.org-Log-1/event</eventSubURL></service></serviceList></device></root>
16:18:22.334 Thread-15: Upnp.FriendlyName: Monitor Service
16:18:22.335 Thread-15: Upnp.PresentationUrl: null
16:18:22.335 Thread-15: ObserverService: device added for udn d9e2ea95-b62a-4ed3-9c63-0db24028e2cc: org.openhome.net.controlpoint.CpDevice@e596c9
16:18:22.335 Thread-15: ObserverService: calling addRef for device org.openhome.net.controlpoint.CpDevice@e596c9
16:18:22.338 Thread-9: DeviceAddedAction starting
16:18:22.391 Thread-9: initializing DeviceMonitor
16:18:22.607 Thread-9: checking remote runtime version
16:18:22.678 Thread-9: remote runtime version is 0.6.207
16:18:22.743 Thread-9: ServerConsoleCallback: discovered remote device
16:18:22.744 Thread-9: ServerControl: listenerAdded called with RuntimeProxy
16:18:22.761 Thread-15: ListDeviceType:jminim.org:Monitor1: device added for udn d9e2ea95-b62a-4ed3-9c63-0db24028e2cc: org.openhome.net.controlpoint.CpDevice@1a5d193
16:18:22.787 Thread-15: Upnp.Location: http://192.168.1.20:9791/d9e2ea95-b62a-4...device.xml
16:18:22.790 Thread-9: ServerControl: runtime version is 0.6.207
16:18:22.790 Thread-9: TrayCallback: discovered remote device
16:18:22.794 Thread-15: Upnp.DeviceXml: <?xml version="1.0" encoding="utf-8"?><root xmlns="urn:schemas-upnp-org:device-1-0"><specVersion><major>1</major><minor>1</minor></specVersion><device><deviceType>urn:jminim-org:device:Monitor:1</deviceType><friendlyName>Monitor Service</friendlyName><manufacturer>jMinim</manufacturer><modelName>MonitorService</modelName><UDN>uuid:d9e2ea95-b62a-4ed3-9c63-0db24028e2cc</UDN><serviceList><service><serviceType>urn:jminim-org:service:Monitor:1</serviceType><serviceId>urn:jminim-org:serviceId:Monitor</serviceId><SCPDURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/Upnp/jminim.org-Monitor-1/service.xml</SCPDURL><controlURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/jminim.org-Monitor-1/control</controlURL><eventSubURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/jminim.org-Monitor-1/event</eventSubURL></service><service><serviceType>urn:jminim-org:service:Log:1</serviceType><serviceId>urn:jminim-org:serviceId:Log</serviceId><SCPDURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/Upnp/jminim.org-Log-1/service.xml</SCPDURL><controlURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/jminim.org-Log-1/control</controlURL><eventSubURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/jminim.org-Log-1/event</eventSubURL></service></serviceList></device></root>
16:18:22.794 Thread-15: Upnp.FriendlyName: Monitor Service
16:18:22.797 Thread-15: Upnp.PresentationUrl: null
16:18:22.798 Thread-15: ObserverService: device added for udn d9e2ea95-b62a-4ed3-9c63-0db24028e2cc: org.openhome.net.controlpoint.CpDevice@1a5d193
16:18:22.812 Thread-9: TrayCallback: adding ServerControl
16:18:22.813 AWT-EventQueue-0: TrayView: creating tray icon
16:18:22.815 AWT-EventQueue-0: TrayView classloader is org.jminim.core.ComponentClassLoader@b4d39c
16:18:22.820 AWT-EventQueue-0: TrayView: created tray icon
16:18:22.822 Thread-9: ServerControl: listenerAdded called with RuntimeProxy
16:18:22.831 Thread-9: ServerControl: runtime version is 0.6.207
16:18:22.831 Thread-9: starting DeviceMonitor
16:18:22.831 Thread-9: DeviceMonitor.start: subscribing monitorProxy org.jminim.ohnet.CpProxyJminimOrgMonitor1@12c1472
16:18:22.835 Thread-15: ObserverService: ignoring added device with duplicate udn d9e2ea95-b62a-4ed3-9c63-0db24028e2cc
16:18:22.836 Thread-9: DeviceAddedAction ended
16:18:22.848 Thread-22: AllComponentStatusChanged: notifyChange time=1437747502848
16:18:22.852 Thread-9: AllComponentStatusChangedAction starting
16:18:22.852 Thread-9: AllComponentStatusChangedAction ended
16:18:22.854 Thread-22: AllContextStatusChanged: notifyChange time=1437747502854
16:18:22.857 Thread-9: AllContextStatusChangedAction starting
16:18:22.857 Thread-9: AllContextStatusChangedAction ended
16:18:22.857 Thread-22: PropertyUpdatesChanged: notifyChange time=1437747502857
16:18:22.862 Thread-9: PropertyUpdatesChangedAction starting
16:18:22.863 Thread-9: PropertyUpdatesChangedAction ended
16:18:22.863 Thread-22: MonitorInitialEvent: notifyChange time=1437747502863
16:18:22.866 Thread-9: MonitorInitialEventAction starting
16:18:22.868 Thread-9: initial value of AllContextStatus=consoleContext,Running,context0,Running,watchContext,Running,ru​ntimeContext,Running,monitorContext,Running,ohnetContext,Running,httpContext,Run​ning
16:18:22.868 Thread-9: initial value of AllComponentStatus=console,org.jminim.lib.ConsoleService,consoleContext,Running,​minimserver,com.minimserver.Server,context0,Running,stream,com.minimstreamer.Str​eamer,context0,Running,watch,com.minimserver.lib.WatchService,watchContext,Runni​ng,runtime,org.jminim.lib.RuntimeService,runtimeContext,Running,monitor,org.jmin​im.lib.MonitorService,monitorContext,Running,ohnet,org.jminim.lib.OhNetService,o​hnetContext,Running,http,org.jminim.lib.HTTPService,httpContext,Running
16:18:22.869 Thread-9: DeviceMonitor notifyComponent: name=console, type=org.jminim.lib.ConsoleService, context=consoleContext, status=Running
16:18:22.871 Thread-9: DeviceMonitor notifyContext: name=consoleContext, status=Running
16:18:22.871 Thread-9: DeviceMonitor notifyComponent: name=minimserver, type=com.minimserver.Server, context=context0, status=Running
16:18:22.871 Thread-9: ServerControl: monitoring server component minimserver, context context0
16:18:22.871 Thread-9: ServerControl: componentRunning event for minimserver
16:18:22.871 Thread-9: ServerControl: monitoring server component minimserver, context context0
16:18:22.872 Thread-9: ServerControl: componentRunning event for minimserver
16:18:22.872 Thread-9: DeviceMonitor notifyComponent: name=stream, type=com.minimstreamer.Streamer, context=context0, status=Running
16:18:22.872 Thread-9: ServerControl: componentRunning event for stream
16:18:22.872 Thread-9: ServerControl: componentRunning event for stream
16:18:22.872 Thread-9: DeviceMonitor notifyContext: name=context0, status=Running
16:18:22.872 Thread-9: ServerControl: contextRunning event for context0
Selected media server: MinimServer[QNAP-TS-109]
MinimServer[QNAP-TS-109] is running
16:18:22.895 Thread-9: ServerConsole: running checkUpdates
16:18:22.895 Thread-9: ServerConsole.checkUpdates: adding update view for MinimServer[QNAP-TS-109]
16:18:22.898 Thread-23: ServerConsole: running doCheckUpdates
16:18:22.898 Thread-9: ServerControl: contextRunning event for context0
16:18:22.898 Thread-23: ServerConsole.doCheckUpdates: scheduling update check
16:18:22.912 Thread-9: removing default tray icon
16:18:22.912 Thread-9: TrayView: removing tray icon
16:18:22.916 Thread-9: disposed popupMenu peer after 0 retries
16:18:22.917 Thread-9: got trayIcon peer
16:18:22.918 Thread-9: trayIcon messageDialog is null
16:18:22.938 Thread-9: TrayView: removed tray icon
16:18:22.940 Thread-9: TrayView: adding tray icon
16:18:23.196 Thread-15: ListServiceType:jminim.org:Log1: device added for udn d9e2ea95-b62a-4ed3-9c63-0db24028e2cc: org.openhome.net.controlpoint.CpDevice@1c21ed3
16:18:23.196 Thread-15: Upnp.Location: http://192.168.1.20:9791/d9e2ea95-b62a-4...device.xml
16:18:23.196 Thread-15: Upnp.DeviceXml: <?xml version="1.0" encoding="utf-8"?><root xmlns="urn:schemas-upnp-org:device-1-0"><specVersion><major>1</major><minor>1</minor></specVersion><device><deviceType>urn:jminim-org:device:Monitor:1</deviceType><friendlyName>Monitor Service</friendlyName><manufacturer>jMinim</manufacturer><modelName>MonitorService</modelName><UDN>uuid:d9e2ea95-b62a-4ed3-9c63-0db24028e2cc</UDN><serviceList><service><serviceType>urn:jminim-org:service:Monitor:1</serviceType><serviceId>urn:jminim-org:serviceId:Monitor</serviceId><SCPDURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/Upnp/jminim.org-Monitor-1/service.xml</SCPDURL><controlURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/jminim.org-Monitor-1/control</controlURL><eventSubURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/jminim.org-Monitor-1/event</eventSubURL></service><service><serviceType>urn:jminim-org:service:Log:1</serviceType><serviceId>urn:jminim-org:serviceId:Log</serviceId><SCPDURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/Upnp/jminim.org-Log-1/service.xml</SCPDURL><controlURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/jminim.org-Log-1/control</controlURL><eventSubURL>/d9e2ea95-b62a-4ed3-9c63-0db24028e2cc/jminim.org-Log-1/event</eventSubURL></service></serviceList></device></root>
16:18:23.196 Thread-15: Upnp.FriendlyName: Monitor Service
16:18:23.198 Thread-15: Upnp.PresentationUrl: null
16:18:23.198 Thread-15: ObserverService: device added for udn d9e2ea95-b62a-4ed3-9c63-0db24028e2cc: org.openhome.net.controlpoint.CpDevice@1c21ed3
16:18:23.198 Thread-15: ObserverService: ignoring added device with duplicate udn d9e2ea95-b62a-4ed3-9c63-0db24028e2cc
16:18:23.475 Thread-9: TrayView: added tray icon
16:18:23.478 AWT-EventQueue-0: TrayView: displaying tray icon message: MinimServer[QNAP-TS-109] is running
16:18:23.647 AWT-EventQueue-0: TrayView: displaying tray icon tooltip: MinimServer[QNAP-TS-109] is running
16:18:23.669 Thread-9: TrayControl: running checkUpdates
16:18:23.669 Thread-9: TrayControl.checkUpdates: adding update view for MinimServer[QNAP-TS-109]
16:18:23.737 Thread-9: DeviceMonitor notifyComponent: name=watch, type=com.minimserver.lib.WatchService, context=watchContext, status=Running
16:18:23.737 Thread-9: DeviceMonitor notifyContext: name=watchContext, status=Running
16:18:23.737 Thread-9: DeviceMonitor notifyComponent: name=runtime, type=org.jminim.lib.RuntimeService, context=runtimeContext, status=Running
16:18:23.737 Thread-9: DeviceMonitor notifyContext: name=runtimeContext, status=Running
16:18:23.737 Thread-9: DeviceMonitor notifyComponent: name=monitor, type=org.jminim.lib.MonitorService, context=monitorContext, status=Running
16:18:23.738 Thread-9: DeviceMonitor notifyContext: name=monitorContext, status=Running
16:18:23.738 Thread-9: DeviceMonitor notifyComponent: name=ohnet, type=org.jminim.lib.OhNetService, context=ohnetContext, status=Running
16:18:23.738 Thread-9: DeviceMonitor notifyContext: name=ohnetContext, status=Running
16:18:23.738 Thread-9: DeviceMonitor notifyComponent: name=http, type=org.jminim.lib.HTTPService, context=httpContext, status=Running
16:18:23.738 Thread-9: DeviceMonitor notifyContext: name=httpContext, status=Running
16:18:23.738 Thread-9: initial value of PropertyUpdates=
16:18:23.740 Thread-9: MonitorInitialEventAction ended
16:18:23.775 Thread-26: TrayControl: running doCheckUpdates
16:18:23.775 Thread-26: TrayControl.doCheckUpdates: checking update offers for MinimServer[QNAP-TS-109]
16:18:23.791 Thread-26: ServerControl.doCheckUpdateOffer: allPackages=minimserver-0.8-update-50,Active+Original,MinimServer 0.8 update,50,,minimserver-*,minimserver-0.8-update-66,Active,MinimServer 0.8 update,66,,minimserver-*,minimserver-0.8.3,Active+Original,MinimServer,0.8.3,minimserver-0.8.3.jmupd,,minimstreamer-0.5.13,Active,MinimStreamer,0.5.13,minimstreamer-0.5.jmupd,
16:18:23.809 Thread-26: ServerControl.readCheckedUpdates: checkedUpdates=
16:18:23.818 Thread-26: ServerControl.checkOffer: updateFile=minimserver-0.8.3.jmupd
16:18:23.818 Thread-26: getUpdatePackages: updateFile=minimserver-0.8.3.jmupd
16:18:24.017 Thread-26: ServerControl.isPackageRequired: packageName=minimserver-0.8-update-66
16:18:24.017 Thread-26: isPackageRequired: minimserver-0.8-update-66 is already installed
16:18:24.017 Thread-26: ServerControl.checkOffer: updateFile=minimstreamer-0.5.jmupd
16:18:24.017 Thread-26: getUpdatePackages: updateFile=minimstreamer-0.5.jmupd
16:18:24.177 Thread-26: ServerControl.isPackageRequired: packageName=minimstreamer-0.5.13
16:18:24.177 Thread-26: isPackageRequired: minimstreamer-0.5.13 is already installed
16:18:24.177 Thread-26: TrayControl.doCheckUpdates: removing update view for MinimServer[QNAP-TS-109]
16:18:24.177 Thread-26: TrayControl.doCheckUpdates: updateViews is empty
16:18:32.406 AWT-EventQueue-0: TrayView: show log action
16:18:32.408 Thread-27: ServerControl: showLog action
16:18:32.408 Thread-27: Remote runtime log level: debug
16:18:33.271 Thread-27: ServerControl: setLogUpdates action, logUpdates=true
16:18:33.271 Thread-27: TrayView: returning from doShowLog method
16:20:16.381 Thread-28: ServerConsole: running doCheckUpdates
16:20:16.382 Thread-28: ServerConsole.doCheckUpdates: checking update offers for MinimServer[QNAP-TS-109]
16:20:16.393 Thread-28: ServerControl.doCheckUpdateOffer: allPackages=minimserver-0.8-update-50,Active+Original,MinimServer 0.8 update,50,,minimserver-*,minimserver-0.8-update-66,Active,MinimServer 0.8 update,66,,minimserver-*,minimserver-0.8.3,Active+Original,MinimServer,0.8.3,minimserver-0.8.3.jmupd,,minimstreamer-0.5.13,Active,MinimStreamer,0.5.13,minimstreamer-0.5.jmupd,
16:20:16.404 Thread-28: ServerControl.readCheckedUpdates: checkedUpdates=
16:20:16.416 Thread-28: ServerControl.checkOffer: updateFile=minimserver-0.8.3.jmupd
16:20:16.416 Thread-28: getUpdatePackages: updateFile=minimserver-0.8.3.jmupd
16:20:18.337 Thread-28: ServerControl.isPackageRequired: packageName=minimserver-0.8-update-66
16:20:18.337 Thread-28: isPackageRequired: minimserver-0.8-update-66 is already installed
16:20:18.338 Thread-28: ServerControl.checkOffer: updateFile=minimstreamer-0.5.jmupd
16:20:18.338 Thread-28: getUpdatePackages: updateFile=minimstreamer-0.5.jmupd
16:20:19.244 AWT-EventQueue-0: setLogFileChooser: current=null chooser=com.minimserver.lib.TrayControl$TrayView$62[,0,0,0x0,invalid,layout=java.awt.BorderLayout,alignmentX=0.5,alignmentY=0.0,bord​er=sun.swing.plaf.synth.SynthFileChooserUI$UIBorder@11a0ff1,flags=320,maximumSiz​e=,minimumSize=,preferredSize=,approveButtonText=,currentDirectory=/home/nick,dialogTitle=MinimWatch: Save log as file,dialogType=OPEN_DIALOG,fileSelectionMode=FILES_ONLY,returnValue=ERROR_OPTIO​N,selectedFile=,useFileHiding=true]
16:20:19.246 AWT-EventQueue-0: getSaveLogFile: calling showSaveDialog
16:20:20.252 Thread-28: ServerControl.isPackageRequired: packageName=minimstreamer-0.5.13
16:20:20.252 Thread-28: isPackageRequired: minimstreamer-0.5.13 is already installed
16:20:20.252 Thread-28: ServerConsole.doCheckUpdates: removing update view for MinimServer[QNAP-TS-109]
16:20:20.252 Thread-28: ServerConsole.doCheckUpdates: updateViews is empty
16:22:41.467 AWT-EventQueue-0: getSaveLogFile: showSaveDialog returned 0
This log shows a normal startup with the tray icon being created successfully.

You could get this message if the Gnome desktop is not running 10 seconds after MinimWatch has been started automatically when booting the machine. MinimWatch tries to create the tray icon 10 times with a one-second delay between each attempt. Can you time the startup to see how long it takes for the Gnome desktop to appear after booting the machine?
Thanks. I'll time it next time I boot up, which will probably be Thursday morning, as I'm preparing for a trip away right now. I'm pretty certain it takes more than 10 seconds, though, certainly if timing from the moment I click on the grub menu. Or should I time from the moment of login? Even then it probably takes more than ten seconds to the moment the panel indicator icons and launchers for other applications start popping up. Is there a tweak I can do to a config file to increase the number of tries?
(27-07-2015 17:46)nickc Wrote: [ -> ]Thanks. I'll time it next time I boot up, which will probably be Thursday morning, as I'm preparing for a trip away right now. I'm pretty certain it takes more than 10 seconds, though, certainly if timing from the moment I click on the grub menu. Or should I time from the moment of login? Even then it probably takes more than ten seconds to the moment the panel indicator icons and launchers for other applications start popping up. Is there a tweak I can do to a config file to increase the number of tries?

If automatic startup and desktop integration is enabled for MinimWatch, the 10-second interval should start when the desktop is being initialized after login.

If you are logging in manually as soon as the system boots up, it is possible that desktop initialization is being slowed down by other startup activity. This might trigger the problem.

The first step is to confirm the cause of the problem. After that, we can discuss possible solutions.
"If you are logging in manually as soon as the system boots up, it is possible that desktop initialization is being slowed down by other startup activity. This might trigger the problem.

The first step is to confirm the cause of the problem. After that, we can discuss possible solutions."

OK. Thanks. I am logging in manually, so this morning I timed from clicking "enter" for my password. The results were as follows:

14 secs to appearance of wallpaper image
36 secs desktop icons begin to appear
56 secs top panel appears
1min 21 secs MinimWatch startup error message appears

I don't really need to login manually - just habit! I'll try setting login to automatic and see if that makes a difference.
(31-07-2015 09:48)nickc Wrote: [ -> ]OK. Thanks. I am logging in manually, so this morning I timed from clicking "enter" for my password. The results were as follows:

14 secs to appearance of wallpaper image
36 secs desktop icons begin to appear
56 secs top panel appears
1min 21 secs MinimWatch startup error message appears

I don't really need to login manually - just habit! I'll try setting login to automatic and see if that makes a difference.

For me (on Ubuntu 14.04 with Unity), the wallpaper image is already showing when I get the login prompt and everything else happens within less than 20 seconds after I log in. What machine are you using and which versiion of Java (Oracle or OpenJDK) do you have installed?
"For me (on Ubuntu 14.04 with Unity), the wallpaper image is already showing when I get the login prompt and everything else happens within less than 20 seconds after I log in. What machine are you using and which versiion of Java (Oracle or OpenJDK) do you have installed?"

As I mentioned in my original post, I'm running Ubuntu 12.04 with Classic Gnome desktop. The pc is very old now - I built it myself. MSI Neo 865PE mobo, Pentium 4 (Northcott) 3ghz cpu, 2gb RAM, mix of IDE and SATA hard drives. Re Java:

nick@nick-build-1:~$ java -version
java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.5) (7u79-2.5.5-0ubuntu0.12.04.1)
OpenJDK Client VM (build 24.79-b02, mixed mode, sharing)

Setting login to auto doesn't help, by the way, as I still get a prompt that I have to click on, just don't have to enter a password. I thought there was a setup whereby everything happened automatically from the moment of booting the machine, but I haven't (yet) found how to configure that.
(03-08-2015 14:13)nickc Wrote: [ -> ]As I mentioned in my original post, I'm running Ubuntu 12.04 with Classic Gnome desktop. The pc is very old now - I built it myself. MSI Neo 865PE mobo, Pentium 4 (Northcott) 3ghz cpu, 2gb RAM, mix of IDE and SATA hard drives. Re Java:

nick@nick-build-1:~$ java -version
java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.5) (7u79-2.5.5-0ubuntu0.12.04.1)
OpenJDK Client VM (build 24.79-b02, mixed mode, sharing)

Setting login to auto doesn't help, by the way, as I still get a prompt that I have to click on, just don't have to enter a password. I thought there was a setup whereby everything happened automatically from the moment of booting the machine, but I haven't (yet) found how to configure that.

This version of Java should perform adequately on your system.

I would like to see a debug log of the startup failure. Please set the MinimWatch logging level to Debug, then reboot the machine so that you get the tray icon error. When you get the error, don't restart MinimWatch from the desktop launch icon. Intead, zip the minimwatch.log file and attach it (as a file attachment) to a post here. Many thanks!
(03-08-2015 15:31)simoncn Wrote: [ -> ]
(03-08-2015 14:13)nickc Wrote: [ -> ]As I mentioned in my original post, I'm running Ubuntu 12.04 with Classic Gnome desktop. The pc is very old now - I built it myself. MSI Neo 865PE mobo, Pentium 4 (Northcott) 3ghz cpu, 2gb RAM, mix of IDE and SATA hard drives. Re Java:

nick@nick-build-1:~$ java -version
java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.5) (7u79-2.5.5-0ubuntu0.12.04.1)
OpenJDK Client VM (build 24.79-b02, mixed mode, sharing)

Setting login to auto doesn't help, by the way, as I still get a prompt that I have to click on, just don't have to enter a password. I thought there was a setup whereby everything happened automatically from the moment of booting the machine, but I haven't (yet) found how to configure that.

This version of Java should perform adequately on your system.

I would like to see a debug log of the startup failure. Please set the MinimWatch logging level to Debug, then reboot the machine so that you get the tray icon error. When you get the error, don't restart MinimWatch from the desktop launch icon. Intead, zip the minimwatch.log file and attach it (as a file attachment) to a post here. Many thanks!

OK. Thanks. MinimWatch log file attached as requested. Before rebooting I saved then cleared the current log, so what's here should just relate to the most recent reboot and error message.

In poking around I just noticed a whole load of minimserver-crash-logs on the public share of the QNAP. I don't know if these have any bearing - I've not been aware of minimserver crashing; it's been very reliable - but I've taken the liberty of attaching the most recent of these logs too.
(04-08-2015 12:11)nickc Wrote: [ -> ]OK. Thanks. MinimWatch log file attached as requested. Before rebooting I saved then cleared the current log, so what's here should just relate to the most recent reboot and error message.

In poking around I just noticed a whole load of minimserver-crash-logs on the public share of the QNAP. I don't know if these have any bearing - I've not been aware of minimserver crashing; it's been very reliable - but I've taken the liberty of attaching the most recent of these logs too.

Thanks for these files. The log confirms that MinimWatch autostart has delayed for 10 seconds waiting for the GNOME desktop to become available and has given up waiting because the desktop wasn't available after 10 seconds.

Until a fix is available, you can work around this by editing the file

~/.config/autostart/minimwatch.desktop

and adding the line

X-GNOME-Autostart-Delay=10

This will delay for an additional 10 seconds before MinimWatch is started. If the value 10 isn't sufficient to ensure reliable startup after a reboot, you can increase this value to 15 or 20 (etc.) as needed. Please let me know what is the minimum value that enables MinimWatch to autostart reliably on your system.

The crash file indicates that MinimStreamer encountered an end-of-data condition while reading a BBC HLS stream. This is unexpected but it isn't a problem in MinimServer or MinimStreamer and therefore it shouldn't produce a MinimServer crash file. I will fix this in the next update to MinimStreamer.
Pages: 1 2
Reference URL's