https://bugs.kde.org/show_bug.cgi?id=524724
--- Comment #4 from [email protected] --- It kind of sounds like an initialization order problem to me, which could randomly happen in our builds as well and simply luck that it didn't so far. But since it's not reproducible in the official builds, more information is needed from somebody that can reproduce it, a stack trace could already be enough and it may not be necessary to contact the packagers. If you can't manage to get a trace or it's not enough, then we'd probably need their assistance, since they have the setup that lets them track it down. -- You are receiving this mail because: You are watching all bug changes.
