Bug 5361 - Gnome-shell confused by multiheaded setup
Summary: Gnome-shell confused by multiheaded setup
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Olav Vitters
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-04-11 22:00 CEST by Herbert Poetzl
Modified: 2012-08-04 14:09 CEST (History)
1 user (show)

See Also:
Source RPM: gnome-shell
CVE:
Status comment:

Attachments
what's wrong with that screenshot? (76.58 KB, image/png)
2012-04-11 22:03 CEST, Herbert Poetzl 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Herbert Poetzl 2012-04-11 22:00:53 CEST 
Description of problem:
when using a multiheaded setup gnome-shell gets easily confused by xrandr changes and makes completely wrong assumptions about sizes and locations.

Version-Release number of selected component (if applicable):
gnome-shell-3.4.0-4.mga2.x86_64

How reproducible:
always

Steps to Reproduce:
1. create a multiheaded setup
2. add/move/remove one or the other display
3.
Comment 1 Herbert Poetzl 2012-04-11 22:03:02 CEST 
Created attachment 1972 [details]
what's wrong with that screenshot?

note that it gets even worse if you rotate a desktop (this is only with remove/add)
Manuel Hiebel 2012-04-12 16:57:31 CEST

Assignee: bugsquad => olav
Source RPM: (none) => gnome-shell

Comment 2 Olav Vitters 2012-04-18 17:21:49 CEST 
I think mutter 3.4.1 has a change that will fix this. Waiting for new Mageia beta to be released until I update.
Comment 3 Marja Van Waes 2012-05-26 13:06:03 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 4 Marja Van Waes 2012-07-06 15:06:27 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 5 Marja Van Waes 2012-08-04 14:09:14 CEST 
2x no reply, closing as old.

Please reopen when needed and tell for which version(s) of Mageia this bug is still valid.

If it is valid for both cauldron and Mageia 2, then please put MGA2TOO on the whiteboard and let version remain set to cauldron

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.