Bug 669354

Summary: kwin wrongly detects application hanging because of 64bit timetamp issue
Product: Red Hat Enterprise Linux 5 Reporter: Olivier Fourdan <ofourdan>
Component: kdebaseAssignee: Than Ngo <than>
Status: CLOSED ERRATA QA Contact: desktop-bugs <desktop-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 5.5CC: kem, pknirsch, vbenes, vhumpa
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: kdebase-3.5.4-26 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-20 07:21:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 743405    
Attachments:
Description Flags
Proposed patc hfrom upstream commit 652600 none

Description Olivier Fourdan 2011-01-13 13:15:32 UTC 
Created attachment 473314 [details]
Proposed patc hfrom upstream commit 652600

Description of problem:

When attempting to close an application, kwin may falsely detect that the application is not responding and display the "Window is not responding. This window belongs to application Application (PID = ####, hostname = localhost). Do you wish to terminate this application? (All unsaved data in this application will be lost.)"

Version-Release number of selected component (if applicable):

kdebase-3.5.4-20.el5

How reproducible:

Always

Steps to Reproduce:
1. Reproducible on 64bits systems only
2. Set date to 12/17/2010
3. Try to close a window using the [X] button in the window manager
  
Actual results:

  "Window is not responding. 

  This window belongs to application Application (PID = ####, hostname = localhost). Do you wish to terminate this application? (All unsaved data in this application will be lost.)"

Expected results:

No "app not responding" dialog is displayed unless the applicationm is really not responding.

Additional info:

The Xlib API presents timestamps as longs, but on the server side these are  CARD32, but they still only have 32 bits of data in them.

This is upstream bug 143545 fixed by svn commit 652600

    http://websvn.kde.org/?view=revision&revision=652600

Patch attached.
Comment 13 errata-xmlrpc 2012-08-20 07:21:06 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-1177.html