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 337870 - Minimizing windows causes havoc, but to certains apps only
Minimizing windows causes havoc, but to certains apps only
Status: RESOLVED DUPLICATE of bug 337868
Product: metacity
Classification: Other
Component: general
2.14.x
Other All
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2006-04-09 23:33 UTC by cruiseoveride
Modified: 2006-04-10 16:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description cruiseoveride 2006-04-09 23:33:47 UTC
Please describe the problem:
This was not a problem with 2.12x
I am running two screens, as seperate desktops.
When trying to minimize a window, from either screen, metacity looses control of
all window borders and desktops, bringing all applications together in one
desktop, for a few seconds, then returns control to apps, without minimizing the
original app.
This happens while trying to minimize kde apps, xmms, valknut,
This does not happen to gaim, evolution, nautilus etc...

Steps to reproduce:
1. Open xmms for example.
2. Click minimize button on xmms
3. BAM, all windows flash together on one screen, without any borders, then
returns back to normal in a few seconds.


Actual results:


Expected results:


Does this happen every time?
Yes

Other information:
 rpm -q xmms
xmms-1.2.10-22.fc5
 cat /etc/redhat-release
Fedora Core release 5 (Bordeaux)
NOTE; This is not an issue with gnome-2.12x
Comment 1 Luca Cavalli 2006-04-10 08:40:19 UTC

*** This bug has been marked as a duplicate of 337868 ***
Comment 2 Elijah Newren 2006-04-10 15:16:24 UTC
Luca: I marked this bug as a duplicate of 337868 about 9 hours prior to you (check bug 337868 comment 1).  Did you just have it open in a browser window for that long, mark the duplicate, and then get a mid-air collision and choose to submit the changes anyway?  I'm just wondering how my "has been marked as a duplicate" message disappeared.  It seems to have happened in a couple other cases too, and I'm wondering if there's a bugzilla bug.

Thanks in advance for any info...
Comment 3 Elijah Newren 2006-04-10 15:17:37 UTC
Nevermind, I didn't realize that there was yet another duplicate -- I guess I didn't check bug numbers all that closely.

Sorry for the spam.
Comment 4 Ray Strode [halfline] 2006-04-10 16:13:10 UTC
It would be good if bugzilla added a unique token to every request so that when people bookmark process_bug.cgi or whatever causes dupes like this, that they wouldn't work.