Ubuntu 22.04 LTS with Eagle 9.6.2 asking to wait or force quit

[mrsignal]

I have a clean install with all updates and I am trying to install eagle.  I got the normal error that the lib was not there so I read the README file and tried:

export LIBGL_ALWAYS_SOFTWARE=1
./eagle

Eagle starts, I was able to log on and every few seconds the Eagle is not responding pops up.  Two choices were to wait or force quit.  It only affects Eagle and not my OS.  It seems to pop up whenever I am trying to do something like creating a new project, etc.. If I wait and do not click anything it goes away in 5-10 secs.

On the CMD Line I get a inotify_add_watch message that  3d-models-jobs-7K76PZ9SDLGA.json is missing from .local/share/Eagle/cloud-processing/.   failed: "No such file or directory"

The directory exists but it is empty.

I do not know if that is the issue but it does show up.

Any ideas?

[rinaldimj]

I have exactly the same issue, running also Ubuntu 22.04 LTS

[daniel.belles]

Also the same for me (fresh installation of ubuntu 22.04 LTS and EAGLE 9.6.2)

[one-of-the-robs]

I suspect this is Ubuntu trying to be Windows and being overly aggressive about it. There may be a setting you can tweak to increase the allowed response time.

[daniel.belles]

I already tried this and set the timeout to a much larger value:

gsettings set org.gnome.mutter check-alive-timeout 60000

I followed the instructions suggested here: https://askubuntu.com/questions/1068921/how-to-disable-the-window-not-responding-dialog by Vaelus

After that there was no "Force to quit or wait" dialog anymore but now I saw that eagle was totally unresponsive and after the newly configured timeout the popup still appeared.

I think it's an issue regarding the window manager or some graphics related (does it relate to the startup error?)

./eagle: symbol lookup error: /lib/x86_64-linux-gnu/libGLX_mesa.so.0: undefined symbol: xcb_dri3_get_supported_modifiers

In the end I purged my Ubuntu 22.04 installation and reverted to Ubuntu 20.04.7 and everything works fine here.

BR Daniel

[yun.romadho]

Hi, I have same problem too. i use ubuntu 22.04 LTS.

try this one may be it could solve your problem too

https://forums.autodesk.com/t5/eagle-forum/running-eagle-on-fedora-33-dialogs-fail-display-properly-... 

[oe1gca]

Hi!

Is there a working solution for the problem with Ubuntu 22.04.1 LTS?

Regards, Gerhard

[guilherme5CXHP]

hi, exactly same issue here. anyone found a solution?

I see several logs in prompt always pointing to URL *.digicert.com

