Bug 498562

Summary:	Psi 0.12.1 2 windows resize to see room Participants problems in fedora 9
Product:	[Fedora] Fedora	Reporter:	ali <aliahsan81>
Component:	psi	Assignee:	Sven Lankes <sven>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	9	CC:	gauret, j.golderer, mlichvar, sven, tomas.wachtarczyk
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-06-05 19:37:00 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description ali 2009-05-01 05:24:34 UTC

Hi All
In fedora 9,I am facing problem regarding psi room participants,when i enter room i didnt see any room participants then need to resize window to see all currently aviable  participants,Same if any room member left or join room then need to  do window resize to see changes.One very annoying issue if i didn't do resize window CPU usage goes to 100%,I mean psi take all CPU.Some time PSI login out logout it self,Same kind of issue with  list of participants didnt get updated until  window resize.

Comment 1 Sven Lankes 2009-05-26 22:03:43 UTC

I'm unable to reproduce this reliably but I am sometimes able to reproduce.

This feels (no hard facts, unfortunately) like a deeper qt 4.5 issue with psi 0.12.

Upstream has stated that no further development will go into psi 0.12 so we will have to wait for/go with 0.13 to get a proper fix for this.

0.13-rc1 has been released last week and I have a test-build running well that doesn't show the behaviour you have been seeing anymore.

I am going to create f12-packages for 0.13-rc1 this week and if things go well I'll also consider creating f9-f11 packages.

Comment 2 ali 2009-05-27 04:58:07 UTC

Ok thats grate :)

Comment 3 Sven Lankes 2009-06-05 19:37:00 UTC


*** This bug has been marked as a duplicate of bug 497950 ***