Re: myth 0.25.2-dmo1 frontend won't start [solved]

Top Page

Reply to this message
Author: Ross Boylan
To: multimedia
CC: ross
Old-Topics: myth 0.25.2-dmo1 frontend won't start (help request)
Subject: Re: myth 0.25.2-dmo1 frontend won't start [solved]
On Mon, 2012-08-13 at 14:43 -0700, Ross Boylan wrote:
> mythfrontend[17029]: segfault at 6500dd ip b3b67d78 sp bfe49e84 error 4 in[b3b61000+15000]
> when I try to start it. mythbackend is running with no obvious errors,
> and no output coincident with the attempted mythfrontend start.
> This is in a chroot running testing, but I have not updated it in
> several months because of trouble with the mythupgrade. So maybe a
> library mismatch issue (e.g., Qt compiled and run time differ in the
> log)?
> I recall reading some reports that mysql 5.5 and myth didn't make a good
> combination on Debian. I've been unable to find the exact messages.
> aptitude says it wants to remove myth and mysql 5.1 if I attempt to
> upgrade qt to 4.8.2
> Any ideas?

After doing an upgrade of all the packages on the system, including the
mysql 5.1 -> 5.5 transition, the frontend now starts without trouble and
everything seems to work.

> P.S. I thought my original attempt to install 0.25.2 got dmo2.

That may have been the result of using locally built packages from sid
source, while I was debuging the problem.

Last line below, from earlier when it was crashing, indicates one of the
possible library mismatches.

> Running as user mythtv:
> $ mythfrontend
> Qt: Session management error: Could not open network socket
> 2012-08-13 13:59:42.409275 C mythfrontend version: [v0.25.2]
> 2012-08-13 13:59:42.409330 C Qt version: compile: 4.8.2, runtime: 4.8.1