Just tested the binaries in proposed by:
* installing latest saucy-proposed image (101)
* adb shell-ing into device
* remounting rw
* installing debs by hand
* remounting ro
* rebooting
Then tested by:
* installing a Click package from appstore; confirmed that /home/phablet/.cache/ubuntu-download-manager/ubuntu-download-manager/ubuntu-download-manager.log had no debug log; in fact it only had a known broken signal connection:
2013-11-26 16:10:28,564 - WARNING - QObject::connect: No such signal SystemNetworkInfo::onlineStateChange(bool)
* upgrading to trusty (system-image-cli -c trusty-proposed -b 0); confirmed that syslog had no debug output; however note that it had no output at all (not even the above WARNING), which is probably due to a known bug with syslog handling of warning messages in download-manager; I ended up on trusty-proposed (31)
Just tested the binaries in proposed by:
* installing latest saucy-proposed image (101)
* adb shell-ing into device
* remounting rw
* installing debs by hand
* remounting ro
* rebooting
Then tested by: .cache/ ubuntu- download- manager/ ubuntu- download- manager/ ubuntu- download- manager. log had no debug log; in fact it only had a known broken signal connection: fo::onlineState Change( bool)
* installing a Click package from appstore; confirmed that /home/phablet/
2013-11-26 16:10:28,564 - WARNING - QObject::connect: No such signal SystemNetworkIn
* upgrading to trusty (system-image-cli -c trusty-proposed -b 0); confirmed that syslog had no debug output; however note that it had no output at all (not even the above WARNING), which is probably due to a known bug with syslog handling of warning messages in download-manager; I ended up on trusty-proposed (31)
(IOW, this all worked fine)