Hello,
For some reason that I can’t understand, when I click somewhere in the column filter node, the knime is immediately closed. System Ubuntu 22
There is no problem when I want to make the same adjustment in the same workflow. (Windows )
Why do you think there is such a problem? I have never had a problem in Ubuntu until now. Also, there is no problem with the other workflows working. As far as I can see, the moment you want to remove a column in the column filter, it is immediately closed.
Hi @umutcankurt,
Thank you for reporting this issue.
Can you reproduce the issue reliably again? And if yes, is it possible to share the steps to reproduce it? You have mentioned when you click “somewhere” in the Column Filter node. Would you provide a bit more details what settings you were trying to modify?
And if possible, please share the “knime.log” file with us. Thank you!
Hello Armin,
I’m not exactly sure what the problem is stemming from, but I’ve tried three times and each time, the node closed as soon as I clicked on it. Specifically, when selecting a column to remove in the column filtering node, it also closed. On the Windows side, I didn’t encounter any issues with the same workflow. On Ubuntu, the workflows, including Selenium, are running fine without any problems. However, I don’t know why it closes when clicking within the column filter. I’m not sure if there’s a different issue at play right now. I’ve also performed updates and tried again, but the issue persisted. Eventually, I transferred the workflow to Windows, made the necessary adjustments, and it ran smoothly without any problems on Ubuntu. Unfortunately, I couldn’t make edits directly on Ubuntu.
Thanks for sharing. This is not expected (obviously). We had people try internally on Ubuntu 22.04 but it’s working as expected.
Do you also experience similar behavior with other nodes using a “modern dialog”, e.g. if you use the “Row Aggregator” node or “Number Rounder”?
The difference between plain execution and configuration is the UI element that opens (the configuration dialog uses a new browser windows and maybe there is something wrong there).
Can you confirm:
hs_err_pid*.log file anywhere in your home folder or the workspace folder (log files created during a crash)Sorry for not being more concrete/helpful right now.
– Bernd
Hello,
I’m not entirely sure right now, but it just closed again recently. Since I was on the phone, I didn’t notice exactly where I clicked when it closed, but I suspect there might be an issue with the updated nodes (this is my assumption). I will check if updating the interface or reverting to an older version might cause the problem, and I’ll share my findings. Due to ongoing workflows, I can’t risk testing it for potential shutdowns at the moment, but I will try at the earliest opportunity.
Upon initial observation, when you click on the column filtering node and try to select a column in the newly opened interface, it shuts down.
maybe these could be useful
hs_err_pid881532.log (860.8 KB)
hs_err_pid1044327.log (542.7 KB)
hs_err_pid1073677.log (714.0 KB)
hs_err_pid1600310.log (310.6 KB)
Thank you. The logs are already helpful to further isolate the issue. I would still like (you) to continue researching and confirming if the errors show up in the different scenarios I outlined above.
Since I was on the phone, I didn’t notice exactly where I clicked when it closed
What type of phone is that? The logs claim a powerful 24 cores, 125G machine. Are you using some sort of remote desktop?
Thanks!
I was actually on a phone call at that moment. Yes, I am using the server via remote desktop and the technical details are correct. So, I am not connecting via phone.
Hello, as far as I understand, I think knime is closed when clicked on all nodes with interface updates. Of course, this poses a big problem for me because the server uses Ubuntu. I hope this problem will be resolved with an update as soon as possible.
Is there any correction being made or have you identified the exact problem?
Hi, thanks for the confirmation. We passed it on to the maintainers of the respective library (it’s a browser based on Chromium).
It might also be related to the remote desktop product that you are using. Would it also be possible for you to (a) log-in with a different user and/or (b) log-in directly (not via remote desktop / remote X)?
Thanks,
– Bernd
Unfortunately, I have no solution other than remote access. There is no problem with it working, I just can’t edit it. When I want to edit, I upload the file to my computer with filezilla, edit it in Windows, transfer it back to the server and run it. In this case, it is an unnecessary waste of time. I must proceed like this until there is a clear solution.
Thanks for your help and concern.
We checked back with the provider of the library that is causing the problem (the browser instance that opens when you configure a node with a “modern dialog”). They confirm there is a race condition in place that can cause the observed behavior. The race condition is much more likely to occur when a remote display connection is used, such as in your case.
It seems there currently is no workaround but they have prioritized a fix, which we will deliver as soon as it’s available. For internal tracking purposes these are the tickets: UIEXT-2075 and NXT-2824.
Apologies, no better news for now. Either you have to do what you currently do (edit workflows locally then share - hub makes that very easy) or use the machine directly.
Thank you for your help and support.
@wiswedel I have a question, will I have problems with remote connection in Windows operating system? Is there a possibility of similar or same problem?
Not sure. I don’t think so given that Windows is so prominent and we haven’t heard of any problems (and these new dialogs have been out there for quite a bit).
According to what we were told by the Equo Chromium maintainers the problem is a race condition, so it’s not deterministic. They also say it’s more likely to happen on ARM systems (which KNIME doesn’t offer for Windows and Linux).
Internal ticket ID: UIEXT-2075
Fix version(s): 5.3.2, 5.4.0
Other related topic(s): -