Because Xwindows needs to know where to send output. Without that, or similar statement, X won't start, and everything else that depends on it starting won't go either. Linux for blind general discussion writes: > I found it, When this line is commented out that XCB error returns true line > goes away and when uncommented the error returns. > export DISPLAY=taf:0.0 > > Why that should be doing this, I cannot say. > On Tue, 12 Sep 2017, Linux for blind general discussion wrote: > > > Date: Tue, 12 Sep 2017 13:09:37 > > From: Linux for blind general discussion <blinux-list@xxxxxxxxxx> > > To: Linux for blind general discussion <blinux-list@xxxxxxxxxx> > > Subject: Re: speechdispatcher-git > > > > So, some step beyond that entry in your ~/.bashrc is mucking things up. > > Your assignment is to find out what's mucking things up, and to fix it. > > There's no way we can help you from this kind of general statement > > because it's far too short of specifics. > > > > Linux for blind general discussion writes: > > > I put paplay /usr/share/sounds/freedesktop/stereo/alarm-clock-elapsed.oga in > > > my .bashrc file as the second line in the file. Interesting results too, > > > but I don't know what these mean. On boot up from a poweroff state, the > > > sound file plays with no error. Any subsequent attempt to play the sound > > > file has the error statement come back. > > > > > > On Mon, 11 Sep 2017, Linux for blind general discussion wrote: > > > > > > > Date: Mon, 11 Sep 2017 04:50:37 > > > > From: Linux for blind general discussion <blinux-list@xxxxxxxxxx> > > > > To: Linux for blind general discussion <blinux-list@xxxxxxxxxx> > > > > Subject: Re: speechdispatcher-git > > > > > > > > To be fully certain, you might try the command immediately after > > > > booting. You should run the command before issuing any other having > > > > absolutely anything to do with sound, i.e. not dispatching > > > > speech-dispatcher. > > > > > > > > Linux for blind general discussion writes: > > > > > The sound system isn't perfect. When I used paplay to play an .oga file I > > > > > got xcb_connection_has_error() returned true. > > > > > On Sun, 10 Sep 2017, Linux for blind general discussion wrote: > > > > > > > > > > > Date: Sun, 10 Sep 2017 06:08:04 > > > > > > From: Linux for blind general discussion <blinux-list@xxxxxxxxxx> > > > > > > To: Linux for blind general discussion <blinux-list@xxxxxxxxxx> > > > > > > Subject: Re: speechdispatcher-git > > > > > > > > > > > > Linux for blind general discussion writes: > > > > > > > Curiosity for the most part. I wouldn't do auto-login on a machine. > > > > > > > > > > > > > > > > > > > For the most part that's probably the best approach. However, there are > > > > > > exceptions, and the current discussion illustrates one such. > > > > > > > > > > > > We're being asked to help someone get their Orca plus speech-dispatcher > > > > > > setup working. As with any debugging situation, if the problem isn't > > > > > > immediately obvious, a good approach is to simplify the environment in > > > > > > order to isolate the issue. > > > > > > > > > > > > So, in the current instance, launching startx from a standard text > > > > > > console would quickly show whether there are issues specifically with > > > > > > the Orca setup, or not. The only caveat here is any required unique startx > > > > > > tweak, probably an .xinitrc with: > > > > > > > > > > > > exec gnome-session > > > > > > > > > > > > Yes, it's possibly the case that one could just as easily login on the > > > > > > text console, but that can require some configuration, too, e.g. > > > > > > possibly the beep on backspace hasn't been configured. That wouldn't be > > > > > > an issue with Speakup, or some other console level screen reader, of > > > > > > course. And, one could always test the console environment with with a > > > > > > beep command like: > > > > > > > > > > > > echo Ctrl+g > > > > > > > > > > > > Now, if the situation is such that multiple individuals use the > > > > > > computer, some solution involving gdm is clearly desirable. But, if > > > > > > there's only one person using the computer, I strongly question the > > > > > > value of gdm, though login to the computer is probably still advisable. > > > > > > > > > > > > But, if this individual, the only one using the computer, also lives > > > > > > alone and rarely entertains untrusted individuals, even an auto login > > > > > > could be reasonable. > > > > > > > > > > > > Just my thoughts here. > > > > > > > > > > > > Janina > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, 8 Sep 2017, Linux for blind general discussion wrote: > > > > > > > > > > > > > > > Date: Fri, 8 Sep 2017 18:59:25 > > > > > > > > From: Linux for blind general discussion <blinux-list@xxxxxxxxxx> > > > > > > > > To: Linux for blind general discussion <blinux-list@xxxxxxxxxx> > > > > > > > > Subject: Re: speechdispatcher-git > > > > > > > > > > > > > > > > OK, let me try to be a bit more specific. > > > > > > > > > > > > > > > > Why do you think you need a graphical login manager? What, exactly is it > > > > > > > > doing for you? > > > > > > > > > > > > > > > > I ask this question because the easiest way to avoid the problems > > > > > > > > handing off speech from the dm to the gnome session with orca is to not > > > > > > > > use a dm at all. Options include autologin on the console, or standard > > > > > > > > console login, followed by startx which can reliably start Orca and > > > > > > > > speech-dispatcher. > > > > > > > > > > > > > > > > Linux for blind general discussion writes: > > > > > > > > > because I tried lightdm first and that didn't work either. > > > > > > > > > > > > > > > > > > On Fri, 8 Sep 2017, Linux for blind general discussion wrote: > > > > > > > > > > > > > > > > > > > Date: Fri, 8 Sep 2017 07:44:51 > > > > > > > > > > From: Linux for blind general discussion <blinux-list@xxxxxxxxxx> > > > > > > > > > > To: Linux for blind general discussion <blinux-list@xxxxxxxxxx> > > > > > > > > > > Subject: Re: speechdispatcher-git > > > > > > > > > > > > > > > > > > > > Why do you need gdm? > > > > > > > > > > > > > > > > > > > > Linux for blind general discussion writes: > > > > > > > > > > > It builds but doesn't run. Seems to be missing libdotconf.so.0 and the > > > > > > > > > > > libdotconf library doesn't appear to be in the archlinux repositories. I > > > > > > > > > > > uncommented lines in speechdispatcher-git PKGBUILD file to enable > > > > > > > > > > > speechdispatcher to run as a system-wide process and this may be necessary > > > > > > > > > > > for speech to work in graphical user interface on archlinux but I could be > > > > > > > > > > > wrong about that. If all of this doesn't work, I know what commands to use > > > > > > > > > > > to turn off gdm or lightdm with my archlinux system disk. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > > Blinux-list mailing list > > > > > > > > > > > Blinux-list@xxxxxxxxxx > > > > > > > > > > > https://www.redhat.com/mailman/listinfo/blinux-list > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > Blinux-list mailing list > > > > > > > > > Blinux-list@xxxxxxxxxx > > > > > > > > > https://www.redhat.com/mailman/listinfo/blinux-list > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Blinux-list mailing list > > > > > > > Blinux-list@xxxxxxxxxx > > > > > > > https://www.redhat.com/mailman/listinfo/blinux-list > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > _______________________________________________ > > > > > Blinux-list mailing list > > > > > Blinux-list@xxxxxxxxxx > > > > > https://www.redhat.com/mailman/listinfo/blinux-list > > > > > > > > > > > > > > -- > > > > > > _______________________________________________ > > > Blinux-list mailing list > > > Blinux-list@xxxxxxxxxx > > > https://www.redhat.com/mailman/listinfo/blinux-list > > > > > > -- > > _______________________________________________ > Blinux-list mailing list > Blinux-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/blinux-list -- Janina Sajka, Phone: +1.443.300.2200 sip:janina@xxxxxxxxxxxxxxxxxxxx Email: janina@xxxxxxxxxxx Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Accessible Platform Architectures http://www.w3.org/wai/apa _______________________________________________ Blinux-list mailing list Blinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/blinux-list