Review Request: Hacky workaround for https://bugs.kde.org/show_bug.cgi?id=228005

[Lamarque Vieira Souza]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/103593/#review9556
-----------------------------------------------------------



ksmserver/shutdown.cpp
<http://git.reviewboard.kde.org/r/103593/#comment7815>

    As long as ksmserver is not multi-threaded the race will not cause problems because logoutSoundFinished slot returns if state is different from WaitingForKNotify and the last thing logoutSoundFinished slot does is call startKilling, which changes the state. The second logoutSoundFinished signal will test the state in logoutSoundFinished slot and return.


- Lamarque Vieira Souza


On Dec. 31, 2011, 3:16 a.m., Peter OGorman wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/103593/
> -----------------------------------------------------------
> 
> (Updated Dec. 31, 2011, 3:16 a.m.)
> 
> 
> Review request for KDE Runtime.
> 
> 
> Description
> -------
> 
> https://bugs.kde.org/show_bug.cgi?id=228005
> if sound is not working for some reason (e.g. no phonon
> backends are installed) the closed() signal never happens
> and logoutSoundFinished() never gets called. This hack
> makes sure that logout still occurs. Of course, on systems
> with working sound there's a race.
> 
> 
> Diffs
> -----
> 
>   ksmserver/shutdown.cpp 7fd1e11 
> 
> Diff: http://git.reviewboard.kde.org/r/103593/diff/diff
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Peter OGorman
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20120104/9daed1e1/attachment.htm>