[arch-general] kwrite: error while loading shared libraries: libqt-mt.so.3: wrong ELF class: ELFCLASS64 ??
Guys, New strange error while I troubleshoot the dead X intel card issue. As mentioned, I have managed to get twm and openbox running in vncserver on the box with the intel card. kde4 apps will run, but look terrible due to the difference in color-depth, etc., so I was trying to get kde3/kate or kwrite running. I have always been able to run the kde3 apps from both twm and openbox before, but now I get the following error: /opt/kde/bin/kwrite: error while loading shared libraries: libqt-mt.so.3: wrong ELF class: ELFCLASS64 same error with kate, and just about any other kde3 app. Any way to fix this? I like vim, but I admit, I am a bit quicker with multiple kate/kwrite windows at my disposal. I don't think this would be related to the X problem, but... could it be? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Sun, Oct 18, 2009 at 12:08 AM, David C. Rankin
Guys,
New strange error while I troubleshoot the dead X intel card issue. As mentioned, I have managed to get twm and openbox running in vncserver on the box with the intel card. kde4 apps will run, but look terrible due to the difference in color-depth, etc., so I was trying to get kde3/kate or kwrite running. I have always been able to run the kde3 apps from both twm and openbox before, but now I get the following error:
/opt/kde/bin/kwrite: error while loading shared libraries: libqt-mt.so.3: wrong ELF class: ELFCLASS64
same error with kate, and just about any other kde3 app. Any way to fix this?
It looks like you have installed a x86_64 packages on a i686 system. Reinstall qt3 and make sure it's a package for i686 (I assume here that your system is i686).
I like vim, but I admit, I am a bit quicker with multiple kate/kwrite windows at my disposal.
I don't think this would be related to the X problem, but... could it be?
-- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Sunday 18 October 2009 12:36:07 am Eric Bélanger wrote:
It looks like you have installed a x86_64 packages on a i686 system. Reinstall qt3 and make sure it's a package for i686 (I assume here that your system is i686).
Stranger things have happened... I check on my laptop that it still happily runs kde3 apps, and it does without any problems. So I'll check the other box and reinstall qt3 and report back. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Sunday 18 October 2009 12:36:07 am Eric Bélanger wrote: Oh,... you are good :) [03:51 supersff:/home/david] # l /var/cache/pacman/pkg/qt* -rw-r--r-- 1 root root 28017189 2009-10-07 23:49 /var/cache/pacman/pkg/qt-4.5.3-3-i686.pkg.tar.gz -rw-r--r-- 1 root root 10646153 2009-06-17 19:26 /var/cache/pacman/pkg/qt3-3.3.8-11-i686.pkg.tar.gz -rw-r--r-- 1 root root 10619044 2009-10-13 11:58 /var/cache/pacman/pkg/qt3-3.3.8-13-i686.pkg.tar.gz -rw-r--r-- 1 root root 10599475 2009-04-28 21:14 /var/cache/pacman/pkg/qt3- enhanced-3.3.8-1-i686.pkg.tar.gz -rw-r--r-- 1 root root 11185765 2009-10-07 23:37 /var/cache/pacman/pkg/qt3- enhanced-3.3.8-26-x86_64.pkg.tar.gz Somehow, how I don't know, but somehow I did get an x86_64 package installed on this box. Go figure ;-) (too much Scotch ):p -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Sunday 18 October 2009 03:54:54 am David C. Rankin wrote:
On Sunday 18 October 2009 12:36:07 am Eric Bélanger wrote:
Oh,... you are good :)
[03:51 supersff:/home/david] # l /var/cache/pacman/pkg/qt* -rw-r--r-- 1 root root 28017189 2009-10-07 23:49 /var/cache/pacman/pkg/qt-4.5.3-3-i686.pkg.tar.gz -rw-r--r-- 1 root root 10646153 2009-06-17 19:26 /var/cache/pacman/pkg/qt3-3.3.8-11-i686.pkg.tar.gz -rw-r--r-- 1 root root 10619044 2009-10-13 11:58 /var/cache/pacman/pkg/qt3-3.3.8-13-i686.pkg.tar.gz -rw-r--r-- 1 root root 10599475 2009-04-28 21:14 /var/cache/pacman/pkg/qt3- enhanced-3.3.8-1-i686.pkg.tar.gz -rw-r--r-- 1 root root 11185765 2009-10-07 23:37 /var/cache/pacman/pkg/qt3- enhanced-3.3.8-26-x86_64.pkg.tar.gz
Somehow, how I don't know, but somehow I did get an x86_64 package installed on this box. Go figure ;-) (too much Scotch ):p
Solved - The Arch Repository is Messed up. I just removed qt3-
enhanced-3.3.8-26-x86_64.pkg.tar.gz with 'pacman -R -d qt3-enhanced', then
deleted the file from my machine with:
rm /var/cache/pacman/pkg/qt3-enhanced-3.3.8-26-x86_64.pkg.tar.gz
then I reinstalled the package with 'pacman -Sy qt3-enhanced'
and I'll be damned if it didn't install /var/cache/pacman/pkg/qt3-
enhanced-3.3.8-26-x86_64.pkg.tar.gz again!
......That's when the lightbulb winked on and when the feeling of SHAME begin
to settle in on my consciousness. Further investigation revealed that on 10/8
when I had updated my box and the new pacman package was installed, I used the
pacman.conf from an earlier update of my x86_64 Arch server as a "go-by". It
would seem that there was one occasion with the community repository that an
'x86_64' did not get replaced by and 'i686', thus 'the loose nut behind the
keyboard' had installed some:
04:32 supersff:~> l /var/cache/pacman/pkg/*x86_64* | wc -l
52
Yes FIFTY-TWO x86_64 packages on my fine little i686 box. (SMACK to make sure
I have learned the lesson and SMACK, just for good measure)
Now it seems I need to stroll on over to the bug I opened against the intel
graphics dying after updates -- and quietly close it diplomatically ;-)
Now to clumbisly stumble through removing 52 x86_64 packages and reinstalling
the same, but correct i686 package: drum-roll...
## Parse packages to create a list of packages for removal
for i in $(ls -1 /var/cache/pacman/pkg/*x86_64*); do pkg=${i##*/pkg/}; echo
"$pkg"; done > x86_64pkgs
while read line; do pkg=${line%%.*}; pkg=${pkg%-*}; echo -n " $pkg" >> rmlist;
done
David C. Rankin wrote:
Guys,
New strange error while I troubleshoot the dead X intel card issue. As mentioned, I have managed to get twm and openbox running in vncserver on the box with the intel card. kde4 apps will run, but look terrible due to the difference in color-depth, etc., so I was trying to get kde3/kate or kwrite running. I have always been able to run the kde3 apps from both twm and openbox before, but now I get the following error:
/opt/kde/bin/kwrite: error while loading shared libraries: libqt-mt.so.3: wrong ELF class: ELFCLASS64
same error with kate, and just about any other kde3 app. Any way to fix this?
I like vim, but I admit, I am a bit quicker with multiple kate/kwrite windows at my disposal.
I don't think this would be related to the X problem, but... could it be?
Is this a i686 box or x86_64 box? Could it be that you have an i686 box and your have mixed packages? ie a 32 bit OS and mixed in 64 bit packages?
On Sun, Oct 18, 2009 at 6:08 AM, David C. Rankin
/opt/kde/bin/kwrite: error while loading shared libraries: libqt-mt.so.3: wrong ELF class: ELFCLASS64
You are another candidate for a new feature of the future pacman 3.4 then. http://bugs.archlinux.org/task/15622
On Sun, Oct 18, 2009 at 12:30 PM, David C. Rankin
Now it seems I need to stroll on over to the bug I opened against the intel graphics dying after updates -- and quietly close it diplomatically ;-)
As a side note, your Xorg logs where you were actually using intel did not show anything wrong. Nor did dmesg. So I am not that surprised. But I expect that you already figured that before.
On 10/18/2009 06:30 AM, David C. Rankin wrote:
......That's when the lightbulb winked on and when the feeling of SHAME begin to settle in on my consciousness. Further investigation revealed that on 10/8 when I had updated my box and the new pacman package was installed, I used the pacman.conf from an earlier update of my x86_64 Arch server as a "go-by". It would seem that there was one occasion with the community repository that an 'x86_64' did not get replaced by and 'i686', thus 'the loose nut behind the keyboard' had installed some:
Good Linux debugging clue: when you're having a bunch of major problems that no one else is, it usually means you did something stupid that no one else did! :-) Seriously, though, I was reading all your messages going by, and kept thinking: there must be something weird he did to his box that's causing him all these problems, because Arch rarely gives me this much grief - especially with recent upgrades, as they've all gone very smoothly. Anyway, all's well that ends well, and glad to hear you solved the problem! DR
On Sunday 18 October 2009 10:15:25 pm David Rosenstrauch wrote:
On 10/18/2009 06:30 AM, David C. Rankin wrote:
......That's when the lightbulb winked on and when the feeling of SHAME begin to settle in on my consciousness. Further investigation revealed that on 10/8 when I had updated my box and the new pacman package was installed, I used the pacman.conf from an earlier update of my x86_64 Arch server as a "go-by". It would seem that there was one occasion with the community repository that an 'x86_64' did not get replaced by and 'i686', thus 'the loose nut behind the keyboard' had installed some:
Good Linux debugging clue: when you're having a bunch of major problems that no one else is, it usually means you did something stupid that no one else did! :-)
Seriously, though, I was reading all your messages going by, and kept thinking: there must be something weird he did to his box that's causing him all these problems, because Arch rarely gives me this much grief - especially with recent upgrades, as they've all gone very smoothly.
Anyway, all's well that ends well, and glad to hear you solved the problem!
DR
Yah.. I'm usually very good at problem solving, but in a decade with Linux, this is the first time I had ever seen an ELFCLASS64... Also, I'm still new enough with Arch and pacman that strange messages that I've never seen before don't register yet as to whether they are of the ID-10-T variety or if they have something to do with an Arch tool -- but I'll get there. P.S. The ID-10-T error? write it all together in lower-case and look at it again ;-) (id10t => idiot) I try to minimize the number of ID-10-T errors I create :p -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Sunday 18 October 2009 05:39:46 am Baho Utot wrote:
Is this a i686 box or x86_64 box?
Could it be that you have an i686 box and your have mixed packages?
ie a 32 bit OS and mixed in 64 bit packages?
Baho, It was an i686 box that I tried to turn into a x86_64 box by screwing up my pacman.conf ;-) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
participants (5)
-
Baho Utot
-
David C. Rankin
-
David Rosenstrauch
-
Eric Bélanger
-
Xavier