[ATrpms-users] Re: X86_64 FC4 Segmentation Fault -- update??
On Wed, Oct 26, 2005 at 11:03:12AM -0700, RKVJ wrote: Hi, I'm trying to install mythtv on Fedora 4/AMD 64 machine, using the how-to by Jarod wilson. I get segmentation fault when I tried to run mythfrontend and the messages are similar to the ones mentioned in an earlier email thread(posted about a month ago)attached below. Any suggestions/pointers to ways for getting around the problem? Yes, Alexandre Parenteau had some success with building from svn, check the archives for more details. You could also suggest on the mythtv list to put those fixes in the stable 0.18 branch, and I would repackage it. I suspect thos fixes living only in latest mythtv developer code. Thanks I, too, am having this problem. AMD64 on FC4 with the same discrepencies in rpm versions (114 and 113) It happens when starting mythfrontend. Also, prior to the first time attempting to run mythfrontend, the mythtv-setup ran fine, nice blue clean background. After this frontend error, the setup background is all twisty and nasty. Here are the messages: mythtv at titan ~]$ mythfrontend 2005-09-24 23:09:16.819 New DB connection, total: 1 Total desktop width=1280, height=1024, numscreens=1 2005-09-24 23:09:16.832 Using screen 0, 1280x1024 at 0,0 2005-09-24 23:09:16.836 mythfrontend version: 0.18.1.20050523-1 www.mythtv.org http://www.mythtv.org 2005-09-24 23:09:16.837 Enabled verbose msgs : important general Conflict in /usr/lib/qt-3.3/plugins/styles/bluecurve.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. Conflict in /usr/lib/kde3/plugins/styles/highcolor.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. Conflict in /usr/lib/kde3/plugins/styles/highcontrast.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. Conflict in /usr/lib/kde3/plugins/styles/keramik.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. Conflict in /usr/lib/kde3/plugins/styles/kthemestyle.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. Conflict in /usr/lib/kde3/plugins/styles/light.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. Conflict in /usr/lib/kde3/plugins/styles/plastik.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. 2005-09-24 23:09:17.802 Switching to square mode (G.A.N.T.) Corrupt JPEG data: bad Huffman code 2005-09-24 23:09:18.743 Registering Internal as a media playback plugin. 2005-09-24 23:09:18.778 Joystick disabled. 2005-09-24 23:09:18.756 Inserting MythDVD initial database information. Segmentation fault [mythtv at titan ~]$ The .la's (plastik.la http://plastik.la, etc) all point to /usr/lib instead of /usr/lib64, don't know if this is an issue or not.. Please let me know if there are any other logs you'd like to see. Graham On Thu, Sep 22, 2005 at 09:42:32AM -0500, Benjamin Bakken wrote: Greetings-- I recently noticed that there are new RPMs for fc4/x86_64 for the plugins which is great news. I've been eager to try them. So, I did. Unfortunately I am getting a segmentation fault now when I try run MythTV which persists until I remove most of the plugins I have installed. I've noticed quite a number of posts on what seemed to be an issue for FC4/X86_64 but I didn't follow it all. I assumed that the presence of the RPMs meant that it was resolved. I do notice that the RPM versions of my mythtv-backend, frontend and setup (0.18.1-114.rhfc4.athttp://0.18.1-114.rhfc4.at) are one up from the plugins it installed (0.18.1-113.rhfc4.athttp://0.18.1-113.rhfc4.at ). That's just coincidence. I'm really sorry if this is a problem on my end, but I can't seem to figure out what's going on. Please offer some more detail, which plugins cause the segfault, what where you doing at that time etc. Also consider notifying the mythtv lists. -- Axel.Thimm at ATrpms.net pgpHLJyzAVXiH.pgp Description: PGP signature ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users
[ATrpms-users] Re: X86_64 FC4 Segmentation Fault
On Tue, Sep 27, 2005 at 04:57:48PM -0400, Graham Bowman wrote: Mr Thimm, Would you be able to point me to directions where I can learn about how to install the x86_64 rpms while using the i386 plugins? I don't think that's possible. It is either using i386 myth or x86_64 myth. You can't mix i386 plugins with x86_64 mythtv. On 9/26/05, Axel Thimm [EMAIL PROTECTED] wrote: On Sun, Sep 25, 2005 at 10:09:49AM -0400, Graham Bowman wrote: All the individual themes are noarch, while the mythtv-themes package is x86_64. That's OK. This is the second time I've slicked and reinstalled everything from scratch using Mr. Wilson's FC4 guide, after having stupidly just slicked a (somewhat) perfectly running .17 box. But mythtv 0.17 was not on 64 bits, or was it? At least under FC4 the builds would fail until recently. The issue is that for some reason some mythtv bits want to use /usr/lib/qt-3.3 instead of /usr/lib64/qt-3.3/. On 9/25/05, Axel Thimm [EMAIL PROTECTED] wrote: On Sun, Sep 25, 2005 at 12:37:21AM -0400, Graham Bowman wrote: [EMAIL PROTECTED] ~]$ mythfrontend 2005-09-24 23:09:16.819 New DB connection, total: 1 Total desktop width=1280, height=1024, numscreens=1 2005-09-24 23:09:16.832 Using screen 0, 1280x1024 at 0,0 2005-09-24 23:09:16.836 mythfrontend version: 0.18.1.20050523-1 www.mythtv.org http://www.mythtv.org http://www.mythtv.org http://www.mythtv.org 2005-09-24 23:09:16.837 Enabled verbose msgs : important general Conflict in /usr/lib/qt-3.3/plugins/styles/bluecurve.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. This looks like you are using some i686 plugins on x86_64. You can't mix those, you can choose to use only i386 or only x86_64 myth bits. Try something like rpm -qa --qf '[EMAIL PROTECTED]' myth\* to check what archs the packages have. -- Axel.Thimm at ATrpms.net pgpbzEAAn5bsz.pgp Description: PGP signature ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users
[ATrpms-users] Re: X86_64 FC4 Segmentation Fault
On Tue, Sep 27, 2005 at 02:20:34PM -0700, Alexandre Parenteau wrote: Axel, Thanks for your response. Yesterday the problem was fixed after I did a svn up. I could use successfully mythtv on my AMD64/Hauppauge350, yeah! That's nice! Was it in HEAD or in fixes? If the latter I would respin packages. alex. Axel Thimm wrote: On Sun, Sep 25, 2005 at 09:07:31PM -0700, Alexandre Parenteau wrote: Hi, I am a new user, and I had the same problem (I used the RPM ar first). I went as far as compiling mythtv directly from svn, and I get the same problem at start-up, something with threads being spawned (?): Yes, that looks like a thread problem, but probably not related to the other reported problems. Since even svn shows this, I would report it to the mythtv lists. Unfortunatley most developers don't use mythtv on 64 bits, so some issues slip in. BTW you can use the 32 bit variant of mythtv until this is fixed. /usr/local/bin/mythfrontend 2005-09-25 20:56:20.149 Using runtime prefix = /usr/local Detaching after fork from child process 7377. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 2005-09-25 20:56:21.617 New DB connection, total: 1 2005-09-25 20:56:21.622 Total desktop dim: 1280x1024, with 1 screen[s]. 2005-09-25 20:56:21.624 Using screen 0, 1280x1024 at 0,0 [New Thread 1084229984 (LWP 7380)] Program received signal SIG33, Real-time event 33. [Switching to Thread 1084229984 (LWP 7380)] 0x2e05e8f2 in clone () from /lib64/libc.so.6 (gdb) thread [Current thread is 2 (Thread 1084229984 (LWP 7380))] (gdb) thread 1 [Switching to thread 1 (Thread 46912561695648 (LWP 7374))]#0 0x2d9f182a in __nptl_setxid () from /lib64/libpthread.so.0 (gdb) bt #0 0x2d9f182a in __nptl_setxid () from /lib64/libpthread.so.0 #1 0x2e028107 in setuid () from /lib64/libc.so.6 #2 0x0042638a in ?? () #3 0x2dfb13cf in __libc_start_main () from /lib64/libc.so.6 #4 0x0041f8b9 in ?? () #5 0x7f804e98 in ?? () #6 0x in ?? () (gdb) thread 2 [Switching to thread 2 (Thread 1084229984 (LWP 7380))]#0 0x2e05e8f2 in clone () from /lib64/libc.so.6 (gdb) bt #0 0x2e05e8f2 in clone () from /lib64/libc.so.6 #1 0x2d9f28f0 in __make_stacks_executable () from /lib64/libpthread.so.0 #2 0x40a00960 in ?? () #3 0x in ?? () Thanks, alex. ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users -- Axel.Thimm at ATrpms.net pgp6eXdjJ1zTY.pgp Description: PGP signature ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users
[ATrpms-users] Re: X86_64 FC4 Segmentation Fault
Mr Thimm, Would you be able to point me to directions where I can learn about how to install the x86_64 rpms while using the i386 plugins? On 9/26/05, Axel Thimm [EMAIL PROTECTED] wrote: On Sun, Sep 25, 2005 at 10:09:49AM -0400, Graham Bowman wrote: All the individual themes are noarch, while the mythtv-themes package is x86_64.That's OK. This is the second time I've slicked and reinstalled everything from scratch using Mr. Wilson's FC4 guide, after having stupidly just slicked a (somewhat) perfectly running .17 box.But mythtv 0.17 was not on 64 bits, or was it? At least under FC4 thebuilds would fail until recently. The issue is that for some reason some mythtv bits want to use/usr/lib/qt-3.3 instead of /usr/lib64/qt-3.3/. On 9/25/05, Axel Thimm [EMAIL PROTECTED] wrote: On Sun, Sep 25, 2005 at 12:37:21AM -0400, Graham Bowman wrote: [EMAIL PROTECTED] ~]$ mythfrontend 2005-09-24 23:09:16.819 New DB connection, total: 1 Total desktop width=1280, height=1024, numscreens=1 2005-09-24 23:09:16.832 Using screen 0, 1280x1024 at 0,0 2005-09-24 23:09:16.836 mythfrontend version: 0.18.1.20050523-1 www.mythtv.org http://www.mythtv.org http://www.mythtv.org 2005-09-24 23:09: 16.837 Enabled verbose msgs : important general Conflict in /usr/lib/qt-3.3/plugins/styles/bluecurve.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. This looks like you are using some i686 plugins on x86_64. You can't mix those, you can choose to use only i386 or only x86_64 myth bits. Try something like rpm -qa --qf '[EMAIL PROTECTED]' myth\* to check what archs the packages have.--Axel.Thimm at ATrpms.net ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users
[ATrpms-users] Re: X86_64 FC4 Segmentation Fault
Axel, Thanks for your response. Yesterday the problem was fixed after I did a svn up. I could use successfully mythtv on my AMD64/Hauppauge350, yeah! alex. Axel Thimm wrote: On Sun, Sep 25, 2005 at 09:07:31PM -0700, Alexandre Parenteau wrote: Hi, I am a new user, and I had the same problem (I used the RPM ar first). I went as far as compiling mythtv directly from svn, and I get the same problem at start-up, something with threads being spawned (?): Yes, that looks like a thread problem, but probably not related to the other reported problems. Since even svn shows this, I would report it to the mythtv lists. Unfortunatley most developers don't use mythtv on 64 bits, so some issues slip in. BTW you can use the 32 bit variant of mythtv until this is fixed. /usr/local/bin/mythfrontend 2005-09-25 20:56:20.149 Using runtime prefix = /usr/local Detaching after fork from child process 7377. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 2005-09-25 20:56:21.617 New DB connection, total: 1 2005-09-25 20:56:21.622 Total desktop dim: 1280x1024, with 1 screen[s]. 2005-09-25 20:56:21.624 Using screen 0, 1280x1024 at 0,0 [New Thread 1084229984 (LWP 7380)] Program received signal SIG33, Real-time event 33. [Switching to Thread 1084229984 (LWP 7380)] 0x2e05e8f2 in clone () from /lib64/libc.so.6 (gdb) thread [Current thread is 2 (Thread 1084229984 (LWP 7380))] (gdb) thread 1 [Switching to thread 1 (Thread 46912561695648 (LWP 7374))]#0 0x2d9f182a in __nptl_setxid () from /lib64/libpthread.so.0 (gdb) bt #0 0x2d9f182a in __nptl_setxid () from /lib64/libpthread.so.0 #1 0x2e028107 in setuid () from /lib64/libc.so.6 #2 0x0042638a in ?? () #3 0x2dfb13cf in __libc_start_main () from /lib64/libc.so.6 #4 0x0041f8b9 in ?? () #5 0x7f804e98 in ?? () #6 0x in ?? () (gdb) thread 2 [Switching to thread 2 (Thread 1084229984 (LWP 7380))]#0 0x2e05e8f2 in clone () from /lib64/libc.so.6 (gdb) bt #0 0x2e05e8f2 in clone () from /lib64/libc.so.6 #1 0x2d9f28f0 in __make_stacks_executable () from /lib64/libpthread.so.0 #2 0x40a00960 in ?? () #3 0x in ?? () Thanks, alex. ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users
[ATrpms-users] Re: X86_64 FC4 Segmentation Fault
On Sun, Sep 25, 2005 at 10:09:49AM -0400, Graham Bowman wrote: All the individual themes are noarch, while the mythtv-themes package is x86_64. That's OK. This is the second time I've slicked and reinstalled everything from scratch using Mr. Wilson's FC4 guide, after having stupidly just slicked a (somewhat) perfectly running .17 box. But mythtv 0.17 was not on 64 bits, or was it? At least under FC4 the builds would fail until recently. The issue is that for some reason some mythtv bits want to use /usr/lib/qt-3.3 instead of /usr/lib64/qt-3.3/. On 9/25/05, Axel Thimm [EMAIL PROTECTED] wrote: On Sun, Sep 25, 2005 at 12:37:21AM -0400, Graham Bowman wrote: [EMAIL PROTECTED] ~]$ mythfrontend 2005-09-24 23:09:16.819 New DB connection, total: 1 Total desktop width=1280, height=1024, numscreens=1 2005-09-24 23:09:16.832 Using screen 0, 1280x1024 at 0,0 2005-09-24 23:09:16.836 mythfrontend version: 0.18.1.20050523-1 www.mythtv.org http://www.mythtv.org http://www.mythtv.org 2005-09-24 23:09:16.837 Enabled verbose msgs : important general Conflict in /usr/lib/qt-3.3/plugins/styles/bluecurve.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. This looks like you are using some i686 plugins on x86_64. You can't mix those, you can choose to use only i386 or only x86_64 myth bits. Try something like rpm -qa --qf '[EMAIL PROTECTED]' myth\* to check what archs the packages have. -- Axel.Thimm at ATrpms.net pgpeKKKg6BT9s.pgp Description: PGP signature ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users
[ATrpms-users] Re: X86_64 FC4 Segmentation Fault
On Sun, Sep 25, 2005 at 09:07:31PM -0700, Alexandre Parenteau wrote: Hi, I am a new user, and I had the same problem (I used the RPM ar first). I went as far as compiling mythtv directly from svn, and I get the same problem at start-up, something with threads being spawned (?): Yes, that looks like a thread problem, but probably not related to the other reported problems. Since even svn shows this, I would report it to the mythtv lists. Unfortunatley most developers don't use mythtv on 64 bits, so some issues slip in. BTW you can use the 32 bit variant of mythtv until this is fixed. /usr/local/bin/mythfrontend 2005-09-25 20:56:20.149 Using runtime prefix = /usr/local Detaching after fork from child process 7377. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 2005-09-25 20:56:21.617 New DB connection, total: 1 2005-09-25 20:56:21.622 Total desktop dim: 1280x1024, with 1 screen[s]. 2005-09-25 20:56:21.624 Using screen 0, 1280x1024 at 0,0 [New Thread 1084229984 (LWP 7380)] Program received signal SIG33, Real-time event 33. [Switching to Thread 1084229984 (LWP 7380)] 0x2e05e8f2 in clone () from /lib64/libc.so.6 (gdb) thread [Current thread is 2 (Thread 1084229984 (LWP 7380))] (gdb) thread 1 [Switching to thread 1 (Thread 46912561695648 (LWP 7374))]#0 0x2d9f182a in __nptl_setxid () from /lib64/libpthread.so.0 (gdb) bt #0 0x2d9f182a in __nptl_setxid () from /lib64/libpthread.so.0 #1 0x2e028107 in setuid () from /lib64/libc.so.6 #2 0x0042638a in ?? () #3 0x2dfb13cf in __libc_start_main () from /lib64/libc.so.6 #4 0x0041f8b9 in ?? () #5 0x7f804e98 in ?? () #6 0x in ?? () (gdb) thread 2 [Switching to thread 2 (Thread 1084229984 (LWP 7380))]#0 0x2e05e8f2 in clone () from /lib64/libc.so.6 (gdb) bt #0 0x2e05e8f2 in clone () from /lib64/libc.so.6 #1 0x2d9f28f0 in __make_stacks_executable () from /lib64/libpthread.so.0 #2 0x40a00960 in ?? () #3 0x in ?? () Thanks, alex. ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users -- Axel.Thimm at ATrpms.net pgpa7A0RbSGrY.pgp Description: PGP signature ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users
[ATrpms-users] Re: X86_64 FC4 Segmentation Fault
On Sun, Sep 25, 2005 at 12:37:21AM -0400, Graham Bowman wrote: [EMAIL PROTECTED] ~]$ mythfrontend 2005-09-24 23:09:16.819 New DB connection, total: 1 Total desktop width=1280, height=1024, numscreens=1 2005-09-24 23:09:16.832 Using screen 0, 1280x1024 at 0,0 2005-09-24 23:09:16.836 mythfrontend version: 0.18.1.20050523-1 www.mythtv.org http://www.mythtv.org 2005-09-24 23:09:16.837 Enabled verbose msgs : important general Conflict in /usr/lib/qt-3.3/plugins/styles/bluecurve.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. This looks like you are using some i686 plugins on x86_64. You can't mix those, you can choose to use only i386 or only x86_64 myth bits. Try something like rpm -qa --qf '[EMAIL PROTECTED]' myth\* to check what archs the packages have. -- Axel.Thimm at ATrpms.net pgp4f36vbtKpk.pgp Description: PGP signature ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users
[ATrpms-users] Re: X86_64 FC4 Segmentation Fault
Hi, I am a new user, and I had the same problem (I used the RPM ar first). I went as far as compiling mythtv directly from svn, and I get the same problem at start-up, something with threads being spawned (?): /usr/local/bin/mythfrontend 2005-09-25 20:56:20.149 Using runtime prefix = /usr/local Detaching after fork from child process 7377. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type return to continue, or q return to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 2005-09-25 20:56:21.617 New DB connection, total: 1 2005-09-25 20:56:21.622 Total desktop dim: 1280x1024, with 1 screen[s]. 2005-09-25 20:56:21.624 Using screen 0, 1280x1024 at 0,0 [New Thread 1084229984 (LWP 7380)] Program received signal SIG33, Real-time event 33. [Switching to Thread 1084229984 (LWP 7380)] 0x2e05e8f2 in clone () from /lib64/libc.so.6 (gdb) thread [Current thread is 2 (Thread 1084229984 (LWP 7380))] (gdb) thread 1 [Switching to thread 1 (Thread 46912561695648 (LWP 7374))]#0 0x2d9f182a in __nptl_setxid () from /lib64/libpthread.so.0 (gdb) bt #0 0x2d9f182a in __nptl_setxid () from /lib64/libpthread.so.0 #1 0x2e028107 in setuid () from /lib64/libc.so.6 #2 0x0042638a in ?? () #3 0x2dfb13cf in __libc_start_main () from /lib64/libc.so.6 #4 0x0041f8b9 in ?? () #5 0x7f804e98 in ?? () #6 0x in ?? () (gdb) thread 2 [Switching to thread 2 (Thread 1084229984 (LWP 7380))]#0 0x2e05e8f2 in clone () from /lib64/libc.so.6 (gdb) bt #0 0x2e05e8f2 in clone () from /lib64/libc.so.6 #1 0x2d9f28f0 in __make_stacks_executable () from /lib64/libpthread.so.0 #2 0x40a00960 in ?? () #3 0x in ?? () Thanks, alex. ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users
[ATrpms-users] Re: X86_64 FC4 Segmentation Fault
I, too, am having this problem. AMD64 on FC4 with the same discrepencies in rpm versions (114 and 113) It happens when starting mythfrontend. Also, prior to the first time attempting to run mythfrontend, the mythtv-setup ran fine, nice blue clean background. After this frontend error, the setup background is all twisty and nasty. Here are the messages: [EMAIL PROTECTED] ~]$ mythfrontend 2005-09-24 23:09:16.819 New DB connection, total: 1 Total desktop width=1280, height=1024, numscreens=1 2005-09-24 23:09:16.832 Using screen 0, 1280x1024 at 0,0 2005-09-24 23:09:16.836 mythfrontend version: 0.18.1.20050523-1 www.mythtv.org 2005-09-24 23:09:16.837 Enabled verbose msgs : important general Conflict in /usr/lib/qt-3.3/plugins/styles/bluecurve.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. Conflict in /usr/lib/kde3/plugins/styles/highcolor.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. Conflict in /usr/lib/kde3/plugins/styles/highcontrast.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. Conflict in /usr/lib/kde3/plugins/styles/keramik.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. Conflict in /usr/lib/kde3/plugins/styles/kthemestyle.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. Conflict in /usr/lib/kde3/plugins/styles/light.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. Conflict in /usr/lib/kde3/plugins/styles/plastik.so: Plugin uses incompatible Qt library! expected build key x86_64 Linux g++-4.* full-config, got i686 Linux g++-4.* full-config. 2005-09-24 23:09:17.802 Switching to square mode (G.A.N.T.) Corrupt JPEG data: bad Huffman code 2005-09-24 23:09:18.743 Registering Internal as a media playback plugin. 2005-09-24 23:09:18.778 Joystick disabled. 2005-09-24 23:09:18.756 Inserting MythDVD initial database information. Segmentation fault [EMAIL PROTECTED] ~]$ The .la's (plastik.la, etc) all point to /usr/lib instead of /usr/lib64, don't know if this is an issue or not.. Please let me know if there are any other logs you'd like to see. Graham On Thu, Sep 22, 2005 at 09:42:32AM -0500, Benjamin Bakken wrote: Greetings-- I recently noticed that there are new RPMs for fc4/x86_64 for the plugins which is great news. I've been eager to try them. So, I did. Unfortunately I am getting a segmentation fault now when I try run MythTV which persists until I remove most of the plugins I have installed. I've noticed quite a number of posts on what seemed to be an issue for FC4/X86_64 but I didn't follow it all. I assumed that the presence of the RPMs meant that it was resolved. I do notice that the RPM versions of my mythtv-backend, frontend and setup (0.18.1-114.rhfc4.at) are one up from the plugins it installed (0.18.1-113.rhfc4.at). That's just coincidence. I'm really sorry if this is a problem on my end, but I can't seem to figure out what's going on. Please offer some more detail, which plugins cause the segfault, what where you doing at that time etc. Also consider notifying the mythtv lists. -- Axel.Thimm at ATrpms.net ___ atrpms-users mailing list atrpms-users@atrpms.net http://lists.atrpms.net/mailman/listinfo/atrpms-users
