Description of problem: See upstream report and patches: https://github.com/mono/mono/issues/6752 Basically anything involving mono crashes under fedora 28 in gnome-terminal. A work around exists by setting TERM=xterm . Version-Release number of selected component (if applicable): mono-4.8.0-12.fc28.x86_64 How reproducible: always. Steps to Reproduce: 1. just try anothing (mcs, for example) in a gnome-terminal 2. 3. Actual results: ... 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 Expected results: works. Additional info: Upstream issue and patches: https://github.com/mono/mono/issues/6752
*** Bug 1585271 has been marked as a duplicate of this bug. ***
*** Bug 1576608 has been marked as a duplicate of this bug. ***
mono-4.8.0-14.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-880e05ebc4
mono-4.8.0-14.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-880e05ebc4
mono-4.8.0-14.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1591094 has been marked as a duplicate of this bug. ***
So, what command should work? Either: sudo dnf install mono --enablerepo=updates-testing or sudo dnf upgrade-minimal mono is returning: No match for argument: mono Error: Unable to find a match
the package that has the newer update is mono-core sudo dnf update mono-core You can test if you already have the latest version: rpm -qa | grep mono-core The latest version is: mono-core-4.8.0-14.fc28
*** Bug 1638467 has been marked as a duplicate of this bug. ***
*** Bug 1648630 has been marked as a duplicate of this bug. ***