Cool! Thanks a lot for this detailed information. Seems like we have two options: - I can write a patch that fixes the problem for now. - Also I have resolved the problem upstream, which means the next upstream release [which will take place in the next few weeks] will fix this bug along with others. Which will save some work for getting the patch into debian, but would mean that the bug is present a few weeks longer than necessary.
If you say the 1st option is better (I guess you will) this weekend I'll write the patch. Thanks again, and Kind regards, Gunter.
