I'm not sure if the OS or the desktop environment. I'm running on a VM, at least all the desktop is not working and I must restart the VM to continue when executing LazPaint (but this happens sometimes, other times happens that I can kill the app).
Maybe that could be related to the window manager. On my distro, you can change it in Paramaters > Desktop Parameters. It shows a list of window managers.
Someone had commented about checking the "Ubuntu with Wayland" option, I did that, and in this mode the IDE works perfectly.
Someone had commented about checking the "Ubuntu with Wayland" option, I did that, and in this mode the IDE works perfectly.
How I can change that, when Installing ubuntu I checked automatic login, and now I don't see that gear to change the desktop mode...
I've just used fpcupdeluxe to install fpc fixes3.0 and Lazarus fixes2.0 (Qt5 interface) and it seems to work so far..
OK, I can confirm this freeze up happens on a VM running 19.10. But not every time I start Lazarus, sometimes it starts and continues to run normally. My rough guess is that it fails, for me, on a Virtual Box allocated 4G ram one in four times. Using Lazarus 2.0.6 debs from sourceforge.
I have seen four such freezups now, in each case an initial startup, have not seen it happen in a restart. I blow away the config files between tries to ensure an initial start.
(I have been running Fedora 30 in a VM for a week now without any sign of this issue, about the same level of gnome and release time, that may indicate the freeze up is a Ubuntu only thing ?)
Davo
EDIT: Just found something suggesting it's a swap-Problem.Yes, looks an interesting read, well spotted ! My test u1910 is a VirtualBox VM, fresh install, no extensions. I have given it 4G of ram and, at first though giving it an 8G instead eliminated the problem. But going back to 4G also seemed to 'fix' it :(
https://askubuntu.com/questions/1185491/ubuntu-19-10-freezes-and-lags-reguarly?noredirect=1&lq=1
The last 4 answers
Check your swappiness-valueEDIT: Just found something suggesting it's a swap-Problem.Yes, looks an interesting read, well spotted ! My test u1910 is a VirtualBox VM, fresh install, no extensions. I have given it 4G of ram and, at first though giving it an 8G instead eliminated the problem. But going back to 4G also seemed to 'fix' it :(
https://askubuntu.com/questions/1185491/ubuntu-19-10-freezes-and-lags-reguarly?noredirect=1&lq=1
The last 4 answers
Thats when I realised it was erratic, needed losts of tests to get some valid statistics.
So, swap could indeed do just that, my VM has only 800M swap, thats plainly not enough. Although I do feel with 4G ram it should not really poke much into swap anyway doing what we have been doing. But I will have a go at those suggestions tomorrow ....
Davo
(Recent advise does not seem to be the 1:1 swap ratio, Ubuntu talks about the sqr root of your ram (in Gigs) when more than 4 (?) is available. Clearly is all lazy swap these days ....Mark Russinovich has a series of excellent articles (as is most everything he does) about memory management and in one them, he addresses the advice given on pagefile size (among other things.)
Davo
PS 440bx, thanks for that link, I notice its a 2008 release, I will have a read but I do suspect the relative cheapness of ram these days and the follow on of people having so much more may date it a bit ? When I was running HPC systems, if we saw a user's job running into swap, we'd consider killing in, certainly suggest to them they need to have a little think ....You're welcome and your point that the article is "a bit old" is valid but, my own experience is that what he states about the page file remains and, has remained true throughout the years. Specifically, the more RAM we put in our machines the more programs we feel free to run simultaneously. For instance, most of the time, I'm running three (3) VMs, each consumes more memory than what my 2008 machine had in total. It seems that, no matter how much RAM we have, we'll always consume more than what's available, in part because the programs we use keep getting bigger and bigger, most development environments are good examples of that and, more and more "utility" type programs are needed/useful to get the job done, e.g, text editors, debuggers, hex editors, CLIs, file explorers, internet browsers (which consume ever more memory, mine is consuming 1.5GB as I type this!), etc, etc.
Davo
Well, those updates make no difference. I'd like to see some updates that mention DBUS....
I wonder if the problem relates to apps using GTK2, may explain why not all apps are a problem ? Just speculation I'm afraid.
Davo
I've just used fpcupdeluxe to install fpc fixes3.0 and Lazarus fixes2.0 (Qt5 interface) and it seems to work so far..
I wonder if it is version 2.0 that works better or Qt5.
I just rebuilt Lazarus using fpcupdeluxe for the Gtk widget set, and experienced the same semi-freeze experienced with the .deb packages. It must be a Gnome issue. I've also encountered long launch times for other applications, so I think there is something fundamentally borked in the Gnome / GTK environment.
I still think it relates to dbus (my app does not use dbus) but have just not had the time to try and isolate it down....
Davo, coud you take a look here?
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1834583
Not wanting to rain on your parade, my test rig is a U1910 VM, clean install, updated as recommended. Only one extension manually installed, Applications Menu, I have removed it, logged out, logged in same issues.QuoteDavo, coud you take a look here?
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1834583
No, I don't think so. Thats a problem that crops up as a window closes, we see the lockup before any windows are displayed. It was reported to have been fixed in mutter (3.32.2+git20190711-2ubuntu1) and U1910 uses 3.34...
I 'think' but am not sure that mutter is only used with Wayland, that means Gnome-shell only right now. I can demo this problem on (eg) Mate Desktop too.
Davo
7. make bigide LCL_PLATFORM=qt5 <enter>
Hi, experiencing the same freezes on my Ubuntu 19.10 vmdk.You might be confusing two approaches here TK, if you decide to use fpcupdeluxe you don't build the Qt5 version of Lazarus, however, I will be surprised (pleasantly so) if it avoids whatever this mystery problem in U1910. If you want to build a Qt5 version, and indications are that does avoid the problem, you should download the source (using svn), install the Qt5 libraries, and then build with that command. Refer to wiki.
How do I build Lazarus with Qt5 using fpcupdeluxe?
I installed fpc+laz using https://github.com/LongDirtyAnimAlf/fpcupdeluxe/releases/download/1.6.4d/fpcupdeluxe-x86_64-linux
The following does not work for me:7. make bigide LCL_PLATFORM=qt5 <enter>
Thanks
My FPC304/Laz206 is installed with fpcupdeluxe --> Standard-IDE gtk2 --> Freezes.Hi, experiencing the same freezes on my Ubuntu 19.10 vmdk.You might be confusing two approaches here TK, if you decide to use fpcupdeluxe you don't build the Qt5 version of Lazarus, however, I will be surprised (pleasantly so) if it avoids whatever this mystery problem in U1910. If you want to build a Qt5 version, and indications are that does avoid the problem, you should download the source (using svn), install the Qt5 libraries, and then build with that command. Refer to wiki.
How do I build Lazarus with Qt5 using fpcupdeluxe?
I installed fpc+laz using https://github.com/LongDirtyAnimAlf/fpcupdeluxe/releases/download/1.6.4d/fpcupdeluxe-x86_64-linux
The following does not work for me:7. make bigide LCL_PLATFORM=qt5 <enter>
Thanks
I guess it would be possible to build a Qt5 Lazarus from the source delivered by fpcupdeluxe but you would want to know what changes have been made ....
Davo
Hi, experiencing the same freezes on my Ubuntu 19.10 vmdk.
How do I build Lazarus with Qt5 using fpcupdeluxe?
Not wanting to rain on your parade, my test rig is a U1910 VM, clean install, updated as recommended. Only one extension manually installed, Applications Menu, I have removed it, logged out, logged in same issues.QuoteDavo, coud you take a look here?
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1834583
No, I don't think so. Thats a problem that crops up as a window closes, we see the lockup before any windows are displayed. It was reported to have been fixed in mutter (3.32.2+git20190711-2ubuntu1) and U1910 uses 3.34...
I 'think' but am not sure that mutter is only used with Wayland, that means Gnome-shell only right now. I can demo this problem on (eg) Mate Desktop too.
Davo
Has anyone solved it ?!Not as far as I know. Are you using Ubuntu 19.10 ? Thats where all reports focus ...
And it really is a big problem. But has anyone already communicated the problem to those who develop and maintain the ubuntu project?
I have updated the Mantis notes with solutions that worked for me. Maybe others can test and see if this solves their issues:
This page details solutions
https://askubuntu.com/questions/1184774/some-applications-on-ubuntu-19-10-very-slow-to-start
1.) launch program as super user ("sudo ./project1")
2.) launch application with launch "dbus-launch --exit-with-session ./project1"
3.) Run "sudo apt-get install appmenu-gtk2-module" and restart your computer - after this applications launch quickly, though they report
[DEBUG] Name com.canonical.AppMenu.Registrar does not exist on the session bus
Davo-OK, Chris, are you saying that just installing appmenu-gtk2-module makes the problem go away or are you then using it to put the dbus-launcher env var in front of your launch commands ?
I have two machines running 19.10. On one I installed appmenu-gtk2-module and GTK2 apps now load on that machine instantly.
Juha, I don't think this is a "no change required", instead the change is we need is to add appmenu-gtk2 to the Lazarus Deb's list of dependencies. Its quite small and will otherwise do no harm. It seems to already be on most older Ubuntus that were more GTK2 friendly.Ok. It means the Ubuntu maintainers should update their .deb package. Mattias should add the dependency for the .deb of next release.
I would also suggest we keep the bug open as the fix is not intuitive for users who experience the problem. There seem to be two possible long term solutions:A patch for Lazarus would be the ideal solution. How to make it? What pulls in the dependency? I don't even know what appmenu-gtk2 does.
1. Ubuntu gets updated to support all the GTK2 applications that are impacted
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1852016
2. We work out a patch for Lazarus that allows Lazarus and applications built by Lazarus to avoid these penalties.
A patch for Lazarus would be the ideal solution. How to make it? What pulls in the dependency? I don't even know what appmenu-gtk2 does.
Switched from U19.10/GDM/Gnome to Debian10/Lightdm/GnomeAh, but the issue is "do you have appmenu-gtk2 installed in your Debian install now" ?
No more issues anymore.
So, Canonical borked 19.10
(project1:32719): Gdk-WARNING **: 09:47:28.316: gdk_window_set_icon_list: icons too large
....
I only recently installed MX and am using the latest version 19.2.
So, that says its actually not the same issue as this thread started. It applied to the IDE as well and it was a quite repeatable 20 or so seconds and sometimes triggered a crash. Not very interesting (that its not the same issue) but its one fact we can keep.
* Windows within Lazarus are sometimes delayed in opening, but never the IDE itself.
* The problem disappears after a reboot, only to reappear later.Again, thats not typical of original problem. More like some resource being consumed. Hmm, and it says my tests are not useful then, I fired up the VM, ran the test. Is it enough to just have the OS just running, doing nothing or does it need to be actively used ? And what sort of time frame are we looking at ? Minutes, hours, days ?
and the LATEST LAZARUS COMPILER.Do you mean latest from Git branch 'main' or the last release?
I am having the SAME ISSUE with my latest Lazarus FreePascal Program I wrote.
Awesome, you problem appears important enough to warrant a new thread !