Bug#813728: boinc-client: spews "No protocol specified" every second when active

2018-06-14 Thread Aaron M. Ucko
Preston Maness writes: > I can just do a poor man's timer with a decrement counter, only > retrying failing DISPLAYs every $number of minutes, which would ease > up on the amount of entries at least. Thanks for looking into this report, and sorry for missing your followups. (Copying me would

Bug#813728: boinc-client: spews "No protocol specified" every second when active

2016-02-04 Thread Preston Maness
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Howdy howdy, I suspect this is related to XOpenDisplay() calls failing during idle detection (due to the Xserver being inaccessible for some reason). It shouldn't be harming performance of the boinc-client in any way, but I'll look into suppressing

Bug#813728: boinc-client: spews "No protocol specified" every second when active

2016-02-04 Thread Preston Maness
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Ugh. There's no clean way to do this that I can find, especially given BOINC's custom handling of stdout and stderr. The closest solution I've found that actually starts to be (thread, context, etc) safe is her e:

Bug#813728: boinc-client: spews "No protocol specified" every second when active

2016-02-04 Thread Aaron M. Ucko
Package: boinc-client Version: 7.6.22+dfsg-3 Severity: minor Since upgrading to boinc-client 7.6.22+dfsg-3 last night (when it hit testing), I've observed it to log "No protocol specified" once a second, except when suspended, per the log excerpt below. As far as I can tell, it otherwise