Version: (using KDE KDE 3.4.0) Installed from: RedHat RPMs OS: Linux Operating system : RedHat EL WS 3.0 ( Taroon Update 2 ) KDE VERSION: KDE 3.4.0 gcc version: 3.2.3 20030502 Hi Iam running a UML application ( Umbrello ) on KDE 3.4.0. The application opens fine and is able to open header files also. After setting up clear case ( Rational software ) views, the application is not able to open the header files( it does not display the header files under a particular directory which it was able to before setting up the clear case views) and throws the following error. #################################################################################### kio (KSycoca): Trying to open ksycoca from /var/tmp/kdecache-x00cmagi/ksycoca kio (KSycoca): Could not open ksycoca kio (KSycoca): Trying to open ksycoca from /var/tmp/kdecache-x00cmagi/ksycoca kio (KSycoca): Could not open ksycoca kdecore (KSocket): WARNING: Error listening on socket: -1 kio (Slave): slave failed to connect to application pid=12848 protocol=file kio (Slave): Houston, we lost our slave, pid=12848 kio (Slave): slave died pid = 12848 kio (KDirListerCache): [void KDirListerCache::slotResult (KIO::Job *)] finished listing file:///user/x00cmagi kio (KDirLister): [void KDirLister::stop ()] kio (KDirListerCache): [void KDirListerCache::stop (KDirLister *)] lister: 0x84d2be0 kio (KDirLister): -KDirLister kio (KDirLister): [void KDirLister::stop ()] kio (KDirListerCache): [void KDirListerCache::stop (KDirLister *)] lister: 0x84d2be0 kio (KDirListerCache): [void KDirListerCache::forgetDirs (KDirLister *)] 0x84d2be0 kio (KDirListerCache): [void KDirListerCache::forgetDirs (KDirLister *, const KURL &, bool)] 0x84d2be0 _url: file:///user/x00cmagi kio (KDirWatch): Cancelled FAM (Req 1) for /user/x00cmagi kio (KDirWatch): Removed Dir /user/x00cmagi [KDirWatch-1] kio (KDirWatch): KDirWatch deleted (FAM closed) kio (KDirListerCache): -KDirListerCache ####################################################################################### Iam more interested towards the following lines from the above error messages. kdecore (KSocket): WARNING: Error listening on socket: -1 kio (Slave): slave failed to connect to application pid=12848 protocol=file kio (Slave): Houston, we lost our slave, pid=12848 kio (Slave): slave died pid = 12848 kio (KDirListerCache): [void KDirListerCache::slotResult (KIO::Job *)] finished listing Pl let me know if it's something to do with conflicts on the ports used by clear case and kde. TIA Balaji.k
What are you trying to do? It is really not clear what you are talking about? Are the files you want to load on a network share? Where do you set up clearcase, on the same station? Is clearcase running on Linux?
Hi Thanks for the reply. Iam running a UML Modeller application "Umbrello" on the linux workstation. The application is installed on a network share . clearcase is setup on the same station and it's running on linux. Problem is: Before setting up the clear case views, everything works fine i.e the KDE dialog box to open files displays all the files. After I set up the clear case views i.e after I invoke the clear case shell, the dialog box doesn't show the files present and throws error saying " file protocol died unexpectedly". The .xsession_errors throws the errors I have pasted below. ########################################################## kdecore (KSocket): WARNING: Error listening on socket: -1 kio (Slave): slave failed to connect to application pid=12848 protocol=file kio (Slave): Houston, we lost our slave, pid=12848 kio (Slave): slave died pid = 12848 kio (KDirListerCache): [void KDirListerCache::slotResult (KIO::Job *)] finished listing ########################################################### Pl let me know if it was clear or I could give you more clear info. Thanks Balaji.k
Dear all Any further inputs required?
Balaji Krishnamoorthy <meetbaji@yahoo.com> [050629 13:06]: > Thanks for the reply. Iam running a UML Modeller application "Umbrello" on > the linux workstation. The application is installed on a network share . > clearcase is setup on the same station and it's running on linux. > > Problem is: Before setting up the clear case views, everything works fine > i.e the KDE dialog box to open files displays all the files. > > After I set up the clear case views i.e after I invoke the clear case > shell, the dialog box doesn't show the files present and throws error > saying " file protocol died unexpectedly". > > The .xsession_errors throws the errors I have pasted below. > > ########################################################## > kdecore (KSocket): WARNING: Error listening on socket: -1 > kio (Slave): slave failed to connect to application pid=12848 protocol=file > kio (Slave): Houston, we lost our slave, pid=12848 > kio (Slave): slave died pid = 12848 > kio (KDirListerCache): [void KDirListerCache::slotResult (KIO::Job *)] finished listing > ########################################################### > Pl let me know if it was clear or I could give you more clear info. I'm really not sure, if this is related to Umbrello. As you said without installing clear case everything works fine. After you installed clear case something is messed up. I think the clear case people are providing some kind of support, so I would call them. Sebastian
Sebastian Thanks much for your help. It's true that clear case messes up. I checked out the changes in env before and after invoking clearcase but couldn't find much useful. Iam digging into that more. pl let me know if clear case could get you some inputs. Thanks again
At http://people.fruitsalad.org/phil/kde/userguide-tng/environment-variables.html I see the following: $KDE_FORK_SLAVES (KDE 3.2.3) Set this variable to spawn KIO-slaves directly from the application process itself, by default KIO-slaves are spawned using klauncher/kdeinit. This option is useful if the KIO-slave should run in the same environment as the application, this can be the case with Clearcase.
Hi Oliver/Sebastian Thanks for your time on this. I"ll try your suggestions soon as the test environment is not available and get back to you. Thanks again
Please reopen if need be.