Mailing List Archive: atrpms: devel

Problems with Myth Packages from Bleeding Repo

Index | Next | Previous | View Threaded

jrw3319 at gmail

Apr 16, 2007, 6:48 PM

Post #1 of 15 (1155 views)
Permalink

Problems with Myth Packages from Bleeding Repo

For the last couple of months I have been running the mythtv-trunk "0.21-153"
series packages from the bleeding repo. I had tried upgrading to the 154
and 155 series packages but ran into "undefined symbol" problems with both
series. Frankly, at the time I tried these upgrades I didn't really have
time to troubleshoot, and since everything was essentially working fine for
me with the 153 series I didn't pursue anything. I've been following the
lists and it seems like the latest 156 series packages have some pretty
significant improvements, specifically with QAM channel scanning. I tried
upgrading these packages, but unfortunately I'm still getting an "undefined
symbol". The specific message I'm seeing occurs when I try to start the
back-end, and is as follows:
Starting mythbackend: /usr/bin/mythbackend: symbol lookup error:
/usr/bin/mythbackend: undefined symbol: _ZN4UPnp9g_pConfigE

I did a Google search for this error and got a hit on the Myth lists, but
the solutions talk about changing things when compiling from source. Since
I'm installing from packages I'm not sure what to do. I'm trying to rebuild
the packages on my system with the "rpmbuild --rebuild" command. I'm not
sure if this is going to help at all, so while the rebuild is chugging along
I figured I'd post to see if anyone can provide any help.

TIA,
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20070416/854a83af/attachment.html

Axel.Thimm at ATrpms

Apr 17, 2007, 12:25 AM

Post #2 of 15 (1124 views)
Permalink

Problems with Myth Packages from Bleeding Repo [In reply to]

On Mon, Apr 16, 2007 at 09:48:10PM -0400, John Welch wrote:
> For the last couple of months I have been running the mythtv-trunk
> "0.21-153"
> series packages from the bleeding repo. I had tried upgrading to the 154
> and 155 series packages but ran into "undefined symbol" problems with both
> series. Frankly, at the time I tried these upgrades I didn't really have
> time to troubleshoot, and since everything was essentially working fine for
> me with the 153 series I didn't pursue anything. I've been following the
> lists and it seems like the latest 156 series packages have some pretty
> significant improvements, specifically with QAM channel scanning. I tried
> upgrading these packages, but unfortunately I'm still getting an "undefined
> symbol". The specific message I'm seeing occurs when I try to start the
> back-end, and is as follows:
> Starting mythbackend: /usr/bin/mythbackend: symbol lookup error:
> /usr/bin/mythbackend: undefined symbol: _ZN4UPnp9g_pConfigE
>
> I did a Google search for this error and got a hit on the Myth lists, but
> the solutions talk about changing things when compiling from source. Since
> I'm installing from packages I'm not sure what to do. I'm trying to rebuild
> the packages on my system with the "rpmbuild --rebuild" command. I'm not
> sure if this is going to help at all, so while the rebuild is chugging along
> I figured I'd post to see if anyone can provide any help.

you probably are partially/selectively upgrading. Since currently
bleeding effectively only carries mythtv trunk, just try a full
upgrade and see what you were missing before.
--
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20070417/fa8cf29f/attachment.bin

jrw3319 at gmail

Apr 17, 2007, 5:08 AM

Post #3 of 15 (1123 views)
Permalink

Problems with Myth Packages from Bleeding Repo [In reply to]

>
>
> you probably are partially/selectively upgrading. Since currently
> bleeding effectively only carries mythtv trunk, just try a full
> upgrade and see what you were missing before.
> --
> Axel.Thimm at ATrpms.net
>
> Hi Axel,

Thanks for the reply, but what you suggested (partial upgrade) is not the
case. I did a 'yum update' first to get my system right up to date. Then I
enabled the bleeding repo and did another full 'yum update'. I can try
again, but I'm pretty sure I didn't miss anything the first time. I did a
rebuild from the .src package, so I may try that also.

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20070417/479b42e9/attachment.html

