Bug 5123

Summary:	shading/focus bug in latest mutter/gnome-shell
Product:	Mageia	Reporter:	Herbert Poetzl <herbert>
Component:	RPM Packages	Assignee:	Olav Vitters <olav>
Status:	RESOLVED OLD	QA Contact:
Severity:	major
Priority:	High	CC:	herbert, marja11
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	mutter-3.4.0-1/gnome-shell-3.4.0-4	CVE:
Status comment:

Description Herbert Poetzl 2012-03-27 01:23:41 CEST

Description of problem:
when shading (rolling up) a window on one workspace and moving the focus away to a different window, then switching the workspace will disable the shaded and inactive window permanently.

one way (workaround) to regain control of that window is to enter the 'Activity Overview' and explicitely clicking on the shaded window title bar.

Version-Release number of selected component (if applicable):
mutter-3.3.92-1.mga2.x86_64

How reproducible:
always

Steps to Reproduce:
1. open terminal on desktop 1 and 2, and a web browser on desktop 2
2. shade terminal window on desktop 2
3. move focus to the web browser by clicking on it
4. switch to desktop 1 and back to desktop 2
5. try to unshade the terminal window

Comment 1 Herbert Poetzl 2012-04-07 02:02:22 CEST

believe it or not, this issue just got worse :)

in latest Cauldron, shading a window on one desktop, then moving away to another desktop and returning makes the shaded window disappear!
it can be recovered as described above.

Priority: Normal => High
CC: (none) => herbert
Source RPM: mutter-3.3.92-1.mga2.src.rpm => mutter-3.4.0-1/gnome-shell-3.4.0-4
Severity: normal => major

Manuel Hiebel 2012-04-07 21:26:23 CEST

Assignee: bugsquad => olav

Comment 2 Marja Van Waes 2012-05-26 13:05:35 CEST

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 3 Marja Van Waes 2012-07-06 15:06:07 CEST

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

Comment 4 Marja Van Waes 2012-08-03 20:13:14 CEST

2x no reply, closing as old

Feel free to reopen if needed and tell in which fully updated Mageia version(s) you still have this issue

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD