On Wed, 2013-04-24 at 14:10 +0000, Mathieu Trudel-Lapierre wrote:
> I understand the usefulness for debugging, but I strongly feel we should avoid having G_MESSAGES_DEBUG set in the upstart job. This is so likely to just get forgotten and left in ;)
>
> No point in spamming .xsession-errors
See, and now you see the beauty of upstart user session. It WON'T spam
xsession-errors because it only puts the log from that job in
~�.cache�upstart�indicator-network.log and we can then attach that in
the apport hook. So we can avoid the xession-errors issue *and* get
good bug reports!
On Wed, 2013-04-24 at 14:10 +0000, Mathieu Trudel-Lapierre wrote:
> I understand the usefulness for debugging, but I strongly feel we should avoid having G_MESSAGES_DEBUG set in the upstart job. This is so likely to just get forgotten and left in ;)
>
> No point in spamming .xsession-errors
See, and now you see the beauty of upstart user session. It WON'T spam upstart� indicator- network. log and we can then attach that in
xsession-errors because it only puts the log from that job in
~�.cache�
the apport hook. So we can avoid the xession-errors issue *and* get
good bug reports!