This article lists bugs which you and I have encountered in macOS Mojave 10.14.2 itself, rather than issues in specific third-party applications and other software.
System Information – Legacy Software wrong and misleading
The information given about ‘legacy software’ in System Information is highly incomplete and misleading. Further details are here. Use 32-bitCheck (from Downloads above) instead.
Note that you cannot rely on Mojave to warn you of 32-bit software when you open an app: that only happens on the first occasion that an app is run after it has been downloaded from the internet. Existing installed apps generated no such warnings.
About This Mac – Storage bar often absurdly incorrect
This isn’t a new bug, but has been present since the introduction of the Storage tab in the About This Mac dialog many moons ago. Figures reported are often absurdly incorrect.
For example, this 1 TB internal SSD is reported as being just under half full, but its bar is almost completely full with a claimed 780 GB of ‘Documents’. In this case, it may result from the fact that the volume contains an alias to an external SSD on which there is an additional 700 GB of ‘documents’, which are somehow being included in the total for the internal SSD despite the obvious numerical impossibility.
I recommend users never to trust what Storage reports, but to believe the Finder and Disk Utility instead, although even they don’t seem to cope well always with APFS.
EFI version numbers – System Information and
eficheck return different numbers
In 10.14.1 and 10.14.2, the EFI firmware version number returned in System Information has the form
22.214.171.124.0, but that returned by
eficheck commands such as
/usr/libexec/firmwarecheckers/eficheck/eficheck --integrity-check are different in form and content, e.g.
App Store – search returns weird hits
When you enter some search terms into the App Store app, completely unrelated apps appear in the results. In some cases, these are additional to genuine hits, in others they just appear weird and unrelated. For example, searching on the word
consommé (a type of soup) consistently returns an app which has nothing whatsoever to do with the word, nor does it appear in the info provided about the app.
clover returns three genuine hits, and three spurious apps which are completely unrelated. This looks like the store’s metadata are corrupted with random terms.
TextEdit – colours displayed differently with Dark Background
Colours used to display text are changed when Dark Background is enabled. If you save or copy Rich Text in that display mode, the colours saved or copied are very likely to differ from those shown. To avoid this, don’t use Dark Background when you’re using colour.
This and other problems are discussed in detail here.
Dark Mode – QuickLook and other bugs
If you use an editor such as my DelightEd which is designed to produce RTF which ‘works’ in Dark as well as Light Mode, then QuickLook thumbnails and previews switch contained text to white in Dark Mode, but retain a white background. This renders the thumbnail/preview useless in Dark Mode.
A similar problem with Dark Mode exists when you use Control-Command-D to show the definition of a selected word: the popover window is semi-transparent, which makes text in custom dictionaries visible only when viewed over a window with a white background. If the underlying window is dark grey, then that text is almost invisible.
These are described in more detail here. There don’t appear to be any workarounds for these, other than switching back to Light Mode.
Thanks to Artyom for drawing my attention to the second of these.
Safari – errors opening local Home page, and others
If you set Safari 12.0.2 to open a local file as its Home page, this may cause an error when Safari first opens, and that error may in turn result in another error reporting that the error page can’t be found. Others also report Safari’s inability to search until a remote page has been loaded, and other potentially related issues. These are detailed here (see the comments there in particular).
Once Safari has started up and connected to a remote page, these problems usually vanish, so can be safely ignored. They also appear to occur most commonly when the Develop menu is enabled; turning that off may make them disappear, but you then lose the additional features of that menu. This bug was present in 12.0 and persists in 12.0.1.(Thanks to Manoli for pointing this out.)
Font Book – can’t disable or remove fonts in /Library/Fonts
Although Font Book used to be able to, and its Help book still claims that it can, since 10.14 (including 10.14.1) it has been unable to disable or remove any font stored in /Library/Fonts. It can currently only disable or remove those in ~/Library/Fonts.
The well-known workaround is to create the folder /Library/Fonts (disabled), or similar, and move fonts to that folder to disable them.
Appearance – grey/gray accent turns ‘traffic lights’ grey too
In the General pane, set the Accent colour to grey. Whether in Light or Dark mode, the ‘traffic lights’ at the top left of every window then show just three grey lights instead. Now which end was red?!
The only workaround is not to use the grey accent.
(Thanks to simweb for reporting this below.)
Finder – incorrect column width
This can occur when using Finder windows which are set to column view. When switching folder in the view, the rightmost column being displayed has excessive width, filling the Finder window, its divider being placed incorrectly at the right edge of that window.
This long-standing but intermittent bug dates back to Mavericks if not earlier, and I have whinged about it here and here. It was also present in every version of El Capitan, Sierra and High Sierra. The only workaround is to select a different folder, then to select the correct folder again.
Bugs known to have been fixed from 10.14.1
(Not updated yet since initial posting.)