OM crashes systematically on Ubuntu 21.10

amichaibenshalev · March 7, 2022, 9:48pm

Hello Karim,
Just to update you: I tried running OM on Elementary OS (OS from USB) and it worked fine, no problems, I then tried with Pop OS (based on the Ubuntu 21.10) and I had the same problem. So now I have a dual boot with Elementary and I can work fine. I suspect it’s something with Ubuntu 21.10 (maybe on my computer…or in general), in April the new LTS is coming out and maybe it’ll be solved. Elementary is based on ubuntu LTS not the latest…

Best and thanks again for all the help trying to solve this,
Amichai

haddad · March 8, 2022, 4:47pm

Dear Amichai,

Thanks for reporting. I use personally Debian (i am on a stable distribution). And everything’s working. What is strange, is that Ubuntu is a Debian based distrib. So I don’t know. Maybe if you change your window manager from Gnome to something else (more light ) such as Xfce, maybe things will run more smoothly. It is just a guess.

Best
K

priosfilho · October 19, 2022, 2:50am

Hi there

I would like to register that I was facing the same issue Amichai related on this post, with persistent crashes on either OM 6.20 or OM 7.1, with no apparent action within patches-related cause, using Ubuntu 22.04 LTS. It was very frustrating, especially considering that it was running just fine on Ubuntu 20.04 LTS and the problem only appeared after upgrading the OS.

After following Karim’s indications to untick Tooltips option and OMTristan autoload it seems to be working with no random crashes so far. More than 30 minutes of continued use of OM 6.20 on Ubuntu 22.04, and no crashes until now - previously it was lasting no more than 10 minutes before a new crash.

Hope this can help someone facing the same problems in the future…

Will test with OM 7.1 later.

Thanks!

haddad · October 19, 2022, 11:54am

Hi priosfilho,

Thank you for reporting this. I suspect that this is related to some window decorations in Ubuntu that have changed as default. Will try it on the latest release of Ubuntu.
Please keep us informed.

best
K

priosfilho · October 21, 2022, 8:43pm

Hi Karim

Unfortunately, the random crashes continue happening either in OM 6.2 or OM 7.1. Sometimes just after a few minutes of plain use… It seems to be independent of a specific type of action but I think I can affirm that it happens in reaction to (random and diverse) actions within OM. (I can report at least some instances: duplicating objects, pasting objects, inserting comments, opening score objects) When I reopen OM I try to replicate the problem by redoing exactly what I did when the last crash happened, but it doesn’t crash until it (apparently) randomly decides to do so, this time after a new action.

I’m on a HP 15-bs0xx Notebook
16GB RAM
Intel® Core™ i5-7200U CPU @ 2.50GHz × 4
Mesa Intel® HD Graphics 620 (KBL GT2)
Ubuntu 22.04.1 LTS
GNOME 42.4
Wayland Windowing System

I’ve used OM 6.2 without this problem for a long time on this same machine but on Ubuntu 20.04 LTS. This only has begun after upgrading to 22.04 LTS.

OM log is bellow - but I don’t know if it registered the last fails (the date of the log file is Oct. 18th…)

openmusic-log (105.6 KB)

I may add that OM 7.1 is showing up a message just after initialization (OM 6.2 was not, by the way):

I hope you can figure out what is going on! Thanks for your attention!
Paulo

haddad · October 21, 2022, 10:33pm

Dear Paulo,

reading your log, it seems that you are running LispWorks 7.1.2 which is really strange and i doubt that this is happening!

I suggest to clean up your install first, ie remove ALL OpenMusic installations on your machine, and install the latest version. It appears that you have conflicting OM’s runing.
All prior to version 7.0 are based on LW 7.x
Starting from OM version 7.x, OpenMusic uses LispWorks 8.x
It could be probably this mix up that is resulting all these crashes.

Please keep me informed.

Best
K

priosfilho · October 22, 2022, 2:50am

Dear Karim

Many thanks for the fast reply. I will try a complete removal and reinstalling OM 7.1 aftwards to see what happens. I suppose then that 7.1 installation will get correct version of LispWorks, right?

In the meantime, I would like to send some more information, just in case…

I tried to run OM 7.1 from the terminal, so I could better monitor what was happening (not that I would be able to understand it, but…)

Firts of all, even before crashing again, I noticed the following messages on terminal:

