App doesn't seem to autostart on kde in a Manjaro installation #49
Comments
|
I'm under the impression the app might be crashing during or immediately
after the system restarts. To test that, I am using a process monitor
script:
-----
#!/bin/bash
if [[ -z "$1" ]];then
echo "ERROR: must specify program"
exit 1
fi
while (( 0 == 0 ));do
$@ &
pid=`jobs -l | awk '{print $2}'`
wait $pid
done
----
I've been running it as a login script to call jamesdsp like
"~/process_monitor.sh jamesdsp -t".
By doing that, I am certain that even if the app eventually crashes, it
will be running again in no time.
…On Tue, 3 May 2022 at 20:47, Tim Schneeberger ***@***.***> wrote:
I noticed this too on my installation after a recent KDE update. I'll look
into it
—
Reply to this email directly, view it on GitHub
<#49 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABVG27JMNNHQU7MLBBPLE53VIG3IJANCNFSM5UJT7YVA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
If the app was compiled with crash reporting support (by default), it should write a crash dump into Does your workaround fix the issue for you? |
|
The workaround works, but certainly not as elegant as, say, a systemd
service, which I would love to see made available in the future. I'm
annexing crash-prev.dmp as crash.dmp looks empty. Also, application and
application-prev.log.
…On Wed, 4 May 2022 at 10:57, Tim Schneeberger ***@***.***> wrote:
If the app was compiled with crash reporting support (by default), it
should write a crash dump into /tmp/jamesdsp/crash.dmp and a log to
/tmp/jamesdsp/application.log .
Does your workaround fix the issue for you?
Perhaps KDE launches the auto-start apps a bit too early when Pulse or
Pipewire are not yet fully ready. If there's no pulse/PW server present,
this app will terminate itself and refuse to run at the moment.
—
Reply to this email directly, view it on GitHub
<#49 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABVG27NJBS4TMRGAEVU6H3DVIJ65HANCNFSM5UJT7YVA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I missed one of the files.
…On Wed, 4 May 2022 at 11:10, Cláudio Bichuetti ***@***.***> wrote:
The workaround works, but certainly not as elegant as, say, a systemd
service, which I would love to see made available in the future. I'm
annexing crash-prev.dmp as crash.dmp looks empty. Also, application and
application-prev.log.
On Wed, 4 May 2022 at 10:57, Tim Schneeberger ***@***.***>
wrote:
> If the app was compiled with crash reporting support (by default), it
> should write a crash dump into /tmp/jamesdsp/crash.dmp and a log to
> /tmp/jamesdsp/application.log .
>
> Does your workaround fix the issue for you?
> Perhaps KDE launches the auto-start apps a bit too early when Pulse or
> Pipewire are not yet fully ready. If there's no pulse/PW server present,
> this app will terminate itself and refuse to run at the moment.
>
> —
> Reply to this email directly, view it on GitHub
> <#49 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABVG27NJBS4TMRGAEVU6H3DVIJ65HANCNFSM5UJT7YVA>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
I am experiencing this same issue on Fedora 36. I just can't get it to start at startup, always have to manually start it. Log: |
|
same error here on archlinux. I need to start it manually, when i check the autostart option on configs it register on the "Tweaks" but does not work. There is some crash on dump files but i'm not sure if this crash comes from autostart or not. |
|
This issue is very likely fixed by https://github.com/Audio4Linux/JDSP4Linux/releases/tag/2.5.0. It adds some additional startup logic that should handle this correctly. |
Even though there's an entry to JamesDSP for Linux Systray in kde's autostart settings, the application doesn't load automatically. I need to manually load the app from the application launcher. Running jamesdsp -t on terminal doesn't pop any error out.
The text was updated successfully, but these errors were encountered: