segmentation fault on start

[dhankin-gh]

running on latest pi image with all listed packages installed. success in building ia, but when attempting to run ia, come up with segmentation fault (along with other issues).

running ia from terminal gives me:

libEGL warning: DRI2: failed to authenticate qt5ct: using qt5ct plugin [2020-03-11 22:46:45.060362] [0x71de62e0] [warning] [OpenAuto] [Configuration] failed to read configuration file: openauto.ini, error: openauto.ini: cannot open file. Using default configuration. qt5ct: palette support is disabled qt5ct: custom style sheet is disabled Segmentation fault

and running from gdb gives me:

Starting program: /home/pi/intelligent-auto/bin/ia [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". [New Thread 0x71668370 (LWP 2088)] libEGL warning: DRI2: failed to authenticate [New Thread 0x6be74370 (LWP 2089)] [New Thread 0x6b473370 (LWP 2090)] [New Thread 0x6ac72370 (LWP 2091)] [New Thread 0x6a0ff370 (LWP 2092)] [New Thread 0x698fe370 (LWP 2093)] [New Thread 0x690fd370 (LWP 2094)] [New Thread 0x686fc370 (LWP 2095)] [New Thread 0x67cff370 (LWP 2096)] QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' [2020-03-11 23:09:16.049848] [0x71e922e0] [warning] [OpenAuto] [Configuration] failed to read configuration file: openauto.ini, error: openauto.ini: cannot open file. Using default configuration. [New Thread 0x674fe370 (LWP 2097)] [Detaching after fork from child process 2098] org.kde.bluez: GetManagerJob Error: "Cannot find org.bluez.Media1 object!"

Thread 1 "ia" received signal SIGSEGV, Segmentation fault. 0x7684e024 in BluezQt::Adapter::devices() const () from /usr/lib/arm-linux-gnueabihf/libKF5BluezQt.so.6

running on rpi 3 model b i believe (no bluetooth devices, is this related?)

[rsjudka]

looks like an error throw by BluezQt.. Does your bluetooth work at all? Like do you have the proper bluetooth services configured? Can you run sudo service bluetooth status and let me know what you see?

[dhankin-gh]

● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Wed 2020-03-11 23:05:35 GMT; 31min ago Docs: man:bluetoothd(8) Main PID: 1873 (bluetoothd) Status: "Running" Tasks: 1 (limit: 2200) Memory: 1020.0K CGroup: /system.slice/bluetooth.service └─1873 /usr/lib/bluetooth/bluetoothd

Mar 11 23:05:35 raspberrypi systemd[1]: Starting Bluetooth service... Mar 11 23:05:35 raspberrypi bluetoothd[1873]: Bluetooth daemon 5.50 Mar 11 23:05:35 raspberrypi systemd[1]: Started Bluetooth service. Mar 11 23:05:35 raspberrypi bluetoothd[1873]: Starting SDP server Mar 11 23:05:35 raspberrypi bluetoothd[1873]: Bluetooth management interface 1.1

[rsjudka]

ah okay so it looks like you're missing the actual enpoints

Mar 11 16:15:46 xps9370l bluetoothd[1328]: Bluetooth management interface 1.14 initialized
Mar 11 16:16:06 xps9370l bluetoothd[1328]: Endpoint registered: sender=:1.379 path=/MediaEndpoint/A2DPSource
Mar 11 16:16:06 xps9370l bluetoothd[1328]: Endpoint registered: sender=:1.379 path=/MediaEndpoint/A2DPSink
Mar 11 16:16:14 xps9370l bluetoothd[1328]: /org/bluez/hci0/dev_00_AD_E6_E1_F7_73/fd0: fd(35) ready

the bluetooth library depends on those to query the devices and whatnot

but now to figure out why they arent being registered... lol

[dhankin-gh]

does the library require an actual Bluetooth device? if so then there's the problem, there is no Bluetooth on my device.

[rsjudka]

yeah that would be a problem lol

luckily all I need to do is check the adapter exists and if not ignore all the bluetooth stuff, will push something to master in a bit

[rsjudka]

Just pushed a fix to master, please let me know if you can get that to work!

[dhankin-gh]

Not tested on my hardware, but have tested on RPI VM and does now load. when plugging in a device it does hang on creating a device, but does continue and works fine

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' [2020-03-12 03:54:21.428549] [0xa43fdb40] [info] [OpenAuto] [App] Waiting for device... [2020-03-12 03:54:21.472593] [0xa3bfcb40] [info] [OpenAuto] [App] Devices enumeration result: true [2020-03-12 03:54:43.609326] [0xa4bfeb40] [info] [OpenAuto] [App] Device connected. [2020-03-12 03:54:43.613473] [0xb2670800] [debug] [OpenAuto] [AudioInput] create. [2020-03-12 03:54:43.624211] [0xb2670800] [debug] [OpenAuto] [QtVideoOutput] create. [2020-03-12 03:54:43.747789] [0xb2670800] [debug] [OpenAuto] [LocalBluetoothDevice] create. Cannot find a running Bluez. Please check the Bluez installation. [2020-03-12 03:55:58.825960] [0xa4bfeb40] [info] [OpenAuto] [AndroidAutoEntity] start. [2020-03-12 03:55:58.826003] [0xa4bfeb40] [info] [OpenAuto] [AudioInputService] start. [2020-03-12 03:55:58.826147] [0xa4bfeb40] [info] [OpenAuto] [AudioService] start, channel: MEDIA_AUDIO [2020-03-12 03:55:58.826169] [0xa4bfeb40] [info] [OpenAuto] [AudioService] start, channel: SPEECH_AUDIO [2020-03-12 03:55:58.826197] [0xa4bfeb40] [info] [OpenAuto] [AudioService] start, channel: SYSTEM_AUDIO [2020-03-12 03:55:58.826225] [0xa4bfeb40] [info] [OpenAuto] [SensorService] start. [2020-03-12 03:55:58.826251] [0xa4bfeb40] [info] [OpenAuto] [VideoService] start. [2020-03-12 03:55:58.826283] [0xa4bfeb40] [info] [OpenAuto] [BluetoothService] start. [2020-03-12 03:55:58.826312] [0xa4bfeb40] [info] [OpenAuto] [InputService] start. [2020-03-12 03:55:58.897819] [0xa53ffb40] [info] [OpenAuto] [AndroidAutoEntity] version response, version: 1.5, status: 0

[rsjudka]

I bet it's hanging on the Cannot find a running Bluez. Please check the Bluez installation. message. This is going to be within OpenAuto, so I'll have to poke around and see if there's a way I can if Bluetooth exists before attempting to do anything with it.

[dhankin-gh]

in the debug info it does say:

[debug] [OpenAuto] [LocalBluetoothDevice] create. Cannot find a running Bluez. Please check the Bluez installation

so it is open auto. seemed to only be on the initial startup anyway, and just tested on actual hardware and was it actually ruins now, so initial problem is solved. thanks! looking forward to seeing more development from this project