Warning: (defun g304592) being redefined in listener (previously in /media/priosfilho/dados/tudo/composicao/bujokas-russia-2022/trio-russia/elements/008f-polyphonic-pitch-rules.omp).
Warning: G-domain : nil, level 16: invalid source position for vertical gradient
Warning: G-domain : nil, level 16: invalid source position for vertical gradient
Warning: G-domain : nil, level 16: invalid source position for vertical gradient
Warning: G-domain : nil, level 16: invalid source position for vertical gradientGtk-Message: 23:07:38.428: Failed to load module "canberra-gtk-module"
Gtk-Message: 23:07:38.430: Failed to load module "canberra-gtk-module"
Gtk-Message: 23:08:44.110: Failed to load module "canberra-gtk-module"
Gtk-Message: 23:08:44.112: Failed to load module "canberra-gtk-module"

Warning: G-domain : nil, level 16: invalid source position for vertical gradientGtk-Message: 23:11:14.569: Failed to load module "canberra-gtk-module"

Nonetheless, this session didn’t crash - I quit to search about this canberra-thing, instead.

So when I re-launched OM 7.1 from Terminal, a new session soon led to a crash and that were the messages on terminal:

Gtk-Message: 23:25:10.114: Failed to load module "canberra-gtk-module"
Gtk-Message: 23:25:10.116: Failed to load module "canberra-gtk-module"
Warning: (defun g304600) being redefined in listener (previously in /media/priosfilho/dados/tudo/composicao/bujokas-russia-2022/trio-russia/elements/008f-polyphonic-pitch-rules.omp).
Warning: (defun g304592) being redefined in listener (previously in /media/priosfilho/dados/tudo/composicao/bujokas-russia-2022/trio-russia/elements/008f-polyphonic-pitch-rules.omp).X-IO-ERROR on ":0 {Lispworks}" : Fatal IO error 11 ("Resource temporarily unavailable") Xlib: request 10 length 24 would exceed buffer size.
Xlib: request 40 length 16 would exceed buffer size.


!!!!!Wrote error log to /home/priosfilho/logs/LispWorks/openmusic-log at 2022/10/21 23:35:13
Xlib: request 14 length 8 would exceed buffer size.
Xlib: request 40 length 16 would exceed buffer size.

Error: Segmentation violation(11) [code 0] at 7F5FDD8F86A1
        Foreign code offset #x71 from symbol "XTranslateCoordinates"
        module "/lib/x86_64-linux-gnu/libX11.so.6" [ #x7F5FDD8B2000 ]
rax            0 ; rbx            0 ; rcx 7F5FDF2FFA6F ; rdx            0
rsp 7F5FD628DE50 ; rbp            0 ; rdi 7F5FD00476F0 ; rsi 7F5FD628DE60
r8            35 ; r9  7F5FD628BBA6 ; r10            0 ; r11          293
r12          824 ; r13      2C02076 ; r14 7F5FD00476F0 ; r15 7F5FD628DEF0
  1 (continue) Remove display-callback from #<patchpanel  426026CD63>
  2 (abort) Return to event loop.
  3 Destroy interface "^008f-polyphonic-pitch-rules" (of type editorwindow)

Type :b for backtrace or :c <option number> to proceed.
Type :bug-form "<subject>" for a bug report template or :? for other options.

Maybe it’s relevant to note that this new session’s caberra-module message came a considerable time before the crash…

I hope this information help figure out the problem! Anyway, I will try the complete removal and reinstall tomorrow and let you know!

Thanks again,
Paulo

haddad · October 22, 2022, 6:38am

Ok thanks for reporting.
Now it appears clearly that it is a gtk2 problem.
LW8 depends on gtk2 and wants to use libcanberra-gtk-module which appears either not installed on your Ubuntu by default or “wrongly” installed.
However, i will try today to install your version of Ubuntu so i can see better. on the 21.20 it’s working OK without crashes. With all dependencies installed.

Best
K

haddad · October 22, 2022, 10:00am

Dear Paulo,

Ok I’ve just tested OM 7.1 on a freshly installed Ubuntu 22.04 LTS on my VM. No problem using it. No crashes.

As stated above, it might be that your libcanberra-gtk-module is not installed correctly.
Since from all OM’s dependencies you have just to install (always on a freshly installed Ubuntu 22.04) libportmidi0 and libcanberra-gtk-module. So i suggest you re-install libcanberra-gtk-module.

For info, on a Debian based install, dependencies are:
libsndfile1, libportmidi0, libsamplerate0, libgtk2.0-0, gtk2-engines-murrine, libcanberra-gtk-module, fontconfig, mime-support, desktop-file-utils, libcurl4

Please keep me notified.

Best
K

priosfilho · October 23, 2022, 3:19am

Dear Karim

Thanks again for all the help.

I followed some of your instructions:

Reinstalled libcanberra-gtk-module
Uninstalled and cleaned traces from OM 6.2 and 7.1 from my machine
Installed OM 7.1 again

I can say that the canberra-module message is no more showing on terminal up while using OM.

And I experienced for the first time a long period of use without crashes.

But then they have just begun to happen again, and I was able to replicate the crashes by clicking on the inlets to edit its values on a cluster-engine object in the patch attached.

The message that showed up at the right moment of the last of these repeated crashes is:

Warning: G-domain : nil, level 16: invalid source position for vertical gradientX-IO-ERROR on ":0 {Lispworks}" : Fatal IO error 11 ("Resource temporarily unavailable") Xlib: request 10 length 24 would exceed buffer size.


!!!!!Wrote error log to /home/priosfilho/logs/LispWorks/openmusic-log at 2022/10/23 00:09:09
Xlib: request 40 length 16 would exceed buffer size.

Error: Segmentation violation(11) [code 0] at 7F7712F106A1
        Foreign code offset #x71 from symbol "XTranslateCoordinates"
        module "/lib/x86_64-linux-gnu/libX11.so.6" [ #x7F7712ECA000 ]
rax            0 ; rbx            0 ; rcx 7F7718924A6F ; rdx            0
rsp 7F7702FF8910 ; rbp            0 ; rdi 7F770C0476F0 ; rsi 7F7702FF8920
r8            35 ; r9  7F7702FF6666 ; r10            0 ; r11          293
r12          824 ; r13      3001727 ; r14 7F770C0476F0 ; r15 7F7702FF89B0
  1 (continue) Remove display-callback from #<patchpanel  41B018725B>
  2 (abort) Return to event loop.

Type :b for backtrace or :c <option number> to proceed.
Type :bug-form "<subject>" for a bug report template or :? for other options.

OpenMusic 1 : 1 > Killed

Patch that was in use during last crashes:
008e-polyphonic-pitch-rules 2.omp (386.2 KB)

Log file:
openmusic-log (272.4 KB)

Hope this helps! Thanks again.

haddad · October 23, 2022, 12:07pm

Dear Paulo,

Are tooltips option checked in your OM preferences? If yes, please uncheck, save workspace and relaunch.

priosfilho · October 23, 2022, 1:47pm

Hi Karim,

It was already unchecked.

haddad · October 23, 2022, 1:58pm

Can you try with the first two options checked (Handle error messages and enable evaluation Process).

Then can you send me your workspace in order to see what’s wrong. It might be ok and it can be a customized feature you had on your OS, i don’t really get it. I tested your patch and it is still ok on the Ubuntu 22

Best
K

priosfilho · October 23, 2022, 2:15pm

Will try with that two options checked, then.

I don’t think that the problem is workspace related because I have tested with different ones and the crashes were persistent across them.

But I send attached the one I’m working on currently.
trio-russia-zip.zip (1.0 MB)

I have been using Ubuntu 20.04 until last week when I did a fresh install of Ubuntu 22.04. Just after upgrading, I installed OM and the problem begun to show up. I don’t think I customized anything in Ubuntu since then… The only thing I did was to change from Wayland to Xorg windowing system from the login screen’s cog, but when I did that I had already experienced the crashes.

Thank you, Karim!

priosfilho · October 23, 2022, 3:02pm

Just to add that the crashes keep happening after checking Handle Error and Enable Evaluation only on General Preferences.

priosfilho · October 23, 2022, 7:06pm

Sorry for the overposting, but I just want to add also that the popup with an error message continues to show up on the initialization of OM 7.1. The message is: “ERROR: In 1- of (nil) arguments should be of type number.” I can just close the popup and continue using OM normally, yet maybe it refers somehow to the crashes, I don’t know…

haddad · October 23, 2022, 7:07pm

Ok Paulo,

Thanks for reporting back. I will try to see what’s wrong here. It could be the new veraion of gnome and its lib. I will send your crash report to LW team. It could be LW related.

Best
K

priosfilho · October 24, 2022, 1:34am

Thank you, Karim. Please let me know if you find something… In the meantime, I’m trying to work piece-by-piece between crashes. Will also consider installing another distro, perhaps Ubuntu is the problem.

By the way, always with hope that a new info can help clarify what the problem could be, I’ve noticed a new message on Terminal when the last crashes happened (OM 6.2, this time):

[xcb] Unknown request in queue while dequeuing
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
openmusic: ../../src/xcb_io.c:175: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed.

All best,
Paulo

anders · October 24, 2022, 6:24am

Hi Paulo.

Will also consider installing another distro, perhaps Ubuntu is the problem.

Perhaps i could suggest testing with Fedora? It could help narrowing in since I develop code on Fedora, and i beleive Karims main platform is Ubuntu. (No, Karim?)

haddad · October 24, 2022, 11:01am

@anders
No i use mainly Debian. (Ubuntu is a Debian based distro). But i am afraid it is not due to a distro, but maybe to GNome. However, teste it on fedora and it works also.
Did you have an issue on Fedora?

Best
K