Lazarus
Programming => Operating Systems => Linux => Topic started by: dbannon on February 26, 2020, 01:36:01 am
-
There are now available early releases of the forthcoming Ubuntu 20.04 and given the problms we found in https://forum.lazarus.freepascal.org/index.php/topic,47240.0.html I thought I'd have a play. No point in complaining to Cannonical after release -
Its a 2.6G download, I tested only the 64bit system in a VM and found -
1. No sign of the long delays and (sometimes) crashes we saw in U19.10 !
2. Out of the box, U20.04 seems to have almost all the GTK2 stuff we need. Unlike U19.10 that required a dependencies download of some 200meg.
3. It does not use Wayland by default !
4. I installed FPC320 and used it to build Lazarus Fixes without problems.
For such an early release, seemed stable and functional !
I did notice that some TLables in my app had the text's decenders clipped. So a 'y' looked like a 'v' that might require a further look at.
But overall, good news IMHO.
Davo
-
1. No sign of the long delays and (sometimes) crashes we saw in U19.10 !
2. Out of the box, U20.04 seems to have almost all the GTK2 stuff we need. Unlike U19.10 that required a dependencies download of some 200meg.
I'm using Xubuntu 19.10 for a month and I didn't see any crash or the extra 200Meg you're talking about.
Unless you're talking about Lazarus running in 19.10. Then I have only one issue (https://forum.lazarus.freepascal.org/index.php/topic,47269.msg350743.html#msg350743) with it (still not crashing though).
-
I'm using Xubuntu 19.10 for a month and I didn't see any crash or the extra 200Meg you're talking about.
No, you would not have, This problem applied to the default, Gnome based Ubuntu
Unless you're talking about Lazarus running in 19.10. Then I have only one issue (https://forum.lazarus.freepascal.org/index.php/topic,47269.msg350743.html#msg350743) with it (still not crashing though).
Yeah, I saw that post. I was not sure what you meant by the "configuration dialog via menu", is that the dialog that pops up the first time you run a new install ? I guess you installed from a deb, did you use the startlazarus command ?
Davo
-
That is good news, indeed.
After Canonical borked U19.10, i switched to Debian 10/Gnome, but there i have the problem with "outdated" versions.
Since i have Manjaro/Gnome on my second Laptop, and there everything is running like mad, i was considering to switch to Manjaro completely.
The only thing stopping me doing it on my main Laptop, is that i actually really like Ubuntu, and the fact, that i would need to install a lot from AUR on Manjaro.
-
Just for fun in a x64 vm i have updated Kubuntu 19.10 to 20.04 and everything works. Lazarus and all my compiled applications. ;)
-
Unless you're talking about Lazarus running in 19.10. Then I have only one issue (https://forum.lazarus.freepascal.org/index.php/topic,47269.msg350743.html#msg350743) with it (still not crashing though).
Yeah, I saw that post. I was not sure what you meant by the "configuration dialog via menu", is that the dialog that pops up the first time you run a new install ? I guess you installed from a deb, did you use the startlazarus command ?
No, I don't mean that. I mean using menu "Tools>Options..." it raises the exception, but I can right-click in some parts (for example the source code editor) to access to part of the configuration.
I've answered in the original thread (https://forum.lazarus.freepascal.org/index.php/topic,47269.msg351097.html#msg351097) too.
-
OK, following on with this thread.
I am now testing with a month later beta of Ubuntu 20.04, about three weeks out from its release date.
Firstly, what I report here is independent of Lazarus 2.0.6 through to Trunk, independent of FPC 3.0.4 or FPC 3.2.0RC1
On Ubuntu 20.04 beta, and we have to assume the release version, we do have problems similar to what we had with U19.10. My test rig is a VM, built specially for this purpose. In all cases I install libgtk2.0-dev and libx11-dev then build a GTK Lazarus from source.
- As Lazarus starts up, there is a 25 second delay. You see an empty white box being the one that initially checks compiler, libraries, etc. This is very similar to https://forum.lazarus.freepascal.org/index.php/topic,47240.0.html except that installing aptmenu-gtk2-module does not fix it and it does not seem associated with occasional crashes.
- A new Lazarus now shows us a blank form, compile it, it runs immediately but crashes when exits. But, apparently not as often when run standalone nor in the IDE but without the debugger. This is similar to what I saw with a month earlier beta of U20.04. By 'crash' in this case I mean, on exit, the app remains on screen for a few seconds then a dialog pops up saying the app is not responding.
Notes -
- Installing libcanberra-gtk-module and / or aptmenu-gtk2-module does seem to 'help'. It reduces the incidences of the delay and the crash. Maybe I just have not taken big enough samples, its very variable.
- This beta of U20.04, unlike a month ago, does not have the GTK2 libraries pre installed. Thats sad.
- Things seem to work without problems using Qt5 instead of GTK2.
Davo
-
I installed the daily of Ubuntu 20.04 about ten days ago, and simply running sudo apt-get install app menu-gtk2-module seemed to work nicely. I installed the Lazarus trunk, compiled with 3.0.4. I do not see issues with character descenders (e.g. 'y' looking like 'v'). Hope this is not a sign things have regressed over the last few days.
Do you have any thoughts on statically linking libqt5pas1 to Lazarus QT5 executables (perhaps not the IDE, but deployed applications)? The Lazarus QT5 widgets seems to be maturing nicely, but as you have noted before the real issue is ensuring the C-bindings are installed.
-
Interesting Chris. I just built a 20.04 Mate VM, it generates errors when I run my application (built with FPC304 and Lazarus Fixes), both the Qt5 and the GTK2 versions.
But, if I build my application on that same VM, using FPC320rc1 and Lazarus Trunk, its fine and the binaries made there work fine in the U20.04 Gnome VM.
Re your question about libqt5pas1, I believe that the only real issue there is on -
* U16.04 - nothing can be done
* U18.04 - better to replace the existing one with the one we make. I agree its messy and end users will push back ....
* Mageia - probably same as above. The same probably applies to a number of other distros.
What we need is a way to detect which platforms need at attention and which don't. But this is a discussion for another thread.
Davo
-
One more piece of the jigsaw -
The formal beta of U20.04 Gnome seems better than the three day previous development release !
Installing appmenu-gtk2.module does seem to fix it, but only if you logoff and back in again. That logoff and, more importantly, login must load appmenu-gtk2-module properly.
This test is using FPC320 and Lazarus trunk, in each test I started Lazarus and stopped it immediately ten times and then started lazarus and clicked 'run' to compile and run the empty form show by default, again, ten times. With U20.04 beta, aptmenu-gtk2-module and a restart, perfect score.
The April 1st release of U20.04 would have entered the 25 second delay at least five times and the empty form would have crashed on exit, 'most' times.
Thats pretty good news IMHO, in a world starved for good news.
Davo