[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: Serious DCOP problem.
From: Waldo Bastian <bastian () kde ! org>
Date: 2000-12-20 21:15:31
[Download RAW message or body]
On Wednesday 20 December 2000 11:49, rik@kde.org wrote:
> #if Waldo Bastian
>
> > knotify did a system("aplay somefile") and got stuck on that for some
> > reason. As a result knotify didn't handle incoming DCOP request any more.
> > This caused the DCOP server to lock up on a write() call as part of a
> > ICESendMessage (probably after it's buffer filled up with other
> > requests). Result: a total lockup of the desktop.
>
> I would guess that knotify waits for aplay to return. If aplay can't
> grab the audio device, I think it blocks. So knotify could just start
> aplay and not wait for it to finish, if that's how it works.
Sure, knotify needs to be fixed as well, but I shouldn't need to loose my
work in kpresenter because of a bug in knotify. knotify will not be the last
application with a bug :-]
Which reminds me that it might also be helpfully if applications would be
able to survive a crash of the dcopserver.
Cheers,
Waldo
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic