- User Since
- Apr 27 2019, 1:58 AM (29 w, 3 d)
May 5 2019
Sorry for the delay... I was finally able to get the crashing machine set up again.
Ordering changed, qWarning first.
job->errorString() displayed for all values of job->error().
A QString object was created, so job is no longer passed to KMessageBox.
Apr 29 2019
Thanks for the clarification! I understand what you are saying :)
The API for errorString() calls out that it should not be called when error() == 0. The code does not explicitly check for this scenario.
@anthonyfieroni Yes, I think there also an issue with KAuth here. This machine never gets to the auth prompt, which works fine on another machine.
Apr 27 2019
It looks like my alternate error "unknown error" isn't showing up in the dialog... So this isn't quite right yet.