Hi, When I run mozilla, I get the following: sole@djuro:~> mozilla & [2] 21256 sole@djuro:~> grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory cut: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory sed: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory After this, mozilla starts up and works fine... The rest of the system looks fine too - all working as far as I can see. But, anyway this error persists both for root and normal user, indicating that something is not OK. In another thread on this list I learned that libc.so.6 is a part of glibc, and that it's so important that it is very unlikely that it is not installed. I checked for glibc and, yes, it's there. Any explanations? TIA Radule Soskic p.s. It is a fresh install 8.1 updated to all "security and recommended" via YOU
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Mardi 12 Novembre 2002 11:12, Radule Soskic a écrit :
When I run mozilla, I get the following:
sole@djuro:~> mozilla & [2] 21256 sole@djuro:~> grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory cut: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory sed: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
After this, mozilla starts up and works fine... The rest of the system looks fine too - all working as far as I can see.
But, anyway this error persists both for root and normal user, indicating that something is not OK.
In another thread on this list I learned that libc.so.6 is a part of glibc, and that it's so important that it is very unlikely that it is not installed. I checked for glibc and, yes, it's there.
Any explanations?
TIA
Radule Soskic
p.s. It is a fresh install 8.1 updated to all "security and recommended" via YOU
The problem is not Mozilla but Java (something to do with the new compiler gcc3). You probably haven't updated your system for a while, as the fix is available by YOU (glic-2.2.5-161). The problem disappears as soos as this patch is installed. - -- Thibaut Cousin E-mail : cousin@in2p3.fr Web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE90Mm+v1vqsTa1E4oRAh5lAKC08O3w2W75H9MbOd6jgQS3AZL/fwCeNgue r8oGVAf0ai5vm2zIjpO0A7g= =Xwm+ -----END PGP SIGNATURE-----
On Tue, Nov 12, 2002 at 10:28:27AM +0100, Thibaut Cousin wrote:
Le Mardi 12 Novembre 2002 11:12, Radule Soskic a ?crit :
When I run mozilla, I get the following:
sole@djuro:~> mozilla & [2] 21256 sole@djuro:~> grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
The problem is not Mozilla but Java (something to do with the new compiler gcc3). You probably haven't updated your system for a while, as the fix is available by YOU (glic-2.2.5-161). The problem disappears as soos as this patch is installed.
I can't say about glibc-2.2.5-161 but with -164 (Build Date: Thu Oct 24 09:22:11 2002) the problem is still there. And the actual problem is in LD_ASSUME_KERNEL environment variable. The mozilla start script sets this variable to 2.2.5 to check the JDK version and this is where it breaks. To test it just run the following command: LD_ASSUME_KERNEL=2.2.5 grep a /etc/motd It will give you the same error message about loading shared libraries. I just commented out setting LD_ASSUME_KERNEL=2.2.5 in /usr/X11R6/bin/mozilla, but anyway, the messages are harmless. Regards, -Kastus
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Mercredi 13 Novembre 2002 06:04, Konstantin (Kastus) Shchuka a écrit :
The problem is not Mozilla but Java (something to do with the new compiler gcc3). You probably haven't updated your system for a while, as the fix is available by YOU (glic-2.2.5-161). The problem disappears as soos as this patch is installed.
I can't say about glibc-2.2.5-161 but with -164 (Build Date: Thu Oct 24 09:22:11 2002) the problem is still there. And the actual problem is in LD_ASSUME_KERNEL environment variable. The mozilla start script sets this variable to 2.2.5 to check the JDK version and this is where it breaks.
To test it just run the following command:
LD_ASSUME_KERNEL=2.2.5 grep a /etc/motd
It will give you the same error message about loading shared libraries.
I just commented out setting LD_ASSUME_KERNEL=2.2.5 in /usr/X11R6/bin/mozilla, but anyway, the messages are harmless.
The -164 release of glibc is not an official update (no patch for it, restricted to i686). First I used it, then I downgraded to -161 and it worked much better (not only in Mozilla, but also in JBuilder, etc). - -- Thibaut Cousin E-mail : cousin@in2p3.fr Web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE90f+iv1vqsTa1E4oRAjmrAJ9bupJnEiAoFf4xHGd/0VHhvlZhbQCg1DP8 Xga38wzAnAbmzIvifKYAAJg= =eI5h -----END PGP SIGNATURE-----
On Wed, Nov 13, Thibaut Cousin wrote:
The -164 release of glibc is not an official update (no patch for it, restricted to i686). First I used it, then I downgraded to -161 and it worked much better (not only in Mozilla, but also in JBuilder, etc).
*ROTFL* The only change you can see with the new glibc is, that Netscape 4.8 does not crash with java. It is impossible that you see any changes with Mozilla or JBuilder, there where no changes in this area! Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de SuSE Linux AG Deutschherrnstr. 15-19 D-90429 Nuernberg -------------------------------------------------------------------- Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Mercredi 13 Novembre 2002 11:09, Thorsten Kukuk a écrit :
The -164 release of glibc is not an official update (no patch for it, restricted to i686). First I used it, then I downgraded to -161 and it worked much better (not only in Mozilla, but also in JBuilder, etc).
*ROTFL*
The only change you can see with the new glibc is, that Netscape 4.8 does not crash with java. It is impossible that you see any changes with Mozilla or JBuilder, there where no changes in this area!
I've read the changelog all right. To be honest I didn't understand most of it, but I know one thing: I installed 8.1 on four machines here at work and JBuilder and Mozilla had problems (same message: libc.so.6 not found). I upgraded glibc to 2.2.5-161 and the problem disappeared on all four machines. I made no other update at the same time. Maybe you can give me the real explanation, then. I'm interested! - -- Thibaut Cousin E-mail : cousin@in2p3.fr Web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE90k+Ev1vqsTa1E4oRAmRmAKDAFzPnlDQob0uEA0hh36MyvaArbACdGE8m q0ygIubIrU6wERcPBpt6hSA= =RzGT -----END PGP SIGNATURE-----
On Wed, Nov 13, Thibaut Cousin wrote:
I've read the changelog all right. To be honest I didn't understand most of it, but I know one thing: I installed 8.1 on four machines here at work and JBuilder and Mozilla had problems (same message: libc.so.6 not found). I upgraded glibc to 2.2.5-161 and the problem disappeared on all four machines. I made no other update at the same time. Maybe you can give me the real explanation, then. I'm interested!
You installed the wrong glibc. I think you had the i686 before and now you have the i586 one. Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de SuSE Linux AG Deutschherrnstr. 15-19 D-90429 Nuernberg -------------------------------------------------------------------- Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Mercredi 13 Novembre 2002 14:20, Thorsten Kukuk a écrit :
On Wed, Nov 13, Thibaut Cousin wrote:
I've read the changelog all right. To be honest I didn't understand most of it, but I know one thing: I installed 8.1 on four machines here at work and JBuilder and Mozilla had problems (same message: libc.so.6 not found). I upgraded glibc to 2.2.5-161 and the problem disappeared on all four machines. I made no other update at the same time. Maybe you can give me the real explanation, then. I'm interested!
You installed the wrong glibc. I think you had the i686 before and now you have the i586 one.
This is true for only one machine out the four which I mentioned. Anyway, the fourth one is a K6 so I couldn't have the i686 package installed. - -- Thibaut Cousin E-mail : cousin@in2p3.fr Web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE90lPbv1vqsTa1E4oRApmaAJ9Hbvo9odwq72NMZX1WQo+PxLItxACgr9sh 890g9BF7sHqcInkbgrnxOVk= =+U15 -----END PGP SIGNATURE-----
On Wednesday 13 November 2002 14.30, Thibaut Cousin wrote:
This is true for only one machine out the four which I mentioned. Anyway, the fourth one is a K6 so I couldn't have the i686 package installed.
Just a hunch, but did you by any chance upgrade java to 1.4? I don't know about JBuilder, but looking at the mozilla startup script, the variable LD_ASSUME_KERNEL is only exported for java version 1.3. Maybe that's it? Anders
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Mercredi 13 Novembre 2002 14:32, Anders Johansson a écrit :
This is true for only one machine out the four which I mentioned. Anyway, the fourth one is a K6 so I couldn't have the i686 package installed.
Just a hunch, but did you by any chance upgrade java to 1.4? I don't know about JBuilder, but looking at the mozilla startup script, the variable LD_ASSUME_KERNEL is only exported for java version 1.3. Maybe that's it?
No, the 8.1 install was relatively "fresh", no major update. Mozilla had the known problem (message during startup). JBuilder refused to install: the installer gave the message as soon as it started and aborted. - -- Thibaut Cousin E-mail : cousin@in2p3.fr Web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE90lbdv1vqsTa1E4oRAgcXAKCB26SZJRUmVQstEAUlMi1P20igzACgiEzt pzG/8iZwgK1YbYyexBFVioU= =/Zj4 -----END PGP SIGNATURE-----
The -164 release of glibc is not an official update (no patch for it, restricted to i686). First I used it, then I downgraded to -161 and it worked much better (not only in Mozilla, but also in JBuilder, etc).
After sending the last reply to this topic and reading this, I realized that my -164 version came with the evolution update via red-carpet. (sorry, I was originally thinking it came from YOU) -Jeric
On Wednesday 13 November 2002 17.20, Jeric wrote:
The -164 release of glibc is not an official update (no patch for it, restricted to i686). First I used it, then I downgraded to -161 and it worked much better (not only in Mozilla, but also in JBuilder, etc).
After sending the last reply to this topic and reading this, I realized that my -164 version came with the evolution update via red-carpet. (sorry, I was originally thinking it came from YOU)
It is an official update, it does come through YOU, it is in the official update directory on ftp.suse.com.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Mercredi 13 Novembre 2002 17:18, Anders Johansson a écrit :
The -164 release of glibc is not an official update (no patch for it, restricted to i686). First I used it, then I downgraded to -161 and it worked much better (not only in Mozilla, but also in JBuilder, etc).
After sending the last reply to this topic and reading this, I realized that my -164 version came with the evolution update via red-carpet. (sorry, I was originally thinking it came from YOU)
It is an official update, it does come through YOU, it is in the official update directory on ftp.suse.com.
Yes, it is in the proper directory on the FTP sites, but YOU never donwloads it. All my 8.1 machines are up-to-date and their glibc is 2.2.5-161. I think YOU does not see it because there is no "patch" file (the last patch file is glibc-13001 and it still points to release 161). That's why I said it was not really official: YOU does not see it. Which is fortunate, as I have issues with -164 and not with -161. - -- Thibaut Cousin E-mail : cousin@in2p3.fr Web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE90n8Wv1vqsTa1E4oRAh0SAJsEHgu9pR1STDS4AIUF+X9t8i+bdwCdG9b5 Rwvq44jOgmfclJmrMZN9NGo= =efoo -----END PGP SIGNATURE-----
On Wed, Nov 13, Thibaut Cousin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Le Mercredi 13 Novembre 2002 17:18, Anders Johansson a écrit :
The -164 release of glibc is not an official update (no patch for it, restricted to i686). First I used it, then I downgraded to -161 and it worked much better (not only in Mozilla, but also in JBuilder, etc).
After sending the last reply to this topic and reading this, I realized that my -164 version came with the evolution update via red-carpet. (sorry, I was originally thinking it came from YOU)
It is an official update, it does come through YOU, it is in the official update directory on ftp.suse.com.
Yes, it is in the proper directory on the FTP sites, but YOU never donwloads it. All my 8.1 machines are up-to-date and their glibc is 2.2.5-161. I think YOU does not see it because there is no "patch" file (the last patch file is glibc-13001 and it still points to release 161). That's why I said it was not really official: YOU does not see it. Which is fortunate, as I have issues with -164 and not with -161.
YOU does see it and install it, if you have the right hardware. -164 is only for i686 hardware. -- Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de SuSE Linux AG Deutschherrnstr. 15-19 D-90429 Nuernberg -------------------------------------------------------------------- Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
Actually, there is a patch file but not in the patch directory. If you go to the update/8.1/i586 (could be in i686 as well) you'll see three files relating to glibc. One is glibc-2.2.5-161.i586.patch.rpm, and glibc-2.2.5-161.i586.rpm and glibc.rpm which is a symlink to the second one. So, I'm wondering why this isn't in the patch dir, since that's the only place YaST seems to look. Overall, I still have issues with YaST2. I don't like the fact that I still can't browse directories. And the integration into konq seems weak and inconsistant. I know many complained when YaST1 went bye bye and I was one. I was hoping that the functionalities in the original version would come back. And the iprovements are nice in YaST2 but not quite what I wanted. Installing from a directory with konq just isn't cutting it, and loading YaST and trying to point it to a dir only gets the "can't find installation source" messages. Cheers, Curtis On Wednesday 13 November 2002 13:21, Thorsten Kukuk wrote:
On Wed, Nov 13, Thibaut Cousin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Le Mercredi 13 Novembre 2002 17:18, Anders Johansson a écrit :
The -164 release of glibc is not an official update (no patch for it, restricted to i686). First I used it, then I downgraded to -161 and it worked much better (not only in Mozilla, but also in JBuilder, etc).
After sending the last reply to this topic and reading this, I realized that my -164 version came with the evolution update via red-carpet. (sorry, I was originally thinking it came from YOU)
It is an official update, it does come through YOU, it is in the official update directory on ftp.suse.com.
Yes, it is in the proper directory on the FTP sites, but YOU never donwloads it. All my 8.1 machines are up-to-date and their glibc is 2.2.5-161. I think YOU does not see it because there is no "patch" file (the last patch file is glibc-13001 and it still points to release 161). That's why I said it was not really official: YOU does not see it. Which is fortunate, as I have issues with -164 and not with -161.
YOU does see it and install it, if you have the right hardware. -164 is only for i686 hardware.
-- Billboard Writer vs. Literature = Micorsoft vs. Computing,
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Mercredi 13 Novembre 2002 20:21, Thorsten Kukuk a écrit :
YOU does see it and install it, if you have the right hardware. -164 is only for i686 hardware.
I'm surprised. I have three machines compatible with i686 (PIII 450, Duron 1200 and Athlon 1800) with 8.1 installed. In the list of proposed updates, YOU displays only -161. I've just checked it again on my machine (PIII 450 here at work) and YOU proposes only -161. It is normal, as the "patches" directory contains only a glibc-13001 file which points to -161, not to -164. - -- Thibaut Cousin E-mail : cousin@in2p3.fr Web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE902NJv1vqsTa1E4oRAhp8AKDJ1wXauddABhj8jAmWV3Ne8wWHugCfbEU7 PBM/06HJEhzlTr9xxKz4TqY= =m88D -----END PGP SIGNATURE-----
On Thu, Nov 14, Thibaut Cousin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Le Mercredi 13 Novembre 2002 20:21, Thorsten Kukuk a écrit :
YOU does see it and install it, if you have the right hardware. -164 is only for i686 hardware.
I'm surprised. I have three machines compatible with i686 (PIII 450, Duron 1200 and Athlon 1800) with 8.1 installed. In the list of proposed updates, YOU displays only -161. I've just checked it again on my machine (PIII 450 here at work) and YOU proposes only -161. It is normal, as the "patches" directory contains only a glibc-13001 file which points to -161, not to -164.
And what does rpm -qi glibc tell you? -- Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de SuSE Linux AG Deutschherrnstr. 15-19 D-90429 Nuernberg -------------------------------------------------------------------- Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Jeudi 14 Novembre 2002 09:49, Thorsten Kukuk a écrit :
Le Mercredi 13 Novembre 2002 20:21, Thorsten Kukuk a écrit :
YOU does see it and install it, if you have the right hardware. -164 is only for i686 hardware.
I'm surprised. I have three machines compatible with i686 (PIII 450, Duron 1200 and Athlon 1800) with 8.1 installed. In the list of proposed updates, YOU displays only -161. I've just checked it again on my machine (PIII 450 here at work) and YOU proposes only -161. It is normal, as the "patches" directory contains only a glibc-13001 file which points to -161, not to -164.
And what does rpm -qi glibc tell you?
What I expect: glibc is installed with version 2.2.5-161. Sorry to repeat it, but I don't see how YOU could install -164, as it is not visible (no patch file for it in the "patches" directory). - -- Thibaut Cousin E-mail : cousin@in2p3.fr Web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE902Xpv1vqsTa1E4oRAqP8AJ9ibaNXd0bvc4LYzsLUlf00jADNqACeJKoc FcSkzzQFWziQjt3q6SpQK9s= =6ZYX -----END PGP SIGNATURE-----
On Thu, Nov 14, Thibaut Cousin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Le Jeudi 14 Novembre 2002 09:49, Thorsten Kukuk a écrit :
Le Mercredi 13 Novembre 2002 20:21, Thorsten Kukuk a écrit :
YOU does see it and install it, if you have the right hardware. -164 is only for i686 hardware.
I'm surprised. I have three machines compatible with i686 (PIII 450, Duron 1200 and Athlon 1800) with 8.1 installed. In the list of proposed updates, YOU displays only -161. I've just checked it again on my machine (PIII 450 here at work) and YOU proposes only -161. It is normal, as the "patches" directory contains only a glibc-13001 file which points to -161, not to -164.
And what does rpm -qi glibc tell you?
What I expect: glibc is installed with version 2.2.5-161.
Is it really a i686 glibc? This sounds like the i586 one is installed, because there is no 2.2.5-161 for i686.
Sorry to repeat it, but I don't see how YOU could install -164, as it is not visible (no patch file for it in the "patches" directory).
YOU know it. Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de SuSE Linux AG Deutschherrnstr. 15-19 D-90429 Nuernberg -------------------------------------------------------------------- Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Jeudi 14 Novembre 2002 12:03, Thorsten Kukuk a écrit :
What I expect: glibc is installed with version 2.2.5-161.
Is it really a i686 glibc? This sounds like the i586 one is installed, because there is no 2.2.5-161 for i686.
Yes, it is a i586 package. I don't see it written with rpm -qi but I have a backup of all the updates and the name of the package file is clear: glibc-2.2.5-161.i586.rpm.
Sorry to repeat it, but I don't see how YOU could install -164, as it is not visible (no patch file for it in the "patches" directory).
YOU know it.
Who do you mean, me or YaST2? ;-) Then I may learn something new. I thought YOU read the "patches" directory to know which RPM to upgrade. It looks like this hasn't changed in 8.1, as YOU displays only the RPM packages for which there is patch file (not a patch.rpm, I mean). Hold on, I'm sure we'll understand each other in two or three mails. ;-) - -- Thibaut Cousin E-mail : cousin@in2p3.fr Web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE906jHv1vqsTa1E4oRAhggAJ9fANuXGqAj0Q0dObhbABT2gFknAgCdEQQS RwP2Bq4AyWuqDWo9anY9TCk= =lw7U -----END PGP SIGNATURE-----
On Thu, Nov 14, Thibaut Cousin wrote:
Sorry to repeat it, but I don't see how YOU could install -164, as it is not visible (no patch file for it in the "patches" directory).
YOU know it.
Who do you mean, me or YaST2? ;-)
YOU -> YaST2 online update.
Then I may learn something new. I thought YOU read the "patches" directory to know which RPM to upgrade. It looks like this hasn't changed in 8.1, as YOU displays only the RPM packages for which there is patch file (not a patch.rpm, I mean). Hold on, I'm sure we'll understand each other in two or three mails. ;-)
But YOU also knows for which architecture the current package is, and prefers the right architecture. If a i686 glibc is installed, YOU will install the glibc from the i686 directory, else the i586 one (this is the reason for the symlinks in this directories). Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de SuSE Linux AG Deutschherrnstr. 15-19 D-90429 Nuernberg -------------------------------------------------------------------- Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Jeudi 14 Novembre 2002 18:26, Thorsten Kukuk a écrit :
YOU know it.
Who do you mean, me or YaST2? ;-)
YOU -> YaST2 online update.
Yes, I knew it. Sorry, I couldn't resist the bad joke. ;-)
Then I may learn something new. I thought YOU read the "patches" directory to know which RPM to upgrade. It looks like this hasn't changed in 8.1, as YOU displays only the RPM packages for which there is patch file (not a patch.rpm, I mean). Hold on, I'm sure we'll understand each other in two or three mails. ;-)
But YOU also knows for which architecture the current package is, and prefers the right architecture. If a i686 glibc is installed, YOU will install the glibc from the i686 directory, else the i586 one (this is the reason for the symlinks in this directories).
You mean that during install I had a i586 glibc installed (from the CDs), so YOU updated only with i586 packages? OK, I understand that. Anyway, I'm happy that YOU didn't use the i686 package, as it has many problems (previously mentioned, with Mozilla and JBuilder, as far as I know). Thanks! - -- Thibaut Cousin E-mail : cousin@in2p3.fr Web : http://clrwww.in2p3.fr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE909/9v1vqsTa1E4oRApGtAJ9RBhfBLCAKNMpi/cTY19ilCFVqgwCguPuX rZ78aqE+OB1mpuXVsaJH2OI= =1ltB -----END PGP SIGNATURE-----
To fix the problem upgrade to Mozilla 1.1 and have glibc 2.2.5.164 Mozilla 1.1 can be found at ftp.suse.com/pub/projects/mozilla I uninstalled mozilla 1.0.1 before upgrading. It complained about breaking evolution (if you use it) if I uninstalled mozilla 1.0.1, but I uninstalled it anyway, and uninstalled evolution, also (since the 1.2 version of evolution was released, and I planned on updating that too). After installing SuSE version of mozilla, I went to xiaman.com and installed evolution 1.2 using red-carpet installer. (It fixed the spell check and palm sync in evolution too ;^) That fixed lots of my problems. -Jeric
participants (7)
-
Anders Johansson -
Curtis Rey -
Jeric -
Konstantin (Kastus) Shchuka -
Radule Soskic -
Thibaut Cousin -
Thorsten Kukuk