[77186:77203:1110/213554.279722:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[77186:77203:1110/213554.279757:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[77186:77203:1110/213554.279781:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com
[77186:77203:1110/213554.281167:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[77186:77203:1110/213554.281304:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: ocsp.digicert.com
[77186:77203:1110/213554.281378:ERROR:nss_ocsp.cc(591)] No URLRequestContext for NSS HTTP handler. host: crl4.digicert.com

[halhollis]

I believe I've found a workaround if not a solution. I stumbled upon this when I installed Ubuntu 22.04 on my 2012 vintage Shuttle PC. Essentially, in order to use xrandr to set the 1440p mode for my 2k monitor, I had to select "Ubuntu on Xorg" on the login screen (the default is Wayland). Then, when I installed Eagle 9.6.2 and started it (with the usual LiBGL_ALWAYS_SOFTWARE=1 setting), I immediately noticed that 'wait or force quit' problem was gone.

So, I just tried this on the 22.04 installation on my relatively new laptop (where I first noticed this problem), and I got the same result. I set "Ubuntu on Xorg" at the login screen, EAGLE runs without the annoyingly frequent 'wait or force quit' dialog boxes popping up. If I log out and then log in using Wayland, the problem returns.

If others get the same result (please let me know either way) then the problem appears to be Wayland related.

This link might be helpful:  https://fostips.com/switch-back-xorg-ubuntu-21-04/

[one-of-the-robs]

I can't say I'm in the slightest bit surprised that Wayland breaks things. It's really not production ready yet.

[guilherme5CXHP]

it worked for me, just tried and had not that annoying message. still need to use for some time, but seams workaround fixed it.

thanks for sharing

[rinaldimj]

---

@one-of-the-robswrote:

I can't say I'm in the slightest bit surprised that Wayland breaks things. It's really not production ready yet.

---

Sorry but this statement is not fair. Wayland is not "breaking things", the real issue here is that EAGLE still does not support Wayland natively, and it's running using the XWayland wrapper. It's being YEARS since the development of X is almost stalled.

[one-of-the-robs]

---

@rinaldimj wrote:
It's being YEARS since the development of X is almost stalled.

---

Well if you accuse my statement of being "unfair" then you really need to retract that one! Being in a constant state of flux is NOT a mark of software quality or maturity; needing very few changes generally is.

Besides, your comment about Eagle clearly shows you have no idea how things are put together. Eagle DOES NOT USE X "natively" either. It uses Qt.

[rinaldimj]

---

@one-of-the-robs wrote:

Besides, your comment about Eagle clearly shows you have no idea how things are put together. Eagle DOES NOT USE X "natively" either. It uses Qt.

---

Why do you feel offended by my comment? It doesn't matter if EAGLE uses Qt, it still runs using Xwayland, and that's a current decision of the developers.

[one-of-the-robs]

---

@rinaldimj wrote:

---

@one-of-the-robs wrote:

Besides, your comment about Eagle clearly shows you have no idea how things are put together. Eagle DOES NOT USE X "natively" either. It uses Qt.

---

Why do you feel offended by my comment? It doesn't matter if EAGLE uses Qt, it still runs using Xwayland, and that's a current decision of the developers.

---

Why do you think I'm "offended"? And why are you so "offended" by my comment? You are choosing to blame the developers of a piece of fairly old software for the fact that some other group of maintainers decided to pull the rug from under THE WHOLE WORLD (not just Eagle) by breaking the underlying OS.

You are clearly a fan of Wayland. I am not. It's unnecessary and underdeveloped and causes nothing but grief for most people. This is what happens when you tear up the fundamentals that people rely on and don't provide a properly working transitional layer. If Xwayland doesn't work properly then THIS IS NOT EAGLE's FAULT. It's Wayland that's at fault here, because they're the ones that broke things for everyone else and didn't provide a properly working compatibility layer.

Eagle works perfectly well on Gentoo, where you are given the choice to remain with a platform that works and you are expected to understand that trying out bleeding edge experimental replacements will cause you problems.

[rinaldimj]

---

@one-of-the-robs wrote:

---

---

Why do you think I'm "offended"? And why are you so "offended" by my comment? You are choosing to blame the developers of a piece of fairly old software for the fact that some other group of maintainers decided to pull the rug from under THE WHOLE WORLD (not just Eagle) by breaking the underlying OS.

You are clearly a fan of Wayland. I am not. It's unnecessary and underdeveloped and causes nothing but grief for most people. This is what happens when you tear up the fundamentals that people rely on and don't provide a properly working transitional layer. If Xwayland doesn't work properly then THIS IS NOT EAGLE's FAULT. It's Wayland that's at fault here, because they're the ones that broke things for everyone else and didn't provide a properly working compatibility layer.

Eagle works perfectly well on Gentoo, where you are given the choice to remain with a platform that works and you are expected to understand that trying out bleeding edge experimental replacements will cause you problems.

---

I simply do not agree. Keeping the software up-to-date and running is the job of the software developers. If they find a bug they should report it, but I really do not think is the case here: it's really hard to believe there isn't a "properly working compatibility layer" when other monstrous applications like Google Chrome runs without any issue on XWayland.
I perfectly remember the days when it was still "underdeveloped" as you say, when I needed to logout several times a day to change back to X if a specific app didn't work, but that was too long ago (maybe 2017, using Fedora 25, 5 years ago!).
One last thing that particularly caught my attention is when you say "they're the ones that broke things...". Who do you think "they" are? Do you know that most of the Wayland developers are former X developers? I really recommend you to read this next article, written by Eric Griffith and Daniel Stone (and just in case you don't know this last "guy", he's a former reference X11 developer)

https://www.phoronix.com/review/x_wayland_situation 

PD: I've never felt offended by your posts (glad to hear you neither), I've just thought that it's not fair to blame Wayland on this issue.