Hi,
i updated with the latest version 5.5.0. However, the knime platform is not loading and displaying a blank page. Appreciate advice any idea why. Thank you.
1 Like
Hello @MAYYIANTAN and thank you for reporting this issue.
I moved your reply here as a new topic since we could reporoduce the issue and now have a ticket for it to fix as soon as possible.
The internal ticket ID is: NXT-3892
Thanks again for reporting the problem so quickly!
3 Likes
Hi @MAYYIANTAN and @armingrudd
I experienced the same. Uninstalling KNIME and installing it from scratch solved the issue. However this is a kind of workaround.
2 Likes
(Sorry for the hassle!)
Short update after talking to Armin and diagnosing further with the team: we are still uncertain why the problem occurs, but we now have a recipe to reproduce it – at least on Windows. Updating older KNIME installations is part of our testing protocol and did not fail in our release testing.
We haven’t been able to fully understand the issue, but we’re continuing to diagnose it. For now, if you encounter the problem, you can work around it by adding -clean to the knime.ini file above the -vmargs line. This line can be removed after KNIME has started. Alternatively, you can start KNIME from the command line with -clean as an argument.
We’ll keep this thread updated as we find out more details.
7 Likes
I have the same or related problem on Linux, Fedora 42 with Gnome/Wayland.
-clean did not help, neither in the ini file nor on the command line. Likewise, reinstallation and using a new workspace did not work.
This is what I get on the command line.
./knime
(java:214292): GdkPixbuf-CRITICAL **: 12:06:33.311: gdk_pixbuf_get_width: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed
(java:214292): GdkPixbuf-CRITICAL **: 12:06:33.311: gdk_pixbuf_get_height: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed
(java:214292): GdkPixbuf-CRITICAL **: 12:06:33.311: gdk_pixbuf_get_height: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed
(java:214292): GdkPixbuf-CRITICAL **: 12:06:33.311: gdk_pixbuf_get_width: assertion ‘GDK_IS_PIXBUF (pixbuf)’ failed
(java:214292): Gtk-CRITICAL **: 12:06:33.311: gtk_window_resize: assertion ‘width > 0’ failed
[0703/120639.108937:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0703/120639.111260:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0703/120639.111336:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0703/120639.112566:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0703/120639.112598:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0703/120639.112653:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0703/120639.112758:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0703/120639.112791:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0703/120639.113085:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0703/120639.113111:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0703/120639.113142:ERROR:elf_dynamic_array_reader.h(64)] tag not found
I actually get two windows, one big white one, and a tiny one with the interface.
yep, extremely messy on linux - double windows, some buttons not clickable
Regarding Linux/Wayland: I think this is independent. Please see the release notes (there is a workaround). Fix is on the way for a bug fix release.
3 Likes
Thanks, that fixed it for me.
1 Like
Thanks, that worked for me! (I’m on Windows 11). Oopsies on this issue, but I’m loving the UI changes I see in the update!
By the way, I notice my geospatial analytics extension didn’t update properly. I had to turn on the experimental community extensions URL again. I wonder if that may have contributed to the white screen opening?
2 Likes
Thanks for help. It helped me.
1 Like
This resolved it for me, thank you.
1 Like
Thank you. I managed to resolve it after re-installing the latest version. Appreciate it.
1 Like
Thank you very much. It worked for me! For the curious: What is the effect of this argument?
1 Like
Thank you for the advice.
The -clean flag is interpreted by the underlying Eclipse framework and cleans out cached files used in normal operation and updates. In this case it helps because in some strange cases one file containing old 5.4 code remains in some internal Eclipse cache and is then chosen over the new 5.5.0 replacement. This leads to the errors because new functionality is missing. After clearing the cache the correct code is being loaded.
4 Likes
What a day! We think we have finally fixed the root problem by slightly repackaging one of the plug-ins. The change is on the update site, and the issue should no longer occur (at least it doesn’t for us).
Apologies for the problems and frustration this caused. We do have automated and manual tests that verify the update of older KNIME installations. However, as far as we can tell, this problem has only surfaced (a) on Windows and (b) only when a certain set of extensions was previously installed in 5.4 or older.
– Bernd (+ team)
8 Likes