Bug 608

Summary: with some particular settings in systemsettings and konsole maximization system totally hangs.
Product: Mageia Reporter: MichaÅ Walenciak <Kicer86>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED FIXED QA Contact:
Severity: critical    
Priority: Normal CC: anssi.hannula, balcaen.john, bert.ram.aerts, jaanus.ojangu, sebastien.guerin.news
Version: CauldronKeywords: Triaged
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=270308
Whiteboard:
Source RPM: nvidia-current-270.41.06-1.mga1.src.rpm CVE:
Status comment:

Description MichaÅ Walenciak 2011-04-01 09:51:37 CEST
Description of problem:
Since 31 of March I can observe weird issue: if I maximize konsole, system totally hangs. Only Magic SysRq are the salvation (saK doesn't work however) ;)

I've made a small investigation and the problem is in OpenGL settings in Desktop Effects (Advanced tab).
If I set:
Scale method: Smooth
OpenGL mode: shared memory
Vsync to yes
Direct rendering to yes

the problem occurs.
It's hard to say which option is the problem as I tried some combinations and once it worked, sometimes it doesn't.
To be sure, that the konsole maximization won't hang the pc, I've set:
Scale method: Crisp
OpenGL mode: Texture from bitmap
Vsync to no
Direct rendering to no

With those options, it's ok, however while konsole maximization, konsole window blinks ominously ;)

The functionality test were disabled in both cases and suspend desktop effects for fullscreen windows were enabled.


ps. above option names were translated from polish so may differ a little.

How reproducible:
Always if I set proper settings and maximize the konsole window

Steps to Reproduce:
1. Set options in systemsettings as descibed above (desktop effects in general tab must be enabled)
2. Logout (it doesn't "work" without logout)
3. open konsole window and maximize it. System will totaly hang


Reproducible: 

Steps to Reproduce:
Comment 1 Ahmad Samir 2011-04-06 05:46:10 CEST
I suggest you submit this report upstream at https://bugs.kde.org , include info about what graphics card you have and which driver is used.

Keywords: (none) => NEEDINFO

Comment 2 MichaÅ Walenciak 2011-04-07 12:11:14 CEST
https://bugs.kde.org/show_bug.cgi?id=270308 here it is
Ahmad Samir 2011-04-08 01:20:01 CEST

Keywords: NEEDINFO => Triaged
CC: (none) => balcaen.john
See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=270308

Comment 3 John Balcaen 2011-05-06 02:22:51 CEST
According arch linux bugzilla ( https://bugs.archlinux.org/task/23381 ) it seems to be a nvidia bug and they are working on it.

CC: (none) => anssi.hannula
Source RPM: (none) => nvidia-current-270.41.06-1.mga1.src.rpm

Comment 4 John Balcaen 2011-05-20 12:11:48 CEST
*** Bug 1352 has been marked as a duplicate of this bug. ***

CC: (none) => bert.ram.aerts

Sébastien GUERIN 2011-05-20 15:21:47 CEST

CC: (none) => sebastien.guerin.news

Comment 5 John Balcaen 2011-06-08 13:12:58 CEST
*** Bug 1682 has been marked as a duplicate of this bug. ***

CC: (none) => jaanus.ojangu

Comment 6 Ahmad Samir 2011-07-20 17:22:56 CEST
This should be fixed by nvidia-current 275.09.07 (which has been in mga1 nonfree/updates for quite some time).

Closing, reopen if you can still reproduce this issue.

Status: NEW => RESOLVED
Resolution: (none) => FIXED