Perhaps this is helpful, as well: it's not anything new that I installed. Whatever it is, it was triggered either by an update to an existing package around late December/early January from the default Fedora RPM repositories. Perhaps by cross-checking that with APT, we can determine which package/version introduced the bug.
Perhaps this is helpful, as well: it's not anything new that I installed. Whatever it is, it was triggered either by an update to an existing package around late December/early January from the default Fedora RPM repositories. Perhaps by cross-checking that with APT, we can determine which package/version introduced the bug.