Bug 1659050

Summary:	System.Exception: Magic number is wrong: 542
Product:	[Fedora] Fedora	Reporter:	Fabrice Bellet <fabrice>
Component:	mono	Assignee:	Timotheus Pokorra <mailinglists>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	29	CC:	chkr, gkaukola, itamar, john.j5live, lxtnow, mailinglists, mbarnes, pokorra.mailinglists, rhughes, rstrode, sandmann
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-14 19:10:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1588734
Bug Blocks:

Description Fabrice Bellet 2018-12-13 13:27:34 UTC

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.

Comment 1 Timotheus Pokorra 2019-01-02 06:26:15 UTC

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.

Comment 2 Timotheus Pokorra 2019-07-08 05:08:30 UTC

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.

Comment 3 Timotheus Pokorra 2019-07-08 05:09:41 UTC

*** Bug 1664088 has been marked as a duplicate of this bug. ***

Comment 4 Timotheus Pokorra 2019-08-14 19:10:48 UTC

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.