jrw3319 at gmail

Apr 17, 2007, 6:58 AM

Post #4 of 15 (1121 views)
Permalink

Problems with Myth Packages from Bleeding Repo [In reply to]

Problem solved... For some reason I didn't have /usr/lib in my
ld.so.conffile. Never caused me any issues with past Myth versions,
but I guess this
is due to some coding changes related to symbols and libraries. At least
got the mythbackend process started; hopefully all else is OK as well.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20070417/faeeb0be/attachment.html

Axel.Thimm at ATrpms

Apr 17, 2007, 11:54 AM

Post #5 of 15 (1120 views)
Permalink

Problems with Myth Packages from Bleeding Repo [In reply to]

On Tue, Apr 17, 2007 at 09:58:55AM -0400, John Welch wrote:
> Problem solved... For some reason I didn't have /usr/lib in my
> ld.so.conffile. Never caused me any issues with past Myth versions,
> but I guess this
> is due to some coding changes related to symbols and libraries. At least
> got the mythbackend process started; hopefully all else is OK as well.

Hm, you don't happen to have mythtv bits under /usr/local, do you? :)
--
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20070417/2b72c1d1/attachment.bin

jrw3319 at gmail

Apr 17, 2007, 12:49 PM

Post #6 of 15 (1120 views)
Permalink

Problems with Myth Packages from Bleeding Repo [In reply to]

>
> Hm, you don't happen to have mythtv bits under /usr/local, do you? :)
> --
> Axel.Thimm at ATrpms.net
>
> Well, I have the following empty directories:
/usr/local/lib/mythtv
/usr/local/include/mythtv
/usr/local/share/mythtv/mythvideo
/usr/local/share/mythtv/mythflix

I don't remember compiling from source, but I must have tried it at some
point. Would any of these empty directories be the cause of the problem?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20070417/3d5440a7/attachment-0001.html

Axel.Thimm at ATrpms

Apr 17, 2007, 1:04 PM

Post #7 of 15 (1124 views)
Permalink

Problems with Myth Packages from Bleeding Repo [In reply to]

On Tue, Apr 17, 2007 at 03:49:37PM -0400, John Welch wrote:
> >
> >Hm, you don't happen to have mythtv bits under /usr/local, do you? :)
> /usr/local/lib/mythtv
> /usr/local/include/mythtv
> /usr/local/share/mythtv/mythvideo
> /usr/local/share/mythtv/mythflix
>
> I don't remember compiling from source, but I must have tried it at some
> point. Would any of these empty directories be the cause of the problem?

empty directories not, but compare the output of ldconfig -p w/ w/o
the /usr/lib addition to ld.so.conf and you'll find the culprit.
--
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20070417/67077fc2/attachment.bin

jrw3319 at gmail

Apr 17, 2007, 1:22 PM

Post #8 of 15 (1124 views)
Permalink

Problems with Myth Packages from Bleeding Repo [In reply to]

>
>
> empty directories not, but compare the output of ldconfig -p w/ w/o
> the /usr/lib addition to ld.so.conf and you'll find the culprit.
> --
> Axel.Thimm at ATrpms.net
>
> I know you probably won't believe this, but the output of the ldconfig -p
command with and without the /usr/lib directory in the ld.so.conf file was
identical.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20070417/6e4d9781/attachment.html

Axel.Thimm at ATrpms

Apr 17, 2007, 1:49 PM

Post #9 of 15 (1123 views)
Permalink

Problems with Myth Packages from Bleeding Repo [In reply to]

On Tue, Apr 17, 2007 at 04:22:48PM -0400, John Welch wrote:
> >
> >
> >empty directories not, but compare the output of ldconfig -p w/ w/o
> >the /usr/lib addition to ld.so.conf and you'll find the culprit.

> I know you probably won't believe this, but the output of the
> ldconfig -p command with and without the /usr/lib directory in the
> ld.so.conf file was identical.

