# Travis woes: warning accessibility bus and segmentation fault

**URL:** https://discourse.julialang.org/t/travis-woes-warning-accessibility-bus-and-segmentation-fault/9362
**Category:** General Usage
**Tags:** question, travis
**Created:** [February 27, 2018, 10:05am UTC](https://discourse.julialang.org/t/travis-woes-warning-accessibility-bus-and-segmentation-fault/9362 "2018-02-27T10:05:07Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![yakir12](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/yakir12/32/297_2.png) [@yakir12](https://discourse.julialang.org/u/yakir12)
#### Post date: [February 27, 2018, 7:41pm UTC](https://discourse.julialang.org/t/travis-woes-warning-accessibility-bus-and-segmentation-fault/9362/5 "2018-02-27T19:41:02Z")

</div>

I thought that the lack of `ffmpeg` on Travis caused all the warnings and segmentation fault, but I was wrong: after successfully adding `ffmpeg` to Travis the warnings and segmentation fault were still there. [Here](https://api.travis-ci.org/v3/job/346833767/log.txt)’s the log of my most recent tests.

Following @Tamas_Papp’s advice on commenting out the plotting parts to see if it helps I found out that:

1. The [warning: error retrieving accessibility bus address](https://travis-ci.org/yakir12/TrackRoots.jl/jobs/346937761#L1204) is still there
2. The segmentation fault is gone

So now I have no idea what causes those warnings, but the segmentation occurs in the plotting part. I’ll continue to comments out parts of the plotting in an attempt to pin point where the fault occurs.

---

_[View the full topic](https://discourse.julialang.org/t/travis-woes-warning-accessibility-bus-and-segmentation-fault/9362)._