Comment 7 for bug 41780

The difficulty here is not that I cannot reproduce the bug, but that everytime I run under gdb, whether setuid or not, I get a slightly different backtrace from the crash. I can repeat this with the repository version, or with a local version with debug symbols. When running the version from the repositories setuid, everything works, and when running without setuid, it crashes.

Upstream recommends running setuid, and has patched as described above (which works when compiled). As a result, I do not expect that distribution-level effort will have lasting value.