In that case the bug is no gone even w/o having to use /usr/lib in
ld.so.conf, correct?

Did you remember to run ldconfig (w/o -p) after modifying ld.so.conf?

Anyway, the main outcome is that currently your system works.
--
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20070417/4299828b/attachment.bin

jrw3319 at gmail

Apr 17, 2007, 3:04 PM

Post #10 of 15 (1125 views)
Permalink

Problems with Myth Packages from Bleeding Repo [In reply to]

>
> In that case the bug is no gone even w/o having to use /usr/lib in
> ld.so.conf, correct?
>
> Did you remember to run ldconfig (w/o -p) after modifying ld.so.conf?
>
> Anyway, the main outcome is that currently your system works.
> --
> Axel.Thimm at ATrpms.net
>
> OK, this is bizarre, at least to me, a non-programmer. With /usr/lib in
the ld.so.conf file mythbackend starts fine. However, I found that I no
longer have any sound, as ALSA appears to be broken. In this state I ran
the 'ldconfig -p' and saved the output to a file. I then stopped
mythbackend, removed /usr/lib from the ld.so.conf, and ran ldconfig. After
doing that the mythbackend won't start (back to the 'undefined symbol'
error), but ALSA appears to be working. Then I re-ran 'ldconfig -p' and
saved the output to another file. Comparing the files from the two
'ldconfig -p' commands, they are identical. So, to answer your question
"the main outcome is that currently your system works", well no, not really.

I must have something hosed on this system that is just being brought to
light by these latest Mythtv packages. I know this most likely not an issue
related to any ATrpms packages, but any help would be greatly appreciated.

Thanks again,
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20070417/80ccbdaf/attachment.html

Axel.Thimm at ATrpms

Apr 17, 2007, 3:26 PM

Post #11 of 15 (1124 views)
Permalink

Problems with Myth Packages from Bleeding Repo [In reply to]

On Tue, Apr 17, 2007 at 06:04:57PM -0400, John Welch wrote:
> >
> >In that case the bug is no gone even w/o having to use /usr/lib in
> >ld.so.conf, correct?
> >
> >Did you remember to run ldconfig (w/o -p) after modifying ld.so.conf?
> >
> >Anyway, the main outcome is that currently your system works.
> the ld.so.conf file mythbackend starts fine. However, I found that I no
> longer have any sound, as ALSA appears to be broken. In this state I ran
> the 'ldconfig -p' and saved the output to a file. I then stopped
> mythbackend, removed /usr/lib from the ld.so.conf, and ran ldconfig. After
> doing that the mythbackend won't start (back to the 'undefined symbol'
> error), but ALSA appears to be working. Then I re-ran 'ldconfig -p' and
> saved the output to another file. Comparing the files from the two
> 'ldconfig -p' commands, they are identical. So, to answer your question
> "the main outcome is that currently your system works", well no, not really.
>
> I must have something hosed on this system that is just being brought to
> light by these latest Mythtv packages. I know this most likely not an issue
> related to any ATrpms packages, but any help would be greatly appreciated.

AFAIK all that ldconfig's operation can do is given by ldconfig -p. And
if some modification to ldconfig's configuration doesn't change that,
it is very strange that there is any effect at all.

E.g. it is strange that ldconfig itself seems to not notice the
changes, but mythtv and alsa do.
--
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20070418/29135a37/attachment.bin

jrw3319 at gmail

Apr 17, 2007, 6:40 PM

Post #12 of 15 (1121 views)
Permalink

Problems with Myth Packages from Bleeding Repo [In reply to]

