Main pipe closed errors

Post a reply


In an effort to prevent automatic submissions, we require that you complete the following challenge.
Smilies
:D :) :( :o :shock: :? 8) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :!: :?: :idea: :arrow: :| :mrgreen:

BBCode is OFF
Smilies are ON

Topic review
   

Expand view Topic review: Main pipe closed errors

Re: Main pipe closed errors

by akatik » Sat Sep 14, 2019 11:32 am

On Raspberry, "sound=on" is for onboard sound via HDMI.
For USB headset, "sound=on, hw:1:0". But you should connect USB headset. With ""sound=on, hw:1:0"" and without USB headset wtware will crush trying to play sound on nonexisting device.

Re: Main pipe closed errors

by Webjom » Wed Sep 11, 2019 9:05 pm

yes it goes but you have to enter the jack 3.5 parameter and plug it into them " sound=on, amixet:cset numid=3 1

Re: Main pipe closed errors

by onatam » Tue Sep 10, 2019 5:19 pm

Can we keep simply sound=on so that it could potentially play through a usb headset?

Re: Main pipe closed errors

by akatik » Tue Sep 10, 2019 8:47 am

Remove "sound=on, hw:1:0" line. There is no hw:1 device.

Main pipe closed errors

by onatam » Tue Sep 10, 2019 12:43 am

We have been seeing a large influx of "Main Pipe Closed" errors in our WTWare environment in one of our sites.

Our environment is two locations which connect to a gateway and the terminal servers are spread across the two sites. We have seen the issue come up in a rare occurrence but now it is happening often throughout the day. Please advise.

See attached for logs.
terminallog.txt
(52.7 KiB) Downloaded 90 times

Top