I had the same experience. It seems like the mythtv or mythtv-common
package should contain the libmyth-0.20 package, too. My failure was
searching Synaptic for "mythtv" instead of "myth"! Is non-association
of these packages a bug or just user error?
--
MythTV install (upgrade) failed exit st
>From what I can see, I think my problem was having the "backports"
packages in my sources.list. I still haven't successfully upgraded
(trying to get schedules direct support), but after commenting out that
line I didn't get this error message upon upgrade.
--
MythTV install (upgrade) failed exi
I got this problem too after trying to upgrade mythtv package on edgy in
the proposed repository. My version before upgrade was
0.20-svn20070122-0.0ubuntu6~edgy1 as well. I have libmyth-0.20 on my
system, but I don't know how to get mythtv to recognize it, so I
reverted to a backup I did just bef
Okay as long as this worked after you had the new libraries installed,
i'm gonna close up the bug. Feel free to re-open should anyone else
encounter something similar :)
** Changed in: mythtv (Ubuntu)
Status: New => Invalid
--
MythTV install (upgrade) failed exit status 127
https://bugs.
Went back and found libmyth-0.20, installed it, Not sure why it didn't
install with the upgrade. Anyway... appears to be working now...
--
MythTV install (upgrade) failed exit status 127
https://bugs.launchpad.net/bugs/135433
You received this bug notification because you are a member of Ubuntu
B
[EMAIL PROTECTED]:~$ mythtv-setup
mythtv-setup: error while loading shared libraries: libmythtv-0.20.2.so.0:
cannot open shared object file: No such file or directory
[EMAIL PROTECTED]:~$ mythbackend
mythbackend: error while loading shared libraries: libmythtv-0.20.2.so.0:
cannot open shared obj
