I updated my Vero 4K+ device to the August update with the new 4.9 kernel and unfortunately librespot doesn’t work anymore (I use it with the raspotify wrapper). Any execution of the librespot binary results in ‘Illegal instruction’.
I also made a core dump, which I can upload if necessary. Some basic output as I have no idea what is useful to debug this:
osmc@osmc0:~$ gdb /usr/bin/librespot core
GNU gdb (Debian 8.2.1-2+b3) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/librespot...done.
[New LWP 9376]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Core was generated by `/usr/bin/librespot'.
Program terminated with signal SIGILL, Illegal instruction.
#0 0xab0911d0 in num_cpus::linux::get_num_cpus ()
(gdb) where
#0 0xab0911d0 in num_cpus::linux::get_num_cpus ()
#1 0xab067a48 in tokio::runtime::threadpool::builder::Builder::new ()
#2 0xab06370c in tokio::runtime::threadpool::Runtime::new ()
#3 0xab05444c in tokio_core::reactor::Core::new ()
#4 0xaac9c480 in librespot::main ()
#5 0xab1e98f4 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) list +
1 library/std/src/lib.rs: No such file or directory.
@sam_nazarko I have the same problem with veracrypt after update.
Looks strongly related. Thus writing it here.
After update the verarcypt started to fail on start with
Still the same thing.
osmc@osmc:~$ gdb veracrypt
GNU gdb (Debian 8.2.1-2+b3) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type “show copying” and “show warranty” for details.
This GDB was configured as “arm-linux-gnueabihf”.
Type “show configuration” for configuration details.
For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/.
For help, type “help”.
Type “apropos word” to search for commands related to “word”…
Reading symbols from veracrypt…(no debugging symbols found)…done.
(gdb) run
Starting program: /usr/bin/veracrypt
[Thread debugging using libthread_db enabled]
Using host libthread_db library “/lib/arm-linux-gnueabihf/libthread_db.so.1”.
Program received signal SIGILL, Illegal instruction.
0xaab1ea98 in ?? ()
(gdb) bt #0 0xaab1ea98 in ?? () #1 0xaab221e0 in ?? () #2 0x00000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)
Will gladly run some tests if needed.
Would be nice to understand what is this about.
@sam_nazarko you indicated you know what the issue is. Could you please share it with us? Maybe it could help us to at least find a workaround until this issue is fixed.
SIGILL error with librespot was reported previously for 4.9 kernel testing thread in January, but it was considered not important then. Hope that there will be solution this time. For now, it is easier get an old raspberry pi for Spotify Connect and not hack around on the platform that has excellent video support but was not meant to be an audiophile player (Vero 4K)
I completely understand that this issue gets a lower priority than others more directly related to core functionality of OSMC and the Vero. However, I would really appreciate it if you could share the few more details that you apparently know about this bug. It could help me and others to find a workaround while we wait for a solution.
Add the following line: deb http://apt.osmc.tv buster-devel main
Run the following commands to update: sudo apt-get update && sudo apt-get dist-upgrade && reboot
Your system should have have received the update.
Please see if the issue is resolved.
I also recommend you edit /etc/apt/sources.list again and remove the line that you added after updating. This will return you to the normal update channel.