Chat tab turns into Red X

[IouSASTU]

Discussed in #55

^{Originally posted by IouSASTU May 24, 2024}
Hello, I'm using version 2.41 of Radegast and using it on ubuntu with mono 6.12. If somebody posts a link with an image, the chat tab window turns into a red X. From the terminal window that I started Radegast I see this error message:

Error decoding image: OpenJpegDotNetNative assembly: type: member:(null)

Is there a way to fix this, or even is there a way to close the failed image render to get back to the chat.

https://i.imgur.com/pUVoTNt.png <-- Screenshot.

Thanks for any tips.

[IouSASTU]

[Update] Upgraded from Ubuntu 22.04.4 LTS to 24.04.1 LTS. Version of Radegast and mono unchanged. The issue of parts of the UI turning to red x's has not happened since upgrading.

[RubyMaelstrom]

This red X issue occurs constantly on Linux now. It is easily reproducible also: Every time that a user sends an emoji to a chat, whether it is Nearby Chat, a group, or an IM, the window crashes and becomes a red X as is shown in the screenshot IouSASTU linked above.

[IouSASTU]

This red X issue occurs constantly on Linux now. It is easily reproducible also: Every time that a user sends an emoji to a chat, whether it is Nearby Chat, a group, or an IM, the window crashes and becomes a red X as is shown in the screenshot IouSASTU linked above.

It's been a month, and now that I'm on Ubuntu 24.04.1 LTS from the previous LTS, this issue has not returned. Using the latest full install of mono.

[RubyMaelstrom]

Thanks IouSASTU, but with my comment I meant that I am still having this issue. I am having the "Red X" problem both on EndeavourOS and SteamOS (both are versions of Arch Linux). I have attached screenshots to display the issue and how easy it is to reproduce.

[IouSASTU]

Thanks IouSASTU, but with my comment I meant that I am still having this issue. I am having the "Red X" problem both on EndeavourOS and SteamOS (both are versions of Arch Linux). I have attached screenshots to display the issue and how easy it is to reproduce.

Are you using mono or wine to run radegast on Arch?

For me the combo that finally was stable, that did not create the red x problem, was current Ubuntu LTS and the current version of mono.

[RubyMaelstrom]

Thanks for trying to help, I am using the current version of mono.

Here are the errors which Radegast throws when an emoji is used in chat:

07:16:01 [ERROR]: - <Ruby Maelstrom>: Unhandled thread exception: Generic Error [GDI+ status: GenericError]
  at System.Drawing.GDIPlus.CheckStatus (System.Drawing.Status status) [0x00079] in <d2cf6374537744cabc5dae479f1fbd9b>:0 
  at System.Drawing.Graphics.FillRectangle (System.Drawing.Brush brush, System.Single x, System.Single y, System.Single width, System.Single height) [0x00025] in <d2cf6374537744cabc5dae479f1fbd9b>:0 
  at (wrapper remoting-invoke-with-check) System.Drawing.Graphics.FillRectangle(System.Drawing.Brush,single,single,single,single)
  at System.Windows.Forms.Document.Draw (System.Drawing.Graphics g, System.Drawing.Rectangle clip) [0x0056d] in <c87c1b414e134a3b85f757beb69a2505>:0 
  at System.Windows.Forms.TextBoxBase.Draw (System.Drawing.Graphics g, System.Drawing.Rectangle clippingArea) [0x0000d] in <c87c1b414e134a3b85f757beb69a2505>:0 
  at System.Windows.Forms.TextBoxBase.OnPaintInternal (System.Windows.Forms.PaintEventArgs pevent) [0x0000d] in <c87c1b414e134a3b85f757beb69a2505>:0 
  at System.Windows.Forms.Control.WmPaint (System.Windows.Forms.Message& m) [0x0006d] in <c87c1b414e134a3b85f757beb69a2505>:0 
  at System.Windows.Forms.Control.WndProc (System.Windows.Forms.Message& m) [0x001a4] in <c87c1b414e134a3b85f757beb69a2505>:0 
  at System.Windows.Forms.TextBoxBase.WndProc (System.Windows.Forms.Message& m) [0x001c5] in <c87c1b414e134a3b85f757beb69a2505>:0 
  at System.Windows.Forms.RichTextBox.WndProc (System.Windows.Forms.Message& m) [0x00000] in <c87c1b414e134a3b85f757beb69a2505>:0 
  at Radegast.ExtendedRichTextBox.WndProc (System.Windows.Forms.Message& m) [0x000b2] in <21355fc948c642aa921ecc2ebad989c6>:0 
  at System.Windows.Forms.Control+ControlWindowTarget.OnMessage (System.Windows.Forms.Message& m) [0x00000] in <c87c1b414e134a3b85f757beb69a2505>:0 
  at System.Windows.Forms.Control+ControlNativeWindow.WndProc (System.Windows.Forms.Message& m) [0x0000b] in <c87c1b414e134a3b85f757beb69a2505>:0 
  at System.Windows.Forms.NativeWindow.WndProc (System.IntPtr hWnd, System.Windows.Forms.Msg msg, System.IntPtr wParam, System.IntPtr lParam) [0x00085] in <c87c1b414e134a3b85f757beb69a2505>:0 

[IouSASTU]

Thanks for trying to help, I am using the current version of mono.

The red X's is mono failing to render a Windows form. In my case it was caused by an issue with the OS, and updating to the current LTS fufilled whatever dependency issue I was having. I did not have this problem on Fedora, but for me now both are stable.

Fedora maintains a full mono package, and I've used it with success - I can install mono-complete. Official mono supports debian based linux's and you can do a mono-complete install. But for Arch I only see mono. I assume you did this to install mono:

sudo pacman -S mono

I can't find anything to confirm that this package is equivalent to mono-complete.

https://www.mono-project.com/download/stable/#download-lin-ubuntu <-- see the install options to see what I mean by the choice of mono-complete, compared to the other install options.

So, I'm not sure if the problem is coming from the install of mono or the underlying OS. I only use Fedora and Ubuntu, so I'm not much help to troubleshoot Arch. You might have more luck in the Arch support forums to ask about how to achieve a mono-complete install.