After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 649264 - Alt+Esc (direct switching) wrong position of highlight border
Alt+Esc (direct switching) wrong position of highlight border
Status: RESOLVED DUPLICATE of bug 637161
Product: gnome-shell
Classification: Core
Component: general
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-05-03 11:10 UTC by Ivan Stojic
Modified: 2011-06-06 16:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Ivan Stojic 2011-05-03 11:10:58 UTC 
When using direct switching (Alt+Esc) only highlight border of first window
(let's call that window WindowA) in Alt+Esc queue is drawn correctly, borders
for rest of windows are drawn with correct sizes but positioned with top left
corner in the position of top left corner of WindowA. See attached image.

This behaviour is reproducible every time.

There are no other graphical issues aside from ocasional flicker during
notification area animation.

GNOME Shell 3.0.1
Distribution: Arch Linux
kernel 2.6.38-ARCH
xf86-video-intel 2.15.0
xorg-server 1.10.1

Machine is Lenovo Thinkpad R500 with integrated Intel GPU (X4500MHD).
Laptop display is not used (turned off in GNOME3 system settings),
external monitor is used instead.
Comment 1 Ivan Stojic 2011-05-03 11:13:23 UTC 
I can't see attached screenshot in bug summary so I uploaded it here:
http://ompldr.org/vOGo5Yg
Comment 2 Petr Janecek 2011-06-06 16:38:01 UTC 
"Switch windows of an app directly" (Alt+F6) has the same issue -- highlight border correctly changes size, but not position.

Fedora 15
gnome-shell-3.0.2-1.fc15.x86_64
Comment 3 Florian Müllner 2011-06-06 16:40:13 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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