>
> AFAIK all that ldconfig's operation can do is given by ldconfig -p. And
> if some modification to ldconfig's configuration doesn't change that,
> it is very strange that there is any effect at all.
>
> E.g. it is strange that ldconfig itself seems to not notice the
> changes, but mythtv and alsa do.
> --
> Axel.Thimm at ATrpms.net
>
> I've been looking at this for a few hours now, trying to troubleshoot the
problem, and I'm back to thinking there may be an issue with the Mythtv
packages rather than my system being hosed in some way. According to the
man page for ldconfig, the command looks at /lib and /usr/lib implicitly, as
well as directories in the ld.so.conf file. To me, this explains why the
ldconfig -p command gives the same output regardless of whether or not my
ld.so.conf file contains /usr/lib or not. If this is the case then why does
the mythbackend process only work if I add /usr/lib to ld.so.conf?
Something doesn't make sense here. I've played around with the
ld.so.conffile and it doesn't seem to matter what I have in there,
other than
mythbackend works when the file contains /usr/lib and doesn't when /usr/lib
is removed. I've tried adding /usr/lib to two other FC6 systems and on both
systems doing this "broke" ALSA, just as it did on my mythbackend machine.
So, I'm starting to think having /usr/lib in the ld.so.conf file is not a
good thing. Who knows what else may be broken by having this in there.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20070417/cdc2659f/attachment.html

jrw3319 at gmail

Apr 17, 2007, 7:13 PM

Post #13 of 15 (1123 views)
Permalink

Problems with Myth Packages from Bleeding Repo [In reply to]

No sooner did I send my last message than I believe I found a solution. I
found that the files from the libmyth package existed in both /lib and
/usr/lib, with the /lib files being older. Apparently, unless specified in
the ld.so.conf directory, the ldconfig command looks in /lib first before
/usr/lib. So, did the location of the lib files change with the newer
versions of Myth, and if so, shouldn't the upgrade have removed the files in
the /lib directory?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20070417/29ad4f3b/attachment-0001.html

Axel.Thimm at ATrpms

Apr 18, 2007, 2:33 AM

Post #14 of 15 (1121 views)
Permalink

Problems with Myth Packages from Bleeding Repo [In reply to]

On Tue, Apr 17, 2007 at 10:13:28PM -0400, John Welch wrote:
> No sooner did I send my last message than I believe I found a solution. I
> found that the files from the libmyth package existed in both /lib and
> /usr/lib, with the /lib files being older. Apparently, unless specified in
> the ld.so.conf directory, the ldconfig command looks in /lib first before
> /usr/lib. So, did the location of the lib files change with the newer
> versions of Myth, and if so, shouldn't the upgrade have removed the files in
> the /lib directory?

No, because the packages never ever placed anything under /lib. You
must have copied the libs there yourself (when for example building
mythtv yourself).

FWIW even if the packages would move their libs around the old libs
would automatically be removed upon upgrade, but as said this was
never the case with /lib.
--
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20070418/01432408/attachment.bin

jrw3319 at gmail

Apr 18, 2007, 5:42 AM

Post #15 of 15 (1123 views)
Permalink

Problems with Myth Packages from Bleeding Repo [In reply to]

>
> No, because the packages never ever placed anything under /lib. You
> must have copied the libs there yourself (when for example building
> mythtv yourself).
>
> FWIW even if the packages would move their libs around the old libs
> would automatically be removed upon upgrade, but as said this was
> never the case with /lib.
> --
> Axel.Thimm at ATrpms.net

Hi Axel,

I figured out what happened. I had been running the Myth stable packages
from ATrpms for quite some time. However, in early February I was forced to
look at the SVN trunk version in order to get some fixes for the HDHomeRun
tuner and QAM channel tuning. At the time the bleeding packages did not
contain the fixes I needed. Having been working on this issue for close to
a month, and getting a bit impatient I decided to try to compile from
source. I got pretty far along, but when I was still having problems, IIRC
I contacted you via the list to see about a new trunk build, and you kindly
obliged. I've been running that version (0.21-153 series) since then. I
guess I was lucky that the lib files installed from source to the /lib
directory matched up with the ones from the libmyth package that were
installed to /usr/lib.

Totally my fault; nothing wrong with the packages, as usual. Sorry for the
bother, and thanks for the help. And as always thanks for the great repos.

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20070418/3052ef21/attachment.html

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads