https://bugs.kde.org/show_bug.cgi?id=171052
Alexander Patrakov <patra...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO |WORKSFORME
--- Comment #5 from Alexander Patrakov <patra...@gmail.com> ---
I have tried to reproduce the bug on today's KDE Neon image, and here are my
findings:
1) It is still possible to provoke a mount error by including bad options in
/etc/fstab. So the test case can still be executed.
2) Instead of calling mount directly, now (judging by the error message text)
disk mounting on Linux goes through udisks2.
3) All error messages about mounting come from udisks2 via dbus.
4) Error messages that go through dbus are not marked for translation in
udisks2 source code, and do not contain any non-ASCII characters.
Therefore, the code that displays mounting errors never receives input that
could provoke visible encoding-conversion errors, and thus black-box testing is
no longer possible. I tried and failed to look in the code whether it goes
through QString::fromLatin1() or not.
As the bug, even if it in fact still exists, can no longer be triggered, let's
resolve this as WORKSFORME.
--
You are receiving this mail because:
You are watching all bug changes.
