Upgrade from 11/25/2209: fsodeviced

[elhennig]

The upgrade mentioned above leads to the following error:

$ /usr/bin/fsodeviced
-sh: /usr/bin/fsodeviced: No such file or directory

Reason is the wrong path in /etc/init.d/fsodeviced as the daemon resides in /usr/sbin/fsodeviced now.

Starting the fsodeviced with the proper path leads to
(process:2020): DEBUG: plugin.vala:502: kernel26_powersupply fso_register_function()
(process:2020): DEBUG: plugin.vala:99: info fso_register_function()
(process:2020): DEBUG: plugin.vala:253: kernel26_rtc fso_register_function()
(process:2020): DEBUG: plugin.vala:178: input fso_register_function()
(process:2020): DEBUG: plugin.vala:177: accelerometer_lis302 fso_factory_function
(process:2020): DEBUG: plugin.vala:349: fsodeviced.accelerometer fso_register_function()
(process:2020): DEBUG: plugin.vala:196: kernel26_display fso_register_function()
(process:2020): DEBUG: plugin.vala:487: input fso_register_function()
(process:2020): DEBUG: plugin.vala:523: input fso_register_function()
(process:2020): DEBUG: plugin.vala:347: input fso_register_function()
* glibc detected * /usr/sbin/fsodeviced: malloc(): memory corruption: 0x0004a120 *
Aborted

[elhennig]

output of strace /usr/sbin/fsodeviced

[TAsn]

try now.

[shishz]

the initscript still points to /usr/bin/fsodeviced instead of /usr/sbin/ (or could be some problem with opkg upgrade?). After I changed that by hand, fsodeviced started up for me here.

[elhennig]

Yes, after the upgrade of frameworkd.conf yesterday evening and fixing the path in the init script of fsodeviced everything works again.

The path in the init script should be fixed, though.

[Heinervdm]

Just checked too, it's fixed.