Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 530781

Summary:	[GTK] assertion 'in != NULL' failed
Product:	[Eclipse Project] Platform	Reporter:	Karsten Thoms <karsten.thoms>
Component:	SWT	Assignee:	Platform-SWT-Inbox <platform-swt-inbox>
Status:	RESOLVED NOT_ECLIPSE	QA Contact:
Severity:	normal
Priority:	P3	CC:	akurtakov, bernd.hufmann, filipe.silva, gustavo_l_walker, m.kurz, murskt
Version:	4.7.2
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Karsten Thoms

2018-02-06 08:09:59 EST

When running Eclipse from command line (using Eclipse Oxygen.2 CPP bundle) the following message is printed several times to the console:

   (Eclipse:54341): GLib-CRITICAL **: g_base64_encode_step: assertion 'in != NULL' failed

Comment 1 Alexander Kurtakov

2018-02-15 11:47:20 EST

g_base64_encode_step is not used directly inside SWT. Which distribution is this? If not using Adwaita GTK theme can you please try running with it so we can verify this is not warning coming from the GTK theme used?

Comment 2 Karsten Thoms

2018-02-15 11:49:05 EST

This happened on Ubuntu 17.10.

Comment 3 Filipe Silva

2018-05-13 11:42:25 EDT

This happens with Ambiance theme but not with Adwaita. I'm using Ubuntu 18.04.

Comment 4 Dani Megert

2018-06-06 06:34:42 EDT

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

Comment 5 Alexander Kurtakov

2018-07-13 08:31:48 EDT

SWT doesn't call g_base64_encode_step directly . As this is seen with Ambience (Ubuntu theme) it should be reported to the respective developers. Nothing can be done on SWT side to prevent it.

Comment 6 Eric Williams

2019-06-20 16:21:55 EDT

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