It seems to me that banshee (and maybe other apps) is concerned by this bug : [bellet@bonobo ~]$ banshee Unhandled Exception: System.TypeInitializationException: The type initializer for 'System.Console' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.ConsoleDriver' threw an exception. ---> System.Exception: Magic number is wrong: 542 at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x0002b] in <373b6e083d6e45e498c9082a8eebd27f>:0 [...] That bug seems to be related to mono, not handling newer terminfo2 file format. https://stackoverflow.com/questions/49242075/mono-bug-magic-number-is-wrong-542 https://github.com/mono/mono/commit/2c1f45f3791f274855e0f5fd2fb0af71c9a756f7 The fix to define TERM=xterm instead of my default (xterm-256color) works in my case.
see related bug 1580447. This was fixed in Fedora 28, but for Fedora 29 and rawhide we cannot build new packages at the moment due to bug 1588734 with a segfault for ppc64le.
This has been fixed in Rawhide and Fedora 30, with Mono 5.18 It probably still exists in Fedora 29, because we did not rebuild Mono for Fedora 29 for the reason that Mono 4.8 does not build on ppc64le.
*** Bug 1664088 has been marked as a duplicate of this bug. ***
The mono package still fails to build on Fedora 29 for ppc64le. If we would exclude the arch ppc64le, we would cause more trouble for other packages depending on it. Since there is a workaround for F29, and it is fixed since F30, I will close this bug.