Problem with Installer Build 1216 Version 1.39.0 - Can't see which native packages to install

[gungwald]

I have first considered asking a question.

There is no Show Log link in and no red banner that would allow me to copy the installation log file.

As you can see from the above, I cannot see which packages to install. All you had to do is make the window resizable. You should never provide a fixed-size window precisely because of this problem.

Nor can I copy the information out of the window so I can paste it somewhere where I can see it. Because you have imposed these limitations, you have made it impossible for me to get the information I need to make the software work.

[merks]

It sounds like you’re on Linux using Wayland. I don’t recognize this dialog. What steps lead to this dialog showing?

If you download a *.tar.gz from here, does that work?

https://www.eclipse.org/downloads/packages/

It really sounds like something is missing from your system..,

[merks]

I see that title defined in p2 being used to open a dialog also defined by p2:

The dialog is just a subclass of org.eclipse.jface.dialogs.MessageDialog so the problem with the sizing of the dialog seems like an SWT issue.

So I think it's correct that the dialog comes up but of course the sizing bad though I think it's normal/typically that a message dialog is not resizable.

I'm not sure I can do anything in Oomph about a dialog created by and opened by p2.... Maybe there is some property I should set in the installer's *.ini...

@HeikoKlare

Does this dialog sizes problem look familiar?

[gungwald]

It sounds like you’re on Linux using Wayland. I don’t recognize this dialog. What steps lead to this dialog showing?

Yes, Linux, Wayland, Fedora 43. I downloaded eclipse-inst-jre-linux64(1).tar.gz and chose a CPP install.

[gungwald]

It sounds like you’re on Linux using Wayland. I don’t recognize this dialog. What steps lead to this dialog showing?

It's an Oomph install. The dialog comes up after the install seems to be done.

If you download a *.tar.gz from here, does that work?

https://www.eclipse.org/downloads/packages/

Yes, those don't have installers, so they start right up.

It really sounds like something is missing from your system..,

Could be. I don't know what.

The solution I would suggest, is to create a subclass of the MessageDialogWithLink that can calculate its width so that it is wide enough to display the text it contains. And it is resizable, just in case. This functionality really should be in the base MessageDialog but I'm not sure how you'll get it in there. I'm just guessing here because I don't know how SWT works. Maybe it's supposed to do that already. But it isn't. In that case it's an SWT or GTK bug.

[gungwald]

I ran the install under X11, not Wayland, in a OpenCDE session which uses mwm and also in an i3 session which uses X11, not Wayland. The dialog shows all the text in both of those cases. I cannot run this under X11/Gnome anymore because Gnome only supports Wayland. Because they're stupid. There is an unsupported way to run X11/Gnome, but I'm not going to install that because it replaces a bunch of standard Gnome files. I'll see if I can run it in KDE/X11. But, it looks like a Wayland problem. Wayland "is the future" but it still can't even work as well as X11. It's not faster. It doesn't have any new features. It has no benefits over X11. But we still must use it and get rid of the thing that always works. Wayland is a regression defect.

[HeikoKlare]

Does this dialog sizes problem look familiar?

The problem does not look familiar to me. To my current understanding, those dialogs should be auto-layouted based on the contents. The screenshots loooks to me as if that dialog had some default size set by the OS. We have recently added a hook to better adapt on DPI/zoom event, but since I don't think any such events are involved here I cannot image that it is related to the reported issue.
One thing I could imagine is that something goes wrong when instantiating that dialog (i.e., an exception is thrown), such that layouting does not happen as expected, but that's just a wild guess. Since there are so many Dialog usages/specialization around and I have never seen something like this, I have only low hopes to reproduce the issue without a description from someone being able to do it reliably.