Re: Unable to create io-slave: unknown protocol file
No, I don't have a partial woody. But the dist-upgrade was some time ago. Maybe I should do one again, are the perl 5.6 problems solved? As far as I know, the perl problems are woody-only, so a dist-upgrade from stable shouldn't introduce this problem. The thing that is really weird, is that it worked as soon I reverted from kernel-2.4.0-test12 to kernel-2.2.17. The packages for kde 2.0.1 were working flawlessly with the 2.4.0-testXX kernel series. I'm not a programmer and don't know a whole lot about io-slave processes, but I do know the the 2.4 series of kernels has a completely different IP stack system. This might be the root of your problem. I know when I did a dist-upgrade on a gateway PC from slink to potato and it killed all the network stuff because it didn't update the kernel, or didn't update the packages, I'm not sure which. I just replaced the system with SmoothWall which is far superior to what I had put together myself. I'd recommend going back to the 2.4 series kernel. it should be ready for release any year now : ). Cheers, John Gay
Re: Unable to create io-slave: unknown protocol file
Am Sunday 17 December 2000 13:27 schrieb Ivan E. Moore II: > > No, I don't have a partial woody. But the dist-upgrade was some time > > ago. Maybe I should do one again, are the perl 5.6 problems solved? > > I'm not even suggesting you upgrade to woody. :) > > All I was saying is the person who was having the problem had a mixed > woody/ potato install. > > but yes, you should make sure you have the latest packages (potato if your > running potato) > > > The thing that is really weird, is that it worked as soon I reverted from > > kernel-2.4.0-test12 to kernel-2.2.17. > > The packages for kde 2.0.1 were working flawlessly with the 2.4.0-testXX > > kernel series. > > weird...I run 2.4.0-testxx on all my machines... No, I'm already running woody, XFree4 was the driving force to do a dist-upgrade in October :) I'll do a dist-upgrade again, maybe it is an weird issue with glibc2.2. Btw: Thanks for providing KDE packages. Great work! WfG, Chris
Re: Unable to create io-slave: unknown protocol file
> No, I don't have a partial woody. But the dist-upgrade was some time > ago. Maybe I should do one again, are the perl 5.6 problems solved? I'm not even suggesting you upgrade to woody. :) All I was saying is the person who was having the problem had a mixed woody/ potato install. but yes, you should make sure you have the latest packages (potato if your running potato) > The thing that is really weird, is that it worked as soon I reverted from > kernel-2.4.0-test12 to kernel-2.2.17. > The packages for kde 2.0.1 were working flawlessly with the 2.4.0-testXX > kernel series. weird...I run 2.4.0-testxx on all my machines... -- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
Re: Unable to create io-slave: unknown protocol file
Am Sunday 17 December 2000 02:07 schrieb Ivan E. Moore II: > On Sat, Dec 16, 2000 at 03:27:38PM +0100, [EMAIL PROTECTED] wrote: > > Hi, > > > > The latest kdebase (2.1) packages I tried the one from 13.12.2000 and > > 14.12.2000 seem to be broken. Klauncher is unable to start any io-slave > > and complains about not finding any mime-type on startup. > > > > In the kde mailinglist archive David Faure suggested to run kbuildsycoca. > > Running kbuildsycoca from within the kde2 script helped against the > > mime-type errors, but not against the unability to find slaves. > > > > There is already a bug report about this problem on woody, so I think > > I'm not alone. > > that bug report is for a system that is part potato and part woody. > > The problem is that I have not seen any problems like this so far...and > unless you have a part potato and part woody install then all we have so > far is 2 unique instances that are similar. > > Ivan No, I don't have a partial woody. But the dist-upgrade was some time ago. Maybe I should do one again, are the perl 5.6 problems solved? The thing that is really weird, is that it worked as soon I reverted from kernel-2.4.0-test12 to kernel-2.2.17. The packages for kde 2.0.1 were working flawlessly with the 2.4.0-testXX kernel series. WfG, Chris
Re: Unable to create io-slave: unknown protocol file
On Sat, Dec 16, 2000 at 03:27:38PM +0100, [EMAIL PROTECTED] wrote: > Hi, > > The latest kdebase (2.1) packages I tried the one from 13.12.2000 and > 14.12.2000 seem to be broken. Klauncher is unable to start any io-slave and > complains about not finding any mime-type on startup. > > In the kde mailinglist archive David Faure suggested to run kbuildsycoca. > Running kbuildsycoca from within the kde2 script helped against the > mime-type errors, but not against the unability to find slaves. > > There is already a bug report about this problem on woody, so I think > I'm not alone. that bug report is for a system that is part potato and part woody. The problem is that I have not seen any problems like this so far...and unless you have a part potato and part woody install then all we have so far is 2 unique instances that are similar. Ivan -- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
