# Volume 2: warning accessibility bus and segmentation fault on Travis
**URL:** https://discourse.julialang.org/t/volume-2-warning-accessibility-bus-and-segmentation-fault-on-travis/9370
**Category:** General Usage
**Tags:** question, ci
**Created:** [February 27, 2018, 4:06pm UTC](https://discourse.julialang.org/t/volume-2-warning-accessibility-bus-and-segmentation-fault-on-travis/9370 "2018-02-27T16:06:38Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@yakir12](https://discourse.julialang.org/u/yakir12)
#### Post date: [February 27, 2018, 4:06pm UTC](https://discourse.julialang.org/t/volume-2-warning-accessibility-bus-and-segmentation-fault-on-travis/9370/1 "2018-02-27T16:06:38Z")
So this is in reference to
> [@Travis woes: warning accessibility bus and segmentation fault](https://discourse.julialang.org/t/travis-woes-warning-accessibility-bus-and-segmentation-fault/9362):
>
> Hi CI wizards, I’m having some trouble with Travis and was wondering if someone could lend me some wisdom. I’m getting a few of these warnings: \*\* (julia:6922): WARNING \*\*: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files and then a segmentation fault right when the test calls a function that plots a few frames to a gif file using the GR backend. Ironically, I would get segmentation faults on m…
I thought that the lack of `ffmpeg` on Travis caused the warnings and segmentation fault reported on in that post, but I was wrong. [Here](https://api.travis-ci.org/v3/job/346833767/log.txt)’s the log of my most recent tests. I’m convinced that it has something to do with the fact that I’m saving a `gif` file and testing for its existence. I’m using `Plots.jl` with `GR` backend.
I tried a minimal test:
```julia
using Base.Test, Plots
anim = @animate for i=1:2
plot(rand(2))
end
name = tempname()*".gif"
gif(anim, name)
@test isfile(name)
```
and it worked. So not sure why my real tests should fail so miserably.
---
### Author:  [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [February 27, 2018, 5:45pm UTC](https://discourse.julialang.org/t/volume-2-warning-accessibility-bus-and-segmentation-fault-on-travis/9370/2 "2018-02-27T17:45:36Z")
Opening the third topic about essentially the same question makes this issue very difficult to follow. Nevertheless, I would bisect the issue by commenting out certain parts of the tests, starting with [saving gifs](https://github.com/yakir12/TrackRoots.jl/blob/master/src/saving.jl#L50).
---
### Author:  [@yakir12](https://discourse.julialang.org/u/yakir12)
#### Post date: [February 27, 2018, 7:16pm UTC](https://discourse.julialang.org/t/volume-2-warning-accessibility-bus-and-segmentation-fault-on-travis/9370/3 "2018-02-27T19:16:44Z")
Yea, I wasn’t sure how best I should post about this. I noticed that having a long self-replies post doesn’t get much attention. And since it wasn’t ffmpeg then it made sense to separate it this way. So do you think it would have been better with just the one (multiple self-replied) post?
I’m sure that commenting out the plotting section will resolve the problem. I’ll try it just to be sure though. brb
---
### Author:  [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [February 27, 2018, 7:29pm UTC](https://discourse.julialang.org/t/volume-2-warning-accessibility-bus-and-segmentation-fault-on-travis/9370/4 "2018-02-27T19:29:23Z")
> [@yakir12](#):
>
> So do you think it would have been better with just the one (multiple self-replied) post?
It would make it easier for people who want to help you to look up the source and the error messages directly.
> [@yakir12](#):
>
> I’m sure that commenting out the plotting section will resolve the problem.
If that helps, then you could try to isolate the problem within that function.
---
### Author:  [@yakir12](https://discourse.julialang.org/u/yakir12)
#### Post date: [February 27, 2018, 7:46pm UTC](https://discourse.julialang.org/t/volume-2-warning-accessibility-bus-and-segmentation-fault-on-travis/9370/5 "2018-02-27T19:46:18Z")
Oh lord. In an attempt to follow your advice I replied to this in the [former](https://discourse.julialang.org/t/travis-woes-warning-accessibility-bus-and-segmentation-fault/9362/5) post, _thinking and believing_ I could just erase this one (since there isn’t that much new information here). But I can’t remove this post… So now the confusion is even larger (evil laughter). Right, feel free to ignore this post, and reply in the other one (i.e. [here](https://discourse.julialang.org/t/travis-woes-warning-accessibility-bus-and-segmentation-fault/9362/5)). Thanks and sorry for the mess.