(*** This bug was imported into bugs.kde.org ***) Package: kdevelop Version: KDE 2.2.2 Severity: normal Installed from: RedHat RPMs Compiler: g++ 2.9.5?? OS: Linux OS/Compiler notes: Using semi-modified Red 7.2 OS on Dual Pentium Xeon with Rational Clearcase 4.x I'm wondering if you have had trouble with Rational's Clearcase version 4.1 on Red Hat Linux 7.2 when trying to the the KDE applications (KDevelop Kate KWord etc). I'm trying to use the clearcase command: "ct setview=joe" to attach to my Clearcase View for software development. Once I attach to my Clearcase View I can no longer use the File/Open Dialog in the KDE applications. I start one of the applications (Kdevelop specifically) and then do a File/Open. The application hangs for about 10-20 seconds and then I get the following error: "The process for the file protocol died unexpectedly". I then can no longer interact with the dialog. If I do not attach to my clearcase view then everything works as expected. Here is my machine info: OS: Red Had Linux 7.2 KDE: 2.2.2 Qt lib: 2.3.1 CPU: Hewlett Packard Dual P4 Xeon 1.8ghz 2GB Memory Fire GL 4 graphics card. I have narrowed down the problem to the one step above (removing any changes to my LD_LIBRARY_PATH and PATH variables thinking that those may be causing it). I do know that Clearcase seems to be causing a problem with the "df -k" application on linux so it might be related to that. If you have any suggestions or solutions please email them to me directly (mailto:Joe.Longson@disney.com) If nothing else could you tell me the basics of what the file/open dialog is doing when it is starting up. (ie what libraries it interacts with what system calls it makes etc) That would greatly help me in my debugging. Thanks in advance Joe Longson Senior Software Engineer Walt Disney Feature Animation (Submitted via bugs.kde.org)
Hello, is this still a problem with KDE-3.x? I don't use clearcase, so I don't know how to check this myself. What does clearcase do that could possibly lead to trouble with df ?? Does it mount partitions (or pseudo-partitions like /proc) ? Has this been reported to the clearcase people? To answer your question, the file dialog (well the "file protocol implementation", kio_file, more precisely) is basically using the usual system calls to list the contents of a directory - much like "ls" would do. However it might also check whether the dir is really local or NFS-mounted, using something like df (not df itself, but the same system calls), so if df hangs, this could explain why the KDE application hangs too...
Subject: Re: file protocol died unexpectedly, rational clearcase Hi, Actually, it is a problem still. However, it is an issue with the way that Rational clearcase does it's filesystem mapping. It's really obnoxious, and I have reported the bug to them. However, nothing has been done about it yet.. joe David Faure wrote: >------- You are receiving this mail because: ------- >You reported the bug, or are watching the reporter. > >http://bugs.kde.org/show_bug.cgi?id=39899 > > > > >------- Additional Comments From faure@kde.org 2003-03-28 15:00 ------- >Hello, > >is this still a problem with KDE-3.x? >I don't use clearcase, so I don't know how to check this myself. >What does clearcase do that could possibly lead to trouble with df ?? >Does it mount partitions (or pseudo-partitions like /proc) ? >Has this been reported to the clearcase people? > >To answer your question, the file dialog (well the "file protocol implementation", kio_file, >more precisely) is basically using the usual system calls to list the contents of a >directory - much like "ls" would do. However it might also check whether the dir is really >local or NFS-mounted, using something like df (not df itself, but the same system calls), >so if df hangs, this could explain why the KDE application hangs too... > >
Subject: Re: file protocol died unexpectedly, rational clearcase On Monday 31 March 2003 18:45, you wrote: > However, it is an issue with the way > that Rational clearcase does it's filesystem mapping. I'm afraid it's no KDE bug then.