After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 789259 - gstreamer changed by monitor installation
gstreamer changed by monitor installation
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
unspecified
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-10-20 16:42 UTC by Joe Mansheim
Modified: 2017-11-01 12:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Joe Mansheim 2017-10-20 16:42:25 UTC 
On Xubuntu 17.04 on an ACER inspire one D255, everything worked until I plugged in a Samsung 173s monitor. 
Then the parole media player wouldn't start;
**(parole:4258): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-8AMRZHzBJ3: Connection refused Segmentation fault (core dumped)

I then tried sudo parole. I got the same warning but parole did run.

I tried using a second computer and got the same results.
Comment 1 Tim-Philipp Müller 2017-10-24 00:22:10 UTC 
This sounds like a pretty serious bug somewhere, but I don't think it's related to GStreamer. What makes you think it's a GStreamer issue?

Do you happen to be able to get a strack trace?
Comment 2 Joe Mansheim 2017-11-01 12:45:46 UTC 
I believed it was gstreamer because I installed other media players that didn't rely on gstreamer and they ran properly.
Since then, I have upgraded from xubuntu 17.04 to 17.10 and the problem went away. 
Now I suspect it was OS related.
Comment 3 Tim-Philipp Müller 2017-11-01 12:56:09 UTC 
Thanks for following up and letting us know it's no longer a problem.

I'll close the bug then.