Bug 382224 - GNOME : intermittent problem moving and maximizing windows
Summary: GNOME : intermittent problem moving and maximizing windows
Status: RESOLVED DUPLICATE of bug 343858
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Factory
Hardware: Other Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-22 08:12 UTC by Willem Meens
Modified: 2008-04-22 08:36 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Willem Meens 2008-04-22 08:12:34 UTC
I'm having issues with Alpha3 and Beta1 using GNOME.

There is an intermittent problem with moving and maximizing windows.
Also sometimes the windows borders disappear (happened twice). This was usig 2D mode.

Symptoms;
1) When first opening a window it appears in the left top, when maximizing that window it maximizes to only a portion of the screen.
Un-maximizing it, moving the window to the right a bit and maximizing again brings it to full proportion (normal). Other windows do not seem affected? It look a bit as if the window itslef is opend in 800x600 resulotion and maximizes to this. Moving the window snaps it to the 1400x1050 working resolution?? 

2) Opening a window all works fine (menus and content) but the window cannot be moved. When this happens it then seems to effect all windows.


Logging out and back in again so far resolves the issues but then randomly it can pop up again?

May be of interest : I'm using an Intel 945GM chipset and as note the general feel is more sluggish then with 10.3 on the same hardware. I've applied the sound engine bug resolution.

Not sure where to look for this?  Any logs I can specifically have a look in?

thanks,
 Wj
Comment 1 Magnus Boman 2008-04-22 08:36:46 UTC

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