Opened 3 months ago

Closed 3 months ago

Last modified 3 months ago

#13628 closed Bug Report - General (Invalid)

mythtv-status script causes issue with scp

Reported by: leafpaulc Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: v31-fixes
Severity: low Keywords:
Cc: Ticket locked: no


Linux The scp command fails sometimes due to a conflict with the mythtv-status script. An ssh session works as expected.

"mythtv" is the pc with mythtv installed, scp is run from another desktop pc both are running linux.

In both cases scp is run on the desktop pc, 1 copying a file from mythtv pc to the desktop pc and 2 copying a file from the desktop pc to the mythtv pc

Case 1 (file copied from mythtv pc to desktop pc):

scp mythtv:filename filename


protocol error: unexpected <newline>

The file (filename) isn't copied from the desktop to the mythtv box.

Case 2 (file copied from desktop pc to mythtv pc):

scp filename mythtv:filename


MythTV status for localhost"

There is a \n (causing a blank line) before the text.

The file (filename) isn't copied in either case 1 or case 2.

Uninstalling the mythtv-status package resolves the issue (ie scp copies the file as expected so this is the workaround) as does removing the .ssh/rc file that causes the mythtv-status to run on remote login (via ssh or scp) to the mythtv pc.

You may want to re-classify this ticket as "Bindings - Perl" as it is a perl script.

Change History (3)

comment:1 Changed 3 months ago by leafpaulc

Forgot to add: "sometimes" is probably erroneous, this has worked in the past but currently doesn't (at least in my case). Originally I was suspecting that it has something to do with there being no recordings scheduled but that doesn't seem to be the case.

comment:2 Changed 3 months ago by Bill Meek

Milestone: needs_triageunknown
Resolution: Invalid
Status: newclosed

You might have better luck on the mailing list. mythtv-status doesn't exist in the MythTV code base. Ref: #8390

I did, however install the package from Ubuntu and see no references to making changes to ~/.ssh. It also doesn't appear in the packaging repo.

comment:3 Changed 3 months ago by David Hampton

IIRC, scp is unhappy with anything that puts data into connection between the two machines. E.G. you would have the same problem if you ran the fortune command on every shell invocation. I think that if you could tweak the .ssh/rc file somehow to distinguish between ssh and scp connections that would solve your problem.

Note: See TracTickets for help on using tickets.