You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i have just updated the synology package for AirConnect release 0.2.26.0 with your newest binaries.
I am using the airupnp and aircast binaries for arch x86-64 for testing.
If i start the package with a high-privileged user (such as root) i can start airupnp without any problems and it is running fine.
If i am trying to start airupnp with a low-privileged user, airupnp crashes directly after the start without an error but it generates a core dump and is throwing a seg faults in the messages log.
For the synology package i need to start the binaries as a low-privileged user.
2020-05-27T20:02:27+02:00 xx kernel:[76992.162360] airupnp[19007]: segfault at 0 ip 00007f5a8cb314bd sp 00007f5a87b69db0 error 4in libc-2.20-2014.11.so[7f5a8cac7000+19b000]2020-05-27T20:02:27+02:00 xx coredump: Process airupnp[18995] dumped core on signal [11].
I have used the same scripts, build steps, same low-privileged user etc. as of version 0.2.25.0. So it should be no problem with the synology package.
Version 0.2.25.0 is working fine for the moment.
Startup commands:
i am not using the config file in my tests (no file exists)
Hi @philippe44
i have just updated the synology package for AirConnect release
0.2.26.0
with your newest binaries.I am using the
airupnp
andaircast
binaries for archx86-64
for testing.If i start the package with a high-privileged user (such as root) i can start
airupnp
without any problems and it is running fine.If i am trying to start
airupnp
with a low-privileged user, airupnp crashes directly after the start without an error but it generates a core dump and is throwing a seg faults in the messages log.For the synology package i need to start the binaries as a low-privileged user.
I have used the same scripts, build steps, same low-privileged user etc. as of version
0.2.25.0
. So it should be no problem with the synology package.Version
0.2.25.0
is working fine for the moment.Startup commands:
i am not using the config file in my tests (no file exists)
Log `0.2.26.0` with low-privileged user - Not OK
Log `0.2.25.0` - OK
Log `0.2.26.0` with root user - OK
Thanks for your help,
René
The text was updated successfully, but these errors were encountered: