Hello Nils and Bill,
Pamac manager lists Agordejo 0.3.0-1 as the latest release. It also has no entries for agordejo-git in the AUR. Both of which are not true and peculiar, maybe an issue with my mirrorlist. I tried refreshing and ranking for speed and sync. I suspect this is the root of the problem, and I'm still investigating. In the meantime, the output from the commands Nils suggested:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
*~ >>> agordejo --versionAgordejo 0.3.0* *~ >>>* *~ >>>*
*~ >>>ls -la /usr/bin/ray-jack_checker_daemonlrwxrwxrwx 1 root root 112 Jan 17 11:34 /usr/bin/ray-jack_checker_daemon -> /var/cache/private/pamac/raysession-git/pkg/raysession-git//usr/share/raysession/src/bin/ray-jack_checker_daemon * ~ >>> ~ >>>
*~ >>> file /usr/bin/ray-jack_checker_daemon /usr/bin/ray-jack_checker_daemon: broken symbolic link to /var/cache/private/pamac/raysession-git/pkg/raysession-git//usr/share/raysession/src/bin/ray-jack_checker_daemon * ~ >>> ~ >>>
*~ >>>lsattr /usr/bin/ray-jack_checker_daemonlsattr: Operation not supported While reading flags on /usr/bin/ray-jack_checker_daemon* ~ >>> ~ >>> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Sudo produces identical output for the above commands. It's worth mentioning I installed raysession from the AUR as an alternative because agordejo was already crashing before. Specifically the line: "*[nsmd] ../src/nsmd.cpp:703 launch(): ERROR:engine.start:Caught crash in execpthook. Trying too execute atexit anyway*" ~has been present before and after installing raysession. I did try uninstalling raysession and tried to start agordejo:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
*~ >>> agordejo[nsmd] ../src/nsmd.cpp:2544 main(): Using OSC port 39616[nsmd] ../src/nsmd.cpp:2603 main(): Session root is: /home/safepurge/NSM Sessions[nsmd] ../src/Endpoint.cpp:205 init(): Creating OSC serverNSM_URL=osc.udp://safepurge-ms7a71:39616/[nsmd] ../src/nsmd.cpp:2373 announce_gui(): A GUI announced to us from the URL osc.udp://127.0.0.1:39013/ http://127.0.0.1:39013/[nsmd] ../src/nsmd.cpp:2396 announce_gui(): Informing GUI that no session is running by sending two empty strings[nsmd] ../src/nsmd.cpp:2425 announce_gui(): Registration with GUI complete[nsmd] ../src/nsmd.cpp:1716 osc_list(): Listing sessions[nsmd] ../src/nsmd.cpp:1716 osc_list(): Listing sessions[nsmd] ../src/nsmd.cpp:1716 osc_list(): Listing sessions[nsmd] ../src/nsmd.cpp:1716 osc_list(): Listing sessions[nsmd] ../src/nsmd.cpp:1634 osc_new(): Creating new session "new session"qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 758, resource id: 4202067, major code: 40 (TranslateCoords), minor code: 0[nsmd] ../src/nsmd.cpp:1663 osc_new(): Informing GUI about running session name: new session with relative path /new session[nsmd] ../src/nsmd.cpp:735 launch(): Process jackpatch has pid: 32037[nsmd] ../src/nsmd.cpp:703 launch(): ERROR:engine.start:Caught crash in execpthook. Trying too execute atexit anywayLaunching jackpatchTraceback (most recent call last): File "/usr/bin/agordejo/engine/jackclient.py", line 69, in _setPlaybackSeconds File "/usr/bin/agordejo/qtgui/jacktransport.py", line 98, in _react_playbackSecondsTypeError: setValue(self, int): argument 1 has unexpected type 'float'[nsmd] ../src/nsmd.cpp:735 launch(): Process nsm-data has pid: 32038[nsmd] ../src/nsmd.cpp[nsmd] :703../src/nsmd.cpp launch():1206: command_client_to_quit(): Launching nsm-dataCommanding jackpatch.nUJWL to quit[nsmd] ../src/nsmd.cpp:1206 command_client_to_quit(): Commanding nsm-data.nKVGO to quit[nsmd] ../src/nsmd.cpp:1133 wait_for_killed_clients_to_die(): [nsmd] Waiting for killed clients to die.../src/nsmd.cpp:2474[nsmd] handle_signal_clean_exit()../src/nsmd.cpp: :1120 killed_clients_are_alive()Caught SIGNAL 15. Stopping nsmd.: [nsmd] Waiting for jackpatch.nUJWL../src/nsmd.cpp:1206 command_client_to_quit(): Commanding jackpatch.nUJWL to quit[nsmd] ../src/nsmd.cpp:1206 command_client_to_quit(): Commanding nsm-data.nKVGO to quit[nsmd] ../src/nsmd.cpp:1133 wait_for_killed_clients_to_die(): Waiting for killed clients to die.[nsmd] ../src/nsmd.cpp:1120 killed_clients_are_alive(): Waiting for jackpatch.nUJWL[nsmd] ../src/nsmd.cpp:1120[nsmd] killed_clients_are_alive()../src/nsmd.cpp: :1120 killed_clients_are_alive()Waiting for jackpatch.nUJWL: Waiting for jackpatch.nUJWL[nsmd] ../src/nsmd.cpp:343[nsmd] handle_client_process_death()../src/nsmd.cpp: :343 handle_client_process_death(): Client jackpatch.nUJWL terminated by server instruction.Client jackpatch.nUJWL terminated by server instruction.[nsmd] [nsmd] ../src/nsmd.cpp../src/nsmd.cpp:1120:1162 killed_clients_are_alive() wait_for_killed_clients_to_die(): : Waiting for nsm-data.nKVGOAll clients have died.[nsmd] ../src/nsmd.cpp:1120 killed_clients_are_alive(): Waiting for nsm-data.nKVGO[nsmd] ../src/nsmd.cpp:343 handle_client_process_death(): Client nsm-data.nKVGO terminated by server instruction.[nsmd] ../src/nsmd.cpp:1162 wait_for_killed_clients_to_die(): All clients have died.~ >>> * *~ >>>*
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Thankyou both for your assistance.
On Tue, Jan 18, 2022 at 4:18 AM arch-proaudio-request@lists.archlinux.org wrote:
Send arch-proaudio mailing list submissions to arch-proaudio@lists.archlinux.org
To subscribe or unsubscribe via the World Wide Web, visit https://lists.archlinux.org/listinfo/arch-proaudio or, via email, send a message with subject or body 'help' to arch-proaudio-request@lists.archlinux.org
You can reach the person managing the list at arch-proaudio-owner@lists.archlinux.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of arch-proaudio digest..."
Today's Topics:
- Agordejo crash on startup (Kevin Roth)
- Re: Agordejo crash on startup (bill-auger)
- Re: Agordejo crash on startup (Nils Hilbricht)
- Re: Agordejo crash on startup (bill-auger)
- Re: Agordejo crash on startup (bill-auger)
Message: 1 Date: Mon, 17 Jan 2022 11:58:08 -0800 From: Kevin Roth safepurge@gmail.com To: arch-proaudio@lists.archlinux.org Subject: [arch-proaudio] Agordejo crash on startup Message-ID: < CAOXpYygUE07wKd_YBjNG5OcuYP+E-mwd5t8b1Bkq2QD+yoPCKQ@mail.gmail.com> Content-Type: text/plain; charset="UTF-8"
As the title says, agordejo crashes immediately on startup:
*ERROR:engine.start:Caught crash in execpthook. Trying too execute atexit anywayTraceback (most recent call last): File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main return _run_code(code, main_globals, None, File "/usr/lib/python3.10/runpy.py", line 86, in _run_code exec(code, run_globals) File "/usr/bin/agordejo/__main__.py", line 13, in <module> File "/usr/bin/agordejo/qtgui/mainwindow.py", line 183, in __init__ File "/usr/bin/agordejo/qtgui/mainwindow.py", line 253, in _updateGUIWithCachedPrograms File "/usr/bin/agordejo/qtgui/addclientprompt.py", line 123, in updateWordlist File "/usr/bin/agordejo/engine/api.py", line 283, in getUnfilteredExecutables File "/usr/bin/agordejo/engine/findprograms.py", line 267, in buildCache_unfilteredExecutables File "/usr/bin/agordejo/engine/findprograms.py", line 267, in <listcomp> File "/usr/bin/agordejo/engine/findprograms.py", line 262, in isexe File "/usr/lib/python3.10/pathlib.py", line 1320, in is_file return S_ISREG(self.stat().st_mode) File "/usr/lib/python3.10/pathlib.py", line 1095, in stat return self._accessor.stat(self, follow_symlinks=follow_symlinks)PermissionError: [Errno 13] Permission denied: '/usr/bin/ray-jack_checker_daemon'*
Running manjaro with jack2. A similar error came and left a few months back. I found references to this issue here https://bugs.archlinux.org/task/68634 and here < https://www.laborejo.org/bugs/Done/agordejo-crash-on-start-using-pipewire-ja...
,
but no solutions as far as I can tell. I tried switching to pipewire, but the error persists. Raysession seems to work ok though. Any thoughts?
Message: 2 Date: Mon, 17 Jan 2022 22:26:48 -0500 From: bill-auger bill-auger@peers.community To: Kevin Roth via arch-proaudio arch-proaudio@lists.archlinux.org Subject: Re: [arch-proaudio] Agordejo crash on startup Message-ID: 20220117222648.162d93be@parabola.localdomain Content-Type: text/plain; charset=US-ASCII
several other important related packages were upgraded at the same time as the latest agordejo (eg: jack2, new-session-manager, jack2-dbus)
agordejo also crashed for me when i first upgraded it - i then restarted the system, and agordejo does not crash now
note:
Permission denied: '/usr/bin/ray-jack_checker_daemon'*
per that error message, you may also want to look at /usr/bin/ray-jack_checker_daemon - that is a foreign file, which does not exist in a clean arch system, and could cause many sorts of problems - the fact that it is the subject of a fatal error message is indicative of something abnormal; but there is not necessarily anything which the arch maintainers have done, or could do about it
# pkgfile /usr/bin/ray-jack_checker_daemon
if that is the cause of your crash, then it is not a bug for arch to handle - it may be an upstream bug, but it is not a bug within the context of "the arch system" - in that case, this is not a bug report; but a support request, for advice maintaining a "franken-system"
if a simple reboot does not help, then the path toward a solution, would be to firstly, remove all non-arch software from your system (retaining only mainline arch packages), then determine if the bug is still present - _then_ and only then, it would be a problem for the arch maintainers to address - in order to address that problem properly, the first triage step, which anyone would _need_ to do, would be to try reproducing the problem on a clean system if the problem can not be reproduced on a clean system, then it is not a bug - it is more likely a conflict caused by mixing unsupported third-party software into the protected main system
Message: 3 Date: Tue, 18 Jan 2022 11:59:18 +0100 From: Nils Hilbricht nils@hilbricht.net To: arch-proaudio@lists.archlinux.org Subject: Re: [arch-proaudio] Agordejo crash on startup Message-ID: 20220118115918.cfc10bb758c75cf9719eedf3@hilbricht.net Content-Type: text/plain; charset=US-ASCII
Hello Kevin,
could you please provide the output of:
agordejo --version
ls -la /usr/bin/ray-jack_checker_daemon
file /usr/bin/ray-jack_checker_daemon
lsattr /usr/bin/ray-jack_checker_daemon
And please tell if any of the above commands fail because of a permission error and then what the sudo version of the command reported.
If Agordejo is below version 0.3.1 please update first. The new arch community package came out on Saturday.
Nils
On Mon, 17 Jan 2022 11:58:08 -0800 safepurge at gmail.com (Kevin Roth) wrote:
As the title says, agordejo crashes immediately on startup:
*ERROR:engine.start:Caught crash in execpthook. Trying too execute atexit anywayTraceback (most recent call last): File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return
_run_code(code, main_globals, None, File "/usr/lib/python3.10/runpy.py", line 86, in _run_code exec(code, run_globals) File "/usr/bin/agordejo/__main__.py", line 13, in <module> File "/usr/bin/agordejo/qtgui/mainwindow.py", line 183, in __init__ File "/usr/bin/agordejo/qtgui/mainwindow.py", line 253, in _updateGUIWithCachedPrograms File "/usr/bin/agordejo/qtgui/addclientprompt.py", line 123, in updateWordlist File "/usr/bin/agordejo/engine/api.py", line 283, in getUnfilteredExecutables File
"/usr/bin/agordejo/engine/findprograms.py",
line 267, in buildCache_unfilteredExecutables File "/usr/bin/agordejo/engine/findprograms.py", line 267, in <listcomp> File "/usr/bin/agordejo/engine/findprograms.py", line 262, in isexe File "/usr/lib/python3.10/pathlib.py", line 1320, in is_file return S_ISREG(self.stat().st_mode) File "/usr/lib/python3.10/pathlib.py", line 1095, in stat return self._accessor.stat(self, follow_symlinks=follow_symlinks)PermissionError: [Errno 13] Permission denied: '/usr/bin/ray-jack_checker_daemon'*
Running manjaro with jack2. A similar error came and left a few months back. I found references to this issue here https://bugs.archlinux.org/task/68634 and here <
https://www.laborejo.org/bugs/Done/agordejo-crash-on-start-using-pipewire-ja...
, but no solutions as far as I can tell. I tried switching to pipewire, but the error persists. Raysession seems to work ok though. Any thoughts?
Message: 4 Date: Tue, 18 Jan 2022 07:04:23 -0500 From: bill-auger bill-auger@peers.community To: Nils Hilbricht via arch-proaudio arch-proaudio@lists.archlinux.org Subject: Re: [arch-proaudio] Agordejo crash on startup Message-ID: 20220118070423.77de1c91@parabola.localdomain Content-Type: text/plain; charset=US-ASCII
as a follow-up, i believe that i found a reproducible procedure to isolate the bug
my crash yesterday was probably not due to the upgraded release; but due to a peculiar environment quirk - namely, i had /root/.gem/ruby/3.0.0/bin/ in the shell PATH; which was not the case after i rebooted
agordejo starts properly: $ PATH=$PATH:/etc/any-thing-works agordejo
agordejo crashes: $ PATH=$PATH:/root/any-thing-fails agordejo
curiously, /root does not induce the crash: $ PATH=$PATH:/etc/any-thing-works agordejo
Message: 5 Date: Tue, 18 Jan 2022 07:09:45 -0500 From: bill-auger bill-auger@peers.community To: bill-auger via arch-proaudio arch-proaudio@lists.archlinux.org Subject: Re: [arch-proaudio] Agordejo crash on startup Message-ID: 20220118070945.39a596f1@parabola.localdomain Content-Type: text/plain; charset=US-ASCII
On Tue, 18 Jan 2022 07:04:23 -0500 bill-auger wrote:
curiously, /root does not induce the crash: $ PATH=$PATH:/etc/any-thing-works agordejo
my bad (copy-paste think-o) - i intended such:
curiously, /root does not induce the crash: $ PATH=$PATH:/root agordejo
Subject: Digest Footer
arch-proaudio mailing list arch-proaudio@lists.archlinux.org https://lists.archlinux.org/listinfo/arch-proaudio
End of arch-proaudio Digest, Vol 31, Issue 2
On Tue, 18 Jan 2022 13:36:32 -0800 Kevin wrote:
Pamac manager lists Agordejo 0.3.0-1 as the latest release.
that is the latest version; but when reporting bugs, only the 'pacman' package manager and the true /etc/pacman.{conf,d/mirrorlist} should be considered - like raysession, pamac is unsupported software - bug reports should be directed toward the AUR maintainers; because only they can address them in any way
i am not certain if this list is appropriate - is this list intended for general pro-audio tech support (eg: including third-party software)? - or is third-party software off-topic on this list? - perhaps i am over-emphasizing that distinction (that this thread may be entirely unrelated to any standard arch software) - the linuxaudio lists/forum/IRC/etc are much more used/popular for such tech support questions, no? - that is why ive assumed this list had an intention, more special than as another general computer music forum
On Tue, 18 Jan 2022 13:36:32 -0800 Kevin wrote:
*~ >>> file /usr/bin/ray-jack_checker_daemon /usr/bin/ray-jack_checker_daemon: broken symbolic link to /var/cache/private/pamac/raysession-git/pkg/raysession-git//usr/share/raysession/src/bin/ray-jack_checker_daemon
the above strongly implicates the unsupported raysession and/or pamac software, as the source of the problem; which was my previous speculation
if this were my problem (the first triage step), i would uninstall raysession, pamac, and all software which was ever installed by pamac (or simulate that state in a VM), to demonstrate that removing one or the other of raysession/pamac, resolves the problem (allows agordejo to start)
demonstrating so, would strongly absolve agordejo (and all other arch software) as the culprits - then, at least it would be more obvious which people/forum would be best for this discussion
does agordejo start, when that raysession package is not installed?
On Wed, 19 Jan 2022 02:25:26 -0500 bill-auger wrote:
On Tue, 18 Jan 2022 13:36:32 -0800 Kevin wrote:
Pamac manager lists Agordejo 0.3.0-1 as the latest release.
that is the latest version
typo, sry - 0.3.1 is the current arch release
Hello Nils and Bill,
Pamac manager lists Agordejo 0.3.0-1 as the latest release.
Hello,
we are dealing with several unrelated problems here.
0) For Agordejo bug reports use https://laborejo.org/bugs/
1) Kevin, you are using Manjaro and not Arch. While I personally have nothing against that you have to accept the consequences of posting to an Archlinux mailinglist, including the suggestion to basically destroy your Manjaro install and convert it manually to Arch. The more mundane consequence is that Manjaro is a slow distro and their packagers are always behind Arch when it comes to new releases.
You could simply download Agordejo 0.3.1 from https://www.laborejo.org/downloads and install it yourself. It's just ./configure --prefix=/usr && make && sudo make install
2) Kevin, you have a broken symlink and Agordejo didn't expect that and crashed. This is indeed a misconfigured system, but it shouldn't crash my program, which I need to fix. I also believe that I fixed that already in 0.3.1, but it may be a different symlink problem. In any case I will try to replicate that and try to prevent the crash. Your own solution is to make sure that there are no broken symlinks. If you use Agordejo, which is New-Session-Manager, you don't need RaySession in the first place anyway.
3) As a future suggestion, Kevin, please try to read and understand the logs you are posting. I admit they are long and verbose, but the problem that you have a broken symlink was in fact there from the beginning. Your assumptions about the other two problems you indentified as "the same" were wrong. I believe you saw the first line which is just "there was a crash, here comes the log" and assumed all three problems were the same. (meaning *ERROR:engine.start:Caught crash in execpthook. Trying too execute atexit anyway. Traceback...)
3) There is a different problem reported by bill-auger regarding root and PATHs. I will look into that, thank you for the report.
Thank you all for making it possible that I can fix my software!
Nils
On Tue, 18 Jan 2022 13:36:32 -0800 Kevin Roth via arch-proaudio arch-proaudio@lists.archlinux.org wrote:
arch-proaudio@lists.archlinux.org