Roomba being enabled causes hass to segfault

[cmsimike]

Home Assistant release with the issue:
.84.6

Last working Home Assistant release (if known):
.82

Operating environment (Hass.io/Docker/Windows/etc.):
python 3 on ubuntu virtualenv
Component/platform:
Vacuum/roomba
https://www.home-assistant.io/components/vacuum.roomba/

Description of problem:
After the upgrade, with the roomba component enabled, hass segfaults

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

vacuum:
  - platform: roomba
    host: 10.18.21.120
    username: x
    password: y
    name: roomba

Traceback (if applicable):

2019-01-03 17:04:13 DEBUG (MainThread) [homeassistant.components.vacuum.roomba] Initializing communication with host 10.18.21.120
Segmentation fault (core dumped)

That is the only thing in the log

Additional information:
With the roomba config commented out, hass starts no problem.

The log for the roomba is: homeassistant.components.vacuum.roomba: debug

[drjared88]

I am seeing the exact same issue. I am unable to find a root cause or any error messages. It just causes home assistant to hard crash.

[cmsimike]

@drjared88 thank you for the reminder, I fixed my issue. I blew away the virtualenv I had hass setup in, and recreated it. Fixed it for me. Hopefully it fixes it for you too.

I am going to close this out since my issue was solved.

[drjared88]

Can you elaborate a little on what you did? I deleted my /srv/homeassistant folder and recreated it and reinstalled home assistant. The same issue occurred. Is this what you did?

[cmsimike]

@drjared88 yup, that's it.

[drjared88]

@cmsimike Hmm I've tried it twice now with the same crashes everytime. Don't know what else to try...