Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 548479 - [GTK 3.22.30] GLib-CRITICAL: g_base64_encode_step: assertion 'in != NULL' failed
Summary: [GTK 3.22.30] GLib-CRITICAL: g_base64_encode_step: assertion 'in != NULL' failed
Status: CLOSED DUPLICATE of bug 530781
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.12   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-20 15:56 EDT by Bernd Hufmann CLA
Modified: 2019-06-20 16:21 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bernd Hufmann CLA 2019-06-20 15:56:30 EDT 
Using Eclipse EPP for Committers version 2019-06, I get the error messages below after starting Eclipse on command-line from a terminal. 

My laptop run environment is:
 Linux Ubuntu 18.04
 GTK3 3.22.30
 Theme Ambiance

(Eclipse:23858): GLib-CRITICAL **: 15:47:32.755: g_base64_encode_step: assertion 'in != NULL' failed

(Eclipse:23858): GLib-CRITICAL **: 15:47:32.755: g_base64_encode_step: assertion 'in != NULL' failed

(Eclipse:23858): GLib-CRITICAL **: 15:47:32.777: g_base64_encode_step: assertion 'in != NULL' failed

(Eclipse:23858): GLib-CRITICAL **: 15:47:32.777: g_base64_encode_step: assertion 'in != NULL' failed

(Eclipse:23858): GLib-CRITICAL **: 15:47:32.799: g_base64_encode_step: assertion 'in != NULL' failed

(Eclipse:23858): GLib-CRITICAL **: 15:47:32.799: g_base64_encode_step: assertion 'in != NULL' failed
Comment 1 Eric Williams CLA 2019-06-20 16:21:55 EDT 
This is actually a bug in Ubuntu's theme -- SWT doesn't call this function directly. Please file a bug downstream with the Ubuntu desktop maintainers.

*** This bug has been marked as a duplicate of bug 530781 ***