Comment 13 for bug 40683

On Tuesday 25 April 2006 00:51, Simon Edwards wrote:
> My apologies, that's a lame bug. Until the next release is out you can
> just open up the displayconfig-restore.py file and look for the line
> containing syslog and remove it or comment it out.
Perhaps... but the developer took it seriously enough to hunt down the
cause ..and it was the *absence* of the import statement. Not
everyone --meaning, obviously, "myself"-- is so script-savvy as yourself,
unfortunately. Some of us need more help than others. It's that tolerance
that has made this community what it is. I had my belly-full of forums that
snort at those who don't know as much as they do ...and state it publicly on
the forums. THIS DOES NOT INCLUDE YOU. Thank you that. :-)
--
 ...CH