Community
Participate
Working Groups
When running the latest Neon M6 I get lots of such critical errors: (Eclipse:24146): GLib-CRITICAL **: g_base64_encode_step: assertion 'in != NULL' failed
This doesn't happen with SWT_GTK3=0
I have the same problem with the final released version
What OS and GTK versions does this occur with?
(In reply to Eric Williams from comment #3) > What OS and GTK versions does this occur with? I have installed the parallel developer edition of neon on a personal PC with opensuse 42.1 using Qt libs 5.7.0 and KDE Framework 5.24.0. libgtk-2_0-0 version is 2.24.30-8.3 libgtk-3-0 version is 3.16.7-5.1
(In reply to Marcin Mielniczuk from comment #1) > This doesn't happen with SWT_GTK3=0 Where did you make that change?
I can't reproduce this anymore on Arch Linux, Gtk 3.20. All I get is a couple of warnings: ** (eclipse:7148): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ** (java:7151): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized. org.eclipse.m2e.logback.configuration: Logback config file: /home/marcin/workspace/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.7.0.20160603-1933.xml When I set SWT_GTK3=0, I ran Eclipse as follows: env SWT_GTK3=0 eclipse Michel, can you try with Gtk 3.20?
(In reply to Marcin Mielniczuk from comment #6) > > When I set SWT_GTK3=0, I ran Eclipse as follows: env SWT_GTK3=0 eclipse Using that tip, I do not have the Glib-CRITICAL messages any more. Thanks! > > Michel, can you try with Gtk 3.20? I have a laptop with a dual boot with opensuse Tumblewwed which is the "rolling release" version of opensuse, hence with more recent versions of components. I shall try to see whether there is any difference.
(In reply to Michel DEVEL from comment #7) > > Michel, can you try with Gtk 3.20? > > I have a laptop with a dual boot with opensuse Tumblewwed which is the > "rolling release" version of opensuse, hence with more recent versions of > components. > I shall try to see whether there is any difference. The laptop has libgtk-3-0 3.20.6-1.2 It seems I do not have Glib-critical messages any more, but I have even more "Gtk-WARNING **: Theme parsing error: gtk.css ... " messages!...
Ran into the same problem with the following configuration: - SWT 4.6.1 - JDK 8 (8u131-b11-0ubuntu1.17.04.1) - Eclipse Neon.3 Release (4.6.3) - Ubuntu Linux 4.10.0-22-generic #24-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux - KDE Plasma 5.9.4 Qt 5.7.1 Error output: (SWT:7578): GLib-CRITICAL **: g_base64_encode_step: assertion 'in != NULL' failed
Ran into the same problem with the following configuration: - openSUSE Leap 42.2 - Linux kernel 4.4.73-18.17-default - KDE Plasma Version: 5.8.6 - KDE Frameworks Version: 5.26.0 - QT Version 5.6.1 - OS type: 64-bit Eclipse: - Eclipse IDE for Java Developers - Version: Oxygen Release (4.7.0) - Build id: 20170620-1800 ------------ Errors: multiple at startup (Eclipse:2963): GLib-CRITICAL **: g_base64_encode_step: assertion 'in != NULL' failed
I see a bunch of these when we run SWT's jUnit tests. This could be used to investigate.
Also occurs with Oxygen Release (4.7.0) on Ubuntu 17.04 with the xfce4 desktop: (Eclipse:14327): GLib-CRITICAL **: g_base64_encode_step: assertion 'in != NULL' failed ... (Eclipse:14327): Gtk-WARNING **: Allocating size to GtkBox 0x7f513532a160 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (Eclipse:14327): Gtk-WARNING **: Negative content width -6 (allocation 1, extents 4x3) while allocating gadget (node toolbar, owner GtkToolbar) ...
(In reply to Juergen Baier from comment #12) > Also occurs with Oxygen Release (4.7.0) on Ubuntu 17.04 with the xfce4 > desktop: > > > (Eclipse:14327): GLib-CRITICAL **: g_base64_encode_step: assertion 'in != > NULL' failed These are the GLib warnings for this bug. > ... > (Eclipse:14327): Gtk-WARNING **: Allocating size to GtkBox 0x7f513532a160 > without calling gtk_widget_get_preferred_width/height(). How does the code > know the size to allocate? > > (Eclipse:14327): Gtk-WARNING **: Negative content width -6 (allocation 1, > extents 4x3) while allocating gadget (node toolbar, owner GtkToolbar) > ... These types of warnings are sizing warnings and are being tracked by bug 486068.
These errors are related to themes, and thus a ticket should be filed upstream with your theme maintainer -- this is known issue with some Ubuntu themes and it seems KDE is affected too. For sizing errors, please see bug 486068.
