Because of the problem in #481409. we understood that we need to validate utf8 asap (_InotifyProcessor and LocalRescan), so there's no further point that will handle wrong strings (in that bug, FSM had the bad path, and that caused a dbus message to crash).
Because of the problem in #481409. we understood that we need to validate utf8 asap (_InotifyProcessor and LocalRescan), so there's no further point that will handle wrong strings (in that bug, FSM had the bad path, and that caused a dbus message to crash).