Am Sa, den 30.07.2005 schrieb neidorff um 20:21:
Holy moley! I ran strace as you suggested, but I couldn't find anything pointing at the error. I've attached kmail.log to this message. Would you please be so kind as to take a look at it for me? (sorry it is a large-ish file)
Mark
I do not see an error in the strace log either. But the error occured during stracing?
Is SElinux active on your host? Please check /var/log/messages for audit / avc messages. One google hit speaks about something wrong with kdeinit. You could try and booting with "enforcing=0" as kernel parameter to test with SELinux in permissive mode. If that bring us not a step further, then create a new user and check whether with this one running Kmail the same happens. You can delete this test user and his files after the test run.
Alexander
On 7/30/05, Alexander Dalloz ad+lists@uni-x.org wrote:
Am Sa, den 30.07.2005 schrieb neidorff um 20:21:
Holy moley! I ran strace as you suggested, but I couldn't find anything pointing at the error. I've attached kmail.log to this message. Would you please be so kind as to take a look at it for me? (sorry it is a large-ish file)
Mark
I do not see an error in the strace log either. But the error occured during stracing?
Is SElinux active on your host? Please check /var/log/messages for audit / avc messages. One google hit speaks about something wrong with kdeinit. You could try and booting with "enforcing=0" as kernel parameter to test with SELinux in permissive mode. If that bring us not a step further, then create a new user and check whether with this one running Kmail the same happens. You can delete this test user and his files after the test run.
Yes, the error occurred during stracing. Strange thing, I straced twice with different log files. The first time I made the error happen once. The second time I made the error happen numerous times. Both times the log file was the same size and number of lines.
Anyway, I have SElinux disabled. Will booting with "enforcing=0" tell me anything?
There is an audit message which comes up on boot: Jul 29 10:20:41 neidorff kernel: audit: initializing netlink socket (disabled) Jul 29 10:20:41 neidorff kernel: audit: initializing netlink socket (disabled) Jul 29 10:20:41 neidorff kernel: audit(1122632103.538:0): initialized Jul 29 10:20:41 neidorff kernel: audit(1122632103.538:0): initialized I don't know if this is relavent or not.
I tried an existing user who had not logged in before. Started kmail and created the user's account. Same problem.
I'm going to try the reboot with enforcing...
On 7/30/05, neidorff neidorff@gmail.com wrote:
On 7/30/05, Alexander Dalloz ad+lists@uni-x.org wrote:
Am Sa, den 30.07.2005 schrieb neidorff um 20:21:
Holy moley! I ran strace as you suggested, but I couldn't find anything pointing at the error. I've attached kmail.log to this message. Would you please be so kind as to take a look at it for me? (sorry it is a large-ish file)
Mark
I do not see an error in the strace log either. But the error occured during stracing?
Is SElinux active on your host? Please check /var/log/messages for audit / avc messages. One google hit speaks about something wrong with kdeinit. You could try and booting with "enforcing=0" as kernel parameter to test with SELinux in permissive mode. If that bring us not a step further, then create a new user and check whether with this one running Kmail the same happens. You can delete this test user and his files after the test run.
Yes, the error occurred during stracing. Strange thing, I straced twice with different log files. The first time I made the error happen once. The second time I made the error happen numerous times. Both times the log file was the same size and number of lines.
Anyway, I have SElinux disabled. Will booting with "enforcing=0" tell me anything?
There is an audit message which comes up on boot: Jul 29 10:20:41 neidorff kernel: audit: initializing netlink socket (disabled) Jul 29 10:20:41 neidorff kernel: audit: initializing netlink socket (disabled) Jul 29 10:20:41 neidorff kernel: audit(1122632103.538:0): initialized Jul 29 10:20:41 neidorff kernel: audit(1122632103.538:0): initialized I don't know if this is relavent or not.
I tried an existing user who had not logged in before. Started kmail and created the user's account. Same problem.
I'm going to try the reboot with enforcing...
Rebooting with enforcing did not change kmail's behavior. Neither did adding a new user and configuring that user's account. I also tried downgrading kdenetwork and kdenetwork-devel to 3.3.1-3.1 (previous version) but that didn't fix the problem either.
Mark
On Sunday 31 July 2005 09:28, neidorff wrote:
Rebooting with enforcing did not change kmail's behavior. Neither did adding a new user and configuring that user's account. I also tried downgrading kdenetwork and kdenetwork-devel to 3.3.1-3.1 (previous version) but that didn't fix the problem either.
If starting KMail from the command line shows an error message like:
kmail: ERROR: : couldn't create slave : Unable to create io-slave: klauncher said: Error loading 'kio_pop3'.
You might find this link of interest:
http://bugs.kde.org/show_bug.cgi?id=104627
Regards, Mike Klinke
On 7/31/05, Mike Klinke lsomike@futzin.com wrote:
On Sunday 31 July 2005 09:28, neidorff wrote:
Rebooting with enforcing did not change kmail's behavior. Neither did adding a new user and configuring that user's account. I also tried downgrading kdenetwork and kdenetwork-devel to 3.3.1-3.1 (previous version) but that didn't fix the problem either.
If starting KMail from the command line shows an error message like:
kmail: ERROR: : couldn't create slave : Unable to create io-slave: klauncher said: Error loading 'kio_pop3'.
You might find this link of interest:
AhHa???? There is no kio_pop3 on my system!!!! Is that the problem, or does fedora core 3 have something else to do the job? If it is indeed missing, what do I install to get it?
This feels promising. Thanks,
Mark
On Sunday 31 July 2005 14:25, neidorff wrote:
AhHa???? There is no kio_pop3 on my system!!!!
You should have.
#locate kio_pop3 /usr/lib/kde3/kio_pop3.la /usr/lib/kde3/kio_pop3.so
# rpm -q --whatprovides /usr/lib/kde3/kio_pop3.la kdebase-3.3.1-4.3.FC3 # rpm -q --whatprovides /usr/lib/kde3/kio_pop3.so kdebase-3.3.1-4.3.FC3
Is that the problem, or does fedora core 3 have something else to do the job? If it is indeed missing, what do I install to get it?
This feels promising.
Well, I'm not sure exactly, just ran into this and it looked like your symptoms on the associated bug ( Bug 104947 has been marked as a duplicate of this bug. ).
Also, it seems that one or two others have had this problem like you and for some reason installing cyrus-sasl cured the problem.
Regards, Mike Klinke
On 7/31/05, Mike Klinke lsomike@futzin.com wrote:
Well, I'm not sure exactly, just ran into this and it looked like your symptoms on the associated bug ( Bug 104947 has been marked as a duplicate of this bug. ).
Also, it seems that one or two others have had this problem like you and for some reason installing cyrus-sasl cured the problem.
Thanks Mike,
I found that these are in kdebase also. (They are not on my system. There was a disk "problem" which involved a major fsck session. That may have been when they got lost) Do you know how to just install these two files from the rpm (which I have downloaded already)?
Mark
On Sunday 31 July 2005 15:22, neidorff wrote:
I found that these are in kdebase also. (They are not on my system. There was a disk "problem" which involved a major fsck session. That may have been when they got lost) Do you know how to just install these two files from the rpm (which I have downloaded already)?
Mark
I'd give:
rpm -ivh --replacepkgs kdebase-<your-matching-version>FC3.i386.rpm
a try. It'll replace all files in the package including those that have gone missing.
Regards, Mike Klinke
We can mark this one solved!!! Many thanks to all who helped!
Mark
-
Alexander Dalloz -
Mike Klinke -
neidorff