[mythtv-users] SOLVED ongoing commo issues with compiled frontend / backend

[Mepis Rocks]

ifconfig produces the following:

eth0 - inet6 addr: fe80::xxxxxx/64 Scope:Link
lo - inet6 addr: ::1/128 Scope:Host

netstat produces:

tcp        0      0 0.0.0.0:6543            0.0.0.0:*
LISTEN      -

this is after re-enabled ipv6 on eth0 and reinstalled myth

this ticket http://code.mythtv.org/trac/ticket/9820 was actually what got
me thinking that it might be an ipv6/ipv4 issue.

before the latest update from debian multimedia, i had been running my
system with ipv6 disabled and mythtv ran fine.  it was only after applying
this last patch that things got squirrelly. the initial problem presented
as a segfault with the backend.  dmesg produced:

segfault at 50 ip b58b2c6c sp bfa06c40 error 4 in libQtCore.so.4.7.1

and when this was happening , i had eth0 set for ipv4.  i don't know enough
about Qt4 to know if it handles some part of networking, but i now suspect
that the two are related.

thinking there was a Qt issue, i downloaded, compiled, installed and ran
the backend without a problem (once i set both backend ips to 192.xxxx).
frontend would not connect to the 192.xxx backend, appearing to default to
127.0.0.1, and this is where i think it was having issues with eth0 being
ipv4 because when i did a netstat it was showing tcp6 being used on the
myth ports.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.mythtv.org/pipermail/mythtv-users/attachments/20111212/6f2ff72b/attachment.html