[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde
Subject:    Re: Lockup in KDE
From:       "Robert E. Parrott" <rep () fluent ! com>
Date:       1999-08-13 13:54:39
[Download RAW message or body]

I believe that kde1.1.2 needs QT 2.0.


rob

wsuetholz@centonline.com wrote:

> I also have some stability issues with KFM, but, you don't have to reset X to
> clear them up..
>
> What I do, is kill off any kfm processes, and restart them from either another
> VT, or an XTerm, JUST kfm.  The one problem, is all the debug output that gets
> written out to the terminal, so you have to redirect that somewhere.
>
> KFM will lock, randomly, AND if you go to a non-existant URL.
>
> Something that hasn't been really mentioned by anybody yet...  I am using
> KDE version 1.1.1 and QT 1.42 compiled using egcs 2.91.57.
>
> Soon I'm going to be updating to QT1.44 and KDE version 1.1.2.  I might even do
> a pre-release version of 1.1.2.  I have also tried to get the KDE 2.0 versions
> to work, but, no luck there.  I'd really like to see koffice.  Don't really care
> much about themes.
>
> Bill Suetholz
>
> On 13-Aug-99 CLIFFORD ILKAY wrote:
> > Hi Rob,
> >
> > I run Mandrake 6 on a dual P2/333 Intel Dakota motherboard system. I too
> > experience the lock up problem described by Doug Young when I use KDE. It
> > has nothing to do with Netscape as far as I can determine. It is a random
> > and non-reproducible event. The event that seem to cause the system to
> > become unresponsive is clicking on a folder to browse its contents in kfm.
> > When this happens, all instances of kfm are hung. If I switch to another
> > virtual desktop and flip back to the desktop with the hung kfm window, the
> > kfm window will not redraw properly. In fact, all the icons on the desktop
> > change to black blobs. The way that I deal with this is to use the
> > Control-Alt-Backspace sequence to bail out of X to the shell prompt.
> > Attempting to startx will cause the X server to crash so I use
> > Xconfigurator to configure X and then do a startx. I could run for a week
> > without a hitch and I could have this happen four times a day. There is no
> > discernible pattern. I have experienced this on more than one system so it
> > rules out hardware.
> --
> Send posts to:  kde@lists.netcentral.net
>  Send all commands to:  kde-request@lists.netcentral.net
>   Put your command in the SUBJECT of the message:
>    "subscribe", "unsubscribe", "set digest on", or "set digest off"
> PLEASE READ THE ARCHIVED MESSAGES AT http://lists.kde.org/ BEFORE POSTING
> **********************************************************************
> This list is from your pals at NetCentral <http://www.netcentral.net/>

-- 
Send posts to:  kde@lists.netcentral.net
 Send all commands to:  kde-request@lists.netcentral.net
  Put your command in the SUBJECT of the message:
   "subscribe", "unsubscribe", "set digest on", or "set digest off"
PLEASE READ THE ARCHIVED MESSAGES AT http://lists.kde.org/ BEFORE POSTING
**********************************************************************
This list is from your pals at NetCentral <http://www.netcentral.net/>

[prev in list] [next in list] [prev in thread] [next in thread]