https://bugs.kde.org/show_bug.cgi?id=417108
--- Comment #12 from David Jarvie <djar...@kde.org> --- I suspect that the QObject::disconnect errors probably come from inside QCommandLineParser rather than KAlarm itself, although I can't be sure. Certainly, there isn't any obvious place in KAlarm where a set of four such errors could be generated together. I've looked at your recordings, and tried running the same scripts (also on a Neon system), but I have been unable to reproduce the errors which you have seen. The command "kalarm -v" doesn't produce the error for me either. So there must be some difference between our systems which is causing the different results - one possibility is because I'm running a slightly older version of Qt. Unfortunately, until I'm able to update my Neon system (which will mess up my current development setup), it's difficult to know how I can investigate this further, and given that you are not a developer, I can't think of how you could help either. I'll look at this again once I do update my system. -- You are receiving this mail because: You are watching all bug changes.
