Hi All Anybody been able to figure out the bug and how to stop it with the above mentioned programs? Sending mail, queueing mail crashes KMail, starting a new project in KDevelop, crashes and just opening KEdit crashes. Seems these new bugs were introduced in the latest batch of patches SuSE installed from the online update. Sure would like to get things working right again SuSE, any thoughts? Patrick -- --- KMail v1.4.3 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 25 October 2002 12:01, Patrick wrote:
Hi All Anybody been able to figure out the bug and how to stop it with the above mentioned programs? Sending mail, queueing mail crashes KMail, starting a new project in KDevelop, crashes and just opening KEdit crashes. Seems these new bugs were introduced in the latest batch of patches SuSE installed from the online update.
Sure would like to get things working right again SuSE, any thoughts?
Patrick Also with me, after update kde 3.0.4 with yast2. May the problem is only the kedit, if it is used as editor by kmail and kdeveloper.
- -- Jose Thadeu Cavalcante -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9uUjsKUBbt4FrItwRAgoiAKCqYoh4xcOAKJ311omhGH2mrTwXCACfYhqr HbC2oD1UH8hqGuybgfxEltY= =BJAh -----END PGP SIGNATURE-----
On Friday 25 October 2002 02:01 pm, Patrick wrote:
any thoughts?
had this too ~ in my case, going back to the previous version of kdelibs3 fixed the probs . . . removed kdelibs3_3.0.4-5_i386.rpm & re-installed kdelibs3_3.0.4-4_i386.rpm . . . removed kdelibs3-devel_3.0.4-5_i386.rpm & re-installed kdelibs3-devel_3.0.4-4_i386.rpm Joe + Sesil kindly put me right on this. . . . that fixed it :o) -- best wishes ____________ sent on Linux ____________
On Friday 25 October 2002 02:01 pm, Patrick wrote:
any thoughts?
had this too ~ in my case, going back to the previous version of kdelibs3 fixed the probs
. . . removed kdelibs3_3.0.4-5_i386.rpm & re-installed kdelibs3_3.0.4-4_i386.rpm
. . . removed kdelibs3-devel_3.0.4-5_i386.rpm & re-installed kdelibs3-devel_3.0.4-4_i386.rpm
Joe + Sesil kindly put me right on this.
. . . that fixed it :o) ============================ tabanna, Thanks also for your help. As they did with you, they also did with me! Joe & Sesil passed along this little tidbit of info earlier today and
On Friday 25 October 2002 12:17, tabanna wrote: that cleared up my problems as well. It's disturbing to have such stable programs suddenly go awry! I would also add to that list of things, the kdelibs3-devel-doc. Once done things work right. Thanks, Patrick -- --- KMail v1.4.3 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206
On Friday 25 October 2002 18.17, tabanna wrote:
On Friday 25 October 2002 02:01 pm, Patrick wrote:
any thoughts?
had this too ~ in my case, going back to the previous version of kdelibs3 fixed the probs
Just beware that the packages in YOU are tagged as a security fix. I'm not sure going back to a previous version is a valid fix in those circumstances. Anders
On 10/26/2002 05:47 AM, Anders Johansson wrote:
On Friday 25 October 2002 18.17, tabanna wrote:
I had this too ~ in my case, going back to the previous version of kdelibs3 fixed the probs
Just beware that the packages in YOU are tagged as a security fix. I'm not sure going back to a previous version is a valid fix in those circumstances.
I would agree with you, Anders, (and I just checked and it is now available via YOU for 8.0, wasn't last time I checked), but the kdelibs3 packages (all 3 apparently) break Kedit (and apparently Kmail and K-Develop), as well as (for me) locking up several times (seemed to be related to kdesu), etc. I backed down one release number, but still same version (3.0.4). I don't know exactly what changed from 3.0.4-4 and 3.0.4-5 for kdelibs3, but the file size increased almost 3M. If the -4 version is not as secure, what else can we do (except file a bug report to feedback@suse.de, which I did as soon as I had my problem)? I am hoping SuSE would fix the packages and re-release (if I knew how I would :-) ), but I was surprised that my system is up to date with KDE (as verified by YOU) except for those 3 packages which are still the -5 versions. I suspect several folks will download the KDE updates via YOU to find out several programs are seriously broke. I truly respect your skill, and I wonder, IYHO, what should we do to be able to use kde? -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace God, I am what I am.
On Saturday 26 October 2002 09.35, Joe_Morris@ntm.org via myvscan.d-one.net wrote:
On 10/26/2002 05:47 AM, Anders Johansson wrote:
On Friday 25 October 2002 18.17, tabanna wrote:
I had this too ~ in my case, going back to the previous version of kdelibs3 fixed the probs
Just beware that the packages in YOU are tagged as a security fix. I'm not sure going back to a previous version is a valid fix in those circumstances.
I would agree with you, Anders, (and I just checked and it is now available via YOU for 8.0, wasn't last time I checked), but the kdelibs3 packages (all 3 apparently) break Kedit (and apparently Kmail and K-Develop), as well as (for me) locking up several times (seemed to be related to kdesu), etc. I backed down one release number, but still same version (3.0.4). I don't know exactly what changed from 3.0.4-4 and 3.0.4-5 for kdelibs3, but the file size increased almost 3M. If the -4 version is not as secure, what else can we do (except file a bug report to feedback@suse.de, which I did as soon as I had my problem)? I am hoping SuSE would fix the packages and re-release (if I knew how I would :-) ), but I was surprised that my system is up to date with KDE (as verified by YOU) except for those 3 packages which are still the -5 versions. I suspect several folks will download the KDE updates via YOU to find out several programs are seriously broke. I truly respect your skill, and I wonder, IYHO, what should we do to be able to use kde?
I'm afraid I can't be of any help here. I have three computers here, one running 8.1 and two running 8.0, and the updates all work on my systems. I haven't seen the crashes others experience. And it's extremely difficult, perhaps even impossible, to solve a crash without being able to reproduce it. Anders
On 10/26/2002 05:38 PM, Anders Johansson wrote:
On Saturday 26 October 2002 09.35, Joe_Morris@ntm.org via myvscan.d-one.net wrote:
On 10/26/2002 05:47 AM, Anders Johansson wrote:
On Friday 25 October 2002 18.17, tabanna wrote:
I had this too ~ in my case, going back to the previous version of kdelibs3 fixed the probs
Just beware that the packages in YOU are tagged as a security fix. I'm not sure going back to a previous version is a valid fix in those circumstances.
I would agree with you, Anders, <snip>, what should we do to be able to use kde?
I'm afraid I can't be of any help here. I have three computers here, one running 8.1 and two running 8.0, and the updates all work on my systems. I haven't seen the crashes others experience. And it's extremely difficult, perhaps even impossible, to solve a crash without being able to reproduce it.
Well, I figured if it worked on anyone's computer, maybe it wasn't a major programming error. (I think Anders is the first running 8.0 that had no problems after the update?). So, I downloaded the source rpm last night, and after recompiling/building the rpm, I installed all 3 [even optimized them for i586], and Kedit is no longer crashing. Can't begin to explain why, but I hope it helps others. I have only tried it less than a day, but since the crashes were every time, I think it may have fixed Kedits problem with kdelibs3. I don't use Kmail, so I would be interested if it fixed that as well. Anyway, should be no more security issues that way. Now, on to the next problem. ;-) -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace God, I am what I am.
On Sunday 27 October 2002 00:20, Joe & Sesil Morris (NTM) wrote:
Well, I figured if it worked on anyone's computer, maybe it wasn't a major programming error. (I think Anders is the first running 8.0 that had no problems after the update?). So, I downloaded the source rpm last night, and after recompiling/building the rpm, I installed all 3 [even optimized them for i586], and Kedit is no longer crashing. Can't begin to explain why, but I hope it helps others. I have only tried it less than a day, but since the crashes were every time, I think it may have fixed Kedits problem with kdelibs3. I don't use Kmail, so I would be interested if it fixed that as well. Anyway, should be no more security issues that way. Now, on to the next problem. ;-) ===================
Ok Joe, thanks. I can also confirm that compiling from source does indeed fix kdelibs3-3.0.4-5 files. Everything is working correctly now, KEdit, KDevelop and KMail all have no problems! I did the i386 build first, just for safety's sake, but will do the i586 now that I know it all works good. Thanks Onward we go! Patrick -- --- KMail v1.4.3 --- SuSE Linux Pro v8.0 --- Registered Linux User #225206
Hi, On Sunday 27 October 2002 08:18, Patrick wrote:
On Sunday 27 October 2002 00:20, Joe & Sesil Morris (NTM) wrote:
Well, I figured if it worked on anyone's computer, maybe it wasn't a major programming error. (I think Anders is the first running 8.0 that had no problems after the update?). So, I downloaded the source rpm last night, and after recompiling/building the rpm, I installed all 3 [even optimized them for i586], and Kedit is no longer crashing. Can't begin to explain why, but I hope it helps others. I have only tried it less than a day, but since the crashes were every time, I think it may have fixed Kedits problem with kdelibs3. I don't use Kmail, so I would be interested if it fixed that as well. Anyway, should be no more security issues that way. Now, on to the next problem. ;-)
===================
Ok Joe, thanks. I can also confirm that compiling from source does indeed fix kdelibs3-3.0.4-5 files. Everything is working correctly now, KEdit, KDevelop and KMail all have no problems! I did the i386 build first, just for safety's sake, but will do the i586 now that I know it all works good. Thanks
I've tried to build kdelibs3.rpm from sources, but I get a compiler error. I'm afraid I did something wrong. I think I installed all devel packages needed. This is what I made: 1) install the source file with 'apt-get source kdelibs3' 2) 'cd /usr/src/pcakages/SPECS' 3) rpm -ba kdelibs3.spec The error is g++ -shared -nostdlib /usr/lib/crti.o /usr/lib/gcc-lib/i486-suse-linux/2.95.3/crtbeginS.o .libs/libDCOP_la.all_cpp.o -Wl,--whole-archive KDE-ICE/.libs/libkICE.a -Wl,--no-whole-archive -Wl,--rpath -Wl,/usr/local/lib -L/usr/local/i686-pc-linux-gnu/lib -L/usr/local/i686-pc-linux-gnu/bin -L/tmp/objdir/gcc -L/tmp/objdir/i686-pc-linux-gnu/libstdc++-v3/src/.libs -L/tmp/objdir/i686-pc-linux-gnu/libstdc++-v3/src -L/usr/X11R6/lib -L/usr/lib/qt3/lib -L/opt/kde3/lib KDE-ICE/.libs/libkICE.a -lqt-mt -lpng -lz -lXext -lX11 -lresolv -lSM -lICE -lpthread -L/usr/lib/gcc-lib/i486-suse-linux/2.95.3 -L/usr/i486-suse-linux/lib /usr/local/lib/libstdc++.so -lgcc_s -lm -lc -lgcc -lc /usr/lib/gcc-lib/i486-suse-linux/2.95.3/crtendS.o /usr/lib/crtn.o -DNDEBUG -DNO_DEBUG -O2 -O2 -march=i486 -mcpu=i686 -DNDEBUG -fno-exceptions -fno-check-new -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_COMPAT -Wl,-soname -Wl,libDCOP.so.4 -o .libs/libDCOP.so.4.0.0 /usr/i486-suse-linux/bin/ld: .libs/libDCOP.so.4.0.0: undefined versioned symbol name __dynamic_cast@@CXXABI_1 /usr/i486-suse-linux/bin/ld: failed to set dynamic section sizes: Bad value collect2: ld returned 1 exit status make[3]: *** [libDCOP.la] Error 1 make[3]: Saliendo directorio `/usr/src/packages/BUILD/kdelibs-3.0.4/dcop' make[2]: *** [all-recursive] Error 1 make[2]: Saliendo directorio `/usr/src/packages/BUILD/kdelibs-3.0.4/dcop' make[1]: *** [all-recursive] Error 1 make[1]: Saliendo directorio `/usr/src/packages/BUILD/kdelibs-3.0.4' make: *** [all] Error 2 Bad exit status from /var/tmp/rpm-tmp.16016 (%build) Any suggestion?. SuSE 8.0 pro. Guillermo.
Onward we go! Patrick
-- Guillermo Ballester Valor gbv@oxixares.com Ogijares, Granada SPAIN
Op zondag 27 oktober 2002 11:33, schreef Guillermo Ballester Valor:
/usr/i486-suse-linux/bin/ld: failed to set dynamic section sizes: Bad value collect2: ld returned 1 exit status make[3]: *** [libDCOP.la] Error 1
Have you set KDEDIR and QTDIR to the correct path? -- Richard Bos Without a home the journey is endless
On Sunday 27 October 2002 11.33, Guillermo Ballester Valor wrote:
I've tried to build kdelibs3.rpm from sources, but I get a compiler error. I'm afraid I did something wrong. I think I installed all devel packages needed. This is what I made: 1) install the source file with 'apt-get source kdelibs3' 2) 'cd /usr/src/pcakages/SPECS' 3) rpm -ba kdelibs3.spec
The error is
g++ -shared -nostdlib /usr/lib/crti.o /usr/lib/gcc-lib/i486-suse-linux/2.95.3/crtbeginS.o
gcc 2.95.3
.libs/libDCOP_la.all_cpp.o -Wl,--whole-archive KDE-ICE/.libs/libkICE.a -Wl,--no-whole-archive -Wl,--rpath -Wl,/usr/local/lib -L/usr/local/i686-pc-linux-gnu/lib
What's this?
-L/usr/local/i686-pc-linux-gnu/bin -L/tmp/objdir/gcc
Not to mention this?
-L/tmp/objdir/i686-pc-linux-gnu/libstdc++-v3/src/.libs -L/tmp/objdir/i686-pc-linux-gnu/libstdc++-v3/src -L/usr/X11R6/lib -L/usr/lib/qt3/lib -L/opt/kde3/lib KDE-ICE/.libs/libkICE.a -lqt-mt -lpng -lz -lXext -lX11 -lresolv -lSM -lICE -lpthread -L/usr/lib/gcc-lib/i486-suse-linux/2.95.3 -L/usr/i486-suse-linux/lib /usr/local/lib/libstdc++.so -lgcc_s
Looks suspiciously like gcc 3.x
-lm -lc -lgcc -lc /usr/lib/gcc-lib/i486-suse-linux/2.95.3/crtendS.o /usr/lib/crtn.o -DNDEBUG -DNO_DEBUG -O2 -O2 -march=i486 -mcpu=i686 -DNDEBUG -fno-exceptions -fno-check-new -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_COMPAT -Wl,-soname -Wl,libDCOP.so.4 -o .libs/libDCOP.so.4.0.0 /usr/i486-suse-linux/bin/ld: .libs/libDCOP.so.4.0.0: undefined versioned symbol name __dynamic_cast@@CXXABI_1 /usr/i486-suse-linux/bin/ld: failed to set dynamic section sizes: Bad value collect2: ld returned 1 exit status make[3]: *** [libDCOP.la] Error 1 make[3]: Saliendo directorio `/usr/src/packages/BUILD/kdelibs-3.0.4/dcop' make[2]: *** [all-recursive] Error 1 make[2]: Saliendo directorio `/usr/src/packages/BUILD/kdelibs-3.0.4/dcop' make[1]: *** [all-recursive] Error 1 make[1]: Saliendo directorio `/usr/src/packages/BUILD/kdelibs-3.0.4' make: *** [all] Error 2 Bad exit status from /var/tmp/rpm-tmp.16016 (%build)
Any suggestion?.
Yes. If you're going to customise your system, keep it consistent. Mixing compilers isn't a good idea. And storing executables in /tmp is downright stupid. Any program for any reason could blow it away at almost any time.
SuSE 8.0 pro.
heavily modified. Anders
Hi, Ooops!. This was the remaining of a bad compilation I made for gcc 3.1 when I was learning (some months ago). I forgot to set in /usr/local/gcc-3.1 and installed it at /usr/local. It also explain some other extrange problems trying to compile some packages :). Now I cleaned it and my system is just compiling kdelibs3 without problems :-) Thank you for your help!. BTW, I have gcc 3.2 installed in /usr/local/gcc-3.2 with the suffix program '-3.2' and there is no problem on it. Have a nice Sunday. Here in Spain it is sunny and warm. Guillermo. On Sunday 27 October 2002 11:50, Anders Johansson wrote:
On Sunday 27 October 2002 11.33, Guillermo Ballester Valor wrote:
I've tried to build kdelibs3.rpm from sources, but I get a compiler error. I'm afraid I did something wrong. I think I installed all devel packages needed. This is what I made: 1) install the source file with 'apt-get source kdelibs3' 2) 'cd /usr/src/pcakages/SPECS' 3) rpm -ba kdelibs3.spec
The error is
g++ -shared -nostdlib /usr/lib/crti.o /usr/lib/gcc-lib/i486-suse-linux/2.95.3/crtbeginS.o
gcc 2.95.3
.libs/libDCOP_la.all_cpp.o -Wl,--whole-archive KDE-ICE/.libs/libkICE.a -Wl,--no-whole-archive -Wl,--rpath -Wl,/usr/local/lib -L/usr/local/i686-pc-linux-gnu/lib
What's this?
-L/usr/local/i686-pc-linux-gnu/bin -L/tmp/objdir/gcc
Not to mention this?
-L/tmp/objdir/i686-pc-linux-gnu/libstdc++-v3/src/.libs -L/tmp/objdir/i686-pc-linux-gnu/libstdc++-v3/src -L/usr/X11R6/lib -L/usr/lib/qt3/lib -L/opt/kde3/lib KDE-ICE/.libs/libkICE.a -lqt-mt -lpng -lz -lXext -lX11 -lresolv -lSM -lICE -lpthread -L/usr/lib/gcc-lib/i486-suse-linux/2.95.3 -L/usr/i486-suse-linux/lib /usr/local/lib/libstdc++.so -lgcc_s
Looks suspiciously like gcc 3.x
-lm -lc -lgcc -lc /usr/lib/gcc-lib/i486-suse-linux/2.95.3/crtendS.o /usr/lib/crtn.o -DNDEBUG -DNO_DEBUG -O2 -O2 -march=i486 -mcpu=i686 -DNDEBUG -fno-exceptions -fno-check-new -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_COMPAT -Wl,-soname -Wl,libDCOP.so.4 -o .libs/libDCOP.so.4.0.0 /usr/i486-suse-linux/bin/ld: .libs/libDCOP.so.4.0.0: undefined versioned symbol name __dynamic_cast@@CXXABI_1 /usr/i486-suse-linux/bin/ld: failed to set dynamic section sizes: Bad value collect2: ld returned 1 exit status make[3]: *** [libDCOP.la] Error 1 make[3]: Saliendo directorio `/usr/src/packages/BUILD/kdelibs-3.0.4/dcop' make[2]: *** [all-recursive] Error 1 make[2]: Saliendo directorio `/usr/src/packages/BUILD/kdelibs-3.0.4/dcop' make[1]: *** [all-recursive] Error 1 make[1]: Saliendo directorio `/usr/src/packages/BUILD/kdelibs-3.0.4' make: *** [all] Error 2 Bad exit status from /var/tmp/rpm-tmp.16016 (%build)
Any suggestion?.
Yes. If you're going to customise your system, keep it consistent. Mixing compilers isn't a good idea. And storing executables in /tmp is downright stupid. Any program for any reason could blow it away at almost any time.
SuSE 8.0 pro.
heavily modified.
Anders
-- Guillermo Ballester Valor gbv@oxixares.com Ogijares, Granada SPAIN
On Sunday 27 October 2002 08:18, Patrick wrote:
On Sunday 27 October 2002 00:20, Joe & Sesil Morris (NTM) wrote:
Well, I figured if it worked on anyone's computer, maybe it wasn't a major programming error. (I think Anders is the first running 8.0 that had no problems after the update?). So, I downloaded the source rpm last night, and after recompiling/building the rpm, I installed all 3 [even optimized them for i586], and Kedit is no longer crashing. Can't begin to explain why, but I hope it helps others. I have only tried it less than a day, but since the crashes were every time, I think it may have fixed Kedits problem with kdelibs3. I don't use Kmail, so I would be interested if it fixed that as well. Anyway, should be no more security issues that way. Now, on to the next problem. ;-)
===================
Ok Joe, thanks. I can also confirm that compiling from source does indeed fix kdelibs3-3.0.4-5 files. Everything is working correctly now, KEdit, KDevelop and KMail all have no problems! I did the i386 build first, just for safety's sake, but will do the i586 now that I know it all works good. Thanks
I also can confirm it is solved in my system after compiling kdelibs3 from sources. It is strange. If compiling from SuSE sources rpm it runs OK, Why in the world the rpm from SuSE (same version) gives problems? Is it an error in compilation stage in SuSE site or a corruption in binaries? Guillermo.
Onward we go! Patrick
-- Guillermo Ballester Valor gbv@oxixares.com Ogijares, Granada SPAIN
On Sun, Oct 27, 2002 at 08:47:25PM +0100, Guillermo Ballester Valor wrote:
Ok Joe, thanks. I can also confirm that compiling from source does indeed fix kdelibs3-3.0.4-5 files. Everything is working correctly now, KEdit, KDevelop and KMail all have no problems! I did the i386 build first, just for safety's sake, but will do the i586 now that I know it all works good. Thanks
I also can confirm it is solved in my system after compiling kdelibs3 from sources.
It is strange. If compiling from SuSE sources rpm it runs OK, Why in the world the rpm from SuSE (same version) gives problems? Is it an error in compilation stage in SuSE site or a corruption in binaries?
I think the problem is that kdelibs3-3.0.4-5 in kde6 directory (an "official" update) is compiled against qt3-3.0.5 which is missing from "official" update tree. If you grab qt3-3.0.5 (and qt3-non-mt) from supplementary directory, kdelibs3 should work fine. Regards, -Kastus
On 10/28/2002 04:13 AM, Konstantin (Kastus) Shchuka wrote:
I think the problem is that kdelibs3-3.0.4-5 in kde6 directory (an "official" update) is compiled against qt3-3.0.5 which is missing from "official" update tree. If you grab qt3-3.0.5 (and qt3-non-mt) from supplementary directory, kdelibs3 should work fine.
I'm afraid not. I had updated to qt3-3.0.5 before kdelibs3-3.0.4-5 came out, so that isn't the missing factor. Obviously as well, I just rebuilt it with qt3-3.0.5 as well. My suspicion is either cpu or video. I am using an AMD K6 3-400 with an ATI rage fury. I believe Anders, who is the only one I have heard that didn't have a problem with the update and Kedit, Kmail, etc., has intel and nvidea. Is it possible the SuSE binary was compiled on an nvidea machine / nvidea kernel that introduced bugs for those of us running ATI??? Anyway, I'm just happy SuSE provided the source rpm and that my machine is working again. -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace God, I am what I am.
On Monday 28 October 2002 01.06, Joe & Sesil Morris (NTM) wrote:
On 10/28/2002 04:13 AM, Konstantin (Kastus) Shchuka wrote:
I think the problem is that kdelibs3-3.0.4-5 in kde6 directory (an "official" update) is compiled against qt3-3.0.5 which is missing from "official" update tree. If you grab qt3-3.0.5 (and qt3-non-mt) from supplementary directory, kdelibs3 should work fine.
I'm afraid not. I had updated to qt3-3.0.5 before kdelibs3-3.0.4-5 came out, so that isn't the missing factor. Obviously as well, I just rebuilt it with qt3-3.0.5 as well. My suspicion is either cpu or video. I am using an AMD K6 3-400 with an ATI rage fury. I believe Anders, who is the only one I have heard that didn't have a problem with the update and Kedit, Kmail, etc., has intel and nvidea.
hwinfo --cpu Vendor: "AuthenticAMD" Model: 6.3.1 "AMD Duron(tm) processor" hwinfo --gfxcard Model: "Trident Microsystems CyberBlade/i1" Vendor: 1023 "Trident Microsystems" Device: 8500 "CyberBlade/i1" I do have an nvidia card, but that's on my main workstation (dual Athlon 1600+ MP), and there I run 8.1. Anders
On 10/28/2002 08:11 AM, Anders Johansson wrote:
On Monday 28 October 2002 01.06, Joe & Sesil Morris (NTM) wrote:
My suspicion is either cpu or video. I am using an AMD K6 3-400 with an ATI rage fury. I believe Anders, who is the only one I have heard that didn't have a problem with the update and Kedit, Kmail, etc., has intel and nvidea.
hwinfo --cpu Vendor: "AuthenticAMD" Model: 6.3.1 "AMD Duron(tm) processor"
hwinfo --gfxcard Model: "Trident Microsystems CyberBlade/i1" Vendor: 1023 "Trident Microsystems" Device: 8500 "CyberBlade/i1"
I do have an nvidia card, but that's on my main workstation (dual Athlon 1600+ MP), and there I run 8.1.
Oh well, another good theory shot. I'm out of ideas then, as to why recompiling /rebuilding the rpm locally fixes this problem on our machines, but others have no problems. I can't be a corrupted binary, as I installed both the binary, and later let YOU install the patch rpm. I guess this one is for only the gurus to understand. :-) -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace God, I am what I am.
On Monday 28 October 2002 02.10, Joe & Sesil Morris (NTM) wrote:
Oh well, another good theory shot. I'm out of ideas then, as to why recompiling /rebuilding the rpm locally fixes this problem on our machines, but others have no problems. I can't be a corrupted binary, as I installed both the binary, and later let YOU install the patch rpm. I guess this one is for only the gurus to understand. :-)
considering the rpm was built against qt-3.0.5, perhaps it was built against other supplementary packages too. I don't keep that machine very up to date with the graphical stuff, and haven't installed the supp. kde packages in a long while. That could be a reason. Anders
participants (9)
-
Anders Johansson -
Anders Johansson -
Guillermo Ballester Valor -
Joe & Sesil Morris (NTM) -
Jose Thadeu Cavalcante -
Konstantin (Kastus) Shchuka -
Patrick -
Richard Bos -
tabanna