FS#57718 - [mono] Incompatible with ncurses 6

Attached to Project: Arch Linux
Opened by Balló György (City-busz) - Monday, 05 March 2018, 10:55 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 16 May 2018, 03:31 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Levente Polyak (anthraxx)
Giancarlo Razzolini (grazzolini)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Currently some mono applications (e.g. pdfmod) fail to start and trow an exception, because System.TermInfoReader cannot handle new NCurses 6 TermInfo files.

Upstream report:
https://github.com/mono/mono/issues/6752

Merged fix:
https://github.com/mono/mono/pull/6960
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 16 May 2018, 03:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  mono 5.10.1.47-1
Comment by Balló György (City-busz) - Monday, 05 March 2018, 11:05 GMT
It trows an exception only when I run it from GNOME Terminal command line, but works when I start it with the desktop launcher.
Comment by Eli Schwartz (eschwartz) - Monday, 05 March 2018, 21:04 GMT
Looks like they also backported this into their maintenance branch.
Comment by Michael Healy (horsemanoffaith) - Tuesday, 13 March 2018, 04:48 GMT
I get this error when I try to build libappindicator-ubuntu in gnome-terminal:

[code]
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) [0x00028] in <a84b655e5e6a49ee96b338ec792f5580>:0
at System.TermInfoReader..ctor (System.String term, System.String filename) [0x0005f] in <a84b655e5e6a49ee96b338ec792f5580>:0
at System.TermInfoDriver..ctor (System.String term) [0x00055] in <a84b655e5e6a49ee96b338ec792f5580>:0
at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <a84b655e5e6a49ee96b338ec792f5580>:0
at System.ConsoleDriver..cctor () [0x0004d] in <a84b655e5e6a49ee96b338ec792f5580>:0
--- End of inner exception stack trace ---
at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00007] in <a84b655e5e6a49ee96b338ec792f5580>:0
at System.Console..cctor () [0x0008e] in <a84b655e5e6a49ee96b338ec792f5580>:0
--- End of inner exception stack trace ---
at GtkSharp.Parsing.Parser.Main (System.String[] args) [0x00304] in <c4eb2506e07247d8bab73dbe24461e2e>:0
[ERROR] FATAL 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) [0x00028] in <a84b655e5e6a49ee96b338ec792f5580>:0
at System.TermInfoReader..ctor (System.String term, System.String filename) [0x0005f] in <a84b655e5e6a49ee96b338ec792f5580>:0
at System.TermInfoDriver..ctor (System.String term) [0x00055] in <a84b655e5e6a49ee96b338ec792f5580>:0
at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <a84b655e5e6a49ee96b338ec792f5580>:0
at System.ConsoleDriver..cctor () [0x0004d] in <a84b655e5e6a49ee96b338ec792f5580>:0
--- End of inner exception stack trace ---
at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00007] in <a84b655e5e6a49ee96b338ec792f5580>:0
at System.Console..cctor () [0x0008e] in <a84b655e5e6a49ee96b338ec792f5580>:0
--- End of inner exception stack trace ---
at GtkSharp.Parsing.Parser.Main (System.String[] args) [0x00304] in <c4eb2506e07247d8bab73dbe24461e2e>:0
[/code]

This looks to be related to this bug.
Comment by Michael Healy (horsemanoffaith) - Tuesday, 13 March 2018, 04:48 GMT
If I issue TERM=xterm, the package builds successfully in gnome-terminal.
Comment by Balló György (City-busz) - Friday, 23 March 2018, 22:59 GMT
  • Field changed: Percent Complete (100% → 0%)
Still not fixed in mono 5.10.0.179-1, a patch needs to be applied. The fix is not backported yet for the current stable branch (2017-12), only for the unstable 2018-02 branch, which will be available in the 5.12.x releases only.
Comment by Han Prower (HanFox) - Tuesday, 15 May 2018, 15:47 GMT
Has anyone tried mono 5.12 that was released on 4th May which I was under the impression included the fix?

I installed it via the bz2 from their download archives and still get the same error. I'm a little confused as the upstream bug report seems to have gone quiet after the fix was merged.

mono -V
Mono JIT compiler version 5.12.0.226 (tarball Tue 15 May 16:03:54 BST 2018)
Comment by Balló György (City-busz) - Tuesday, 15 May 2018, 22:53 GMT
It was fixed in mono 5.10.1.47.

Loading...