Description of problem: 1. On an empty GNOME desktop open a gnome-terminal 2. Maximize it 3. Open another gnome-terminal but do not maximize 4. Grab the non-maximized window and see what happens What happens every time for me is that when I move the non-maximized terminal a little bit to the right suddenly the maximized window is un-maximized and it is moved instead of the second terminal! Version-Release number of selected component (if applicable): Fedora 12 Beta + updates as of 2009-11-03 How reproducible: Always.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Very strange sounding behavior. Unfortunately I can't reproduce it. No metacity fixes have gone in in the last two weeks so it is unlikely to be a difference in Metacity version. - By "Grab the non-maximized window" - do you mean by the titlebar? (I've tried both titlebar and alt-click and can't reproduce either way) - Can you reproduce this with anything but gnome-terminal? - Do the two windows have to be of the same application? - Do you notice anything else weird about mousing? Could it be a mouse driver bug of some sort? - 32-bit or 64-bit ?
Thanks for looking into this. To make sure I had not caused this by myself with some strange configuration changes I created a new user, logged in via GDM and still saw this. > - By "Grab the non-maximized window" - do you mean by the titlebar? Yes. When I click the titlebar nothing happens at that point (as expected) but when I move mouse a bit to south-east the maximized window get unmaximized and suddenly it is being moved. > - Can you reproduce this with anything but gnome-terminal? > - Do the two windows have to be of the same application? I could reproduce this with gnome-calculator + gnome-terminal and gnome-calculator + gnome-calculator but not with firefox + gnome-terminal. It happens only when the first thing after opening the second application is to grab it. > - Do you notice anything else weird about mousing? Could it be a mouse driver > bug of some sort? Nope, everything else fine, as has been since FC6 or so with this laptop. > - 32-bit or 64-bit ? 32-bit. I have now Fedora 12 + updates as of 2009-11-19. I will try in another F12 this or next week and will let you know what happens if you can't reproduce this. Thanks.
Actually, while testing, this appeared to dmesg: metacity[6986]: segfault at 69742062 ip 006039e1 sp bff58110 error 6 in libSM.so.6.0.0[602000+7000]
Actually I now see that the segfault always appears after logging in via GDM. I'm already confused, too, but I hope that segfault proves that I'm not on drugs :)
Hmm, still not reproducing Can you attach the output of 'gconftool-2 -R /apps/metacity' to this bug as an attachment? If you create a new user account can you reproduce the problem in that account?
Created attachment 372543 [details] metacity gconf > Can you attach the output of 'gconftool-2 -R /apps/metacity' to this bug as an > attachment? If you create a new user account can you reproduce the problem in > that account? This after I 1) created a new user, 2) logged in via GDM, 3) launched two gnome-terminals and was able to reproduce. I do notice that the gnome-terminals must be freshly started, ie, if I start first one, move it, then maximize, do something, then the second, then try reproducing, all is ok. This means that the initial method to reproduce still is valid: - move to an empty workspace - open a gnome-terminal and maximize if - open another gnome-terminal, notice how it is placed so that titlebars are next to each other - grab the smaller one, move a bit, see how the maximized gnome-terminal magically is unmaximized and moved instead of the second one
(In reply to comment #7) > - move to an empty workspace > - open a gnome-terminal and maximize if > - open another gnome-terminal, notice how it is placed so that titlebars are > next to each other Can you provide a screenshot? - I'm not sure I understand what you mean by "next to each other". Do you have another mouse you can try plugging in? (Since I can't reproduce and you can reproduce with a new user, I'm back to wondering about hardware problems.)
> Can you provide a screenshot? - I'm not sure I understand what you mean by > "next to each other". Sure - I'm attaching two screenshots, one just before starting to move the non-maximized window and and the second which shows how actually the maximized window has been unmaximized and moved instead of the window initially grabbed. I tried now another mouse, same result. All this has been working well on my system since I bought it around FC 6 or so, F12 Beta is the first release where I see this.
Created attachment 373180 [details] a "before" screenshot
Created attachment 373181 [details] an "after" screenshot
Do you know if the metacity that's crashing is gdm's metacity or your user's metacity? If you could hit ctrl-alt-f2, log in to the text console, then run ps -ef | grep metacity > /tmp/gdm-ps-listing.txt logout, then hit ctrl-alt-f1 to get back to the graphical login screen, reproduce the problem and see if the pid in /tmp/gd-ps-listing.txt matches the metacity that crashed, that would be useful information.
> Do you know if the metacity that's crashing is gdm's metacity or > your user's metacity? Just checked - it's gdm's metacity. Would it be helpful if I'd install gdm/metacity debuginfo packages and see if some backtraces would be generated? Thanks.
I confirm the bug. I observe it on my two linux boxes: Fedora 12 i386 (upgraded from Fedora 11) and Fedora 12 x86_64 (clean install). This bug is 100% reproducible on my PCs How to reproduce 1) I use GNOME enviroment 2) I have launchers on top panel: gnome-terminal and gedit 3) Click on the gnome-terminal icon on the panel. Maximize gnome-terminal window. 4) Click on the gedit icon on the panel. In my case gedit starts maximized automatically. 5) Click on the close button (cross) at the top of right corner. 6) I expect that top level application (gedit) should be closed after 5), but instead underlying application (gnome-terminal) is closed. Actually this bug is observed also with other applications (firefox, kile, etc). If I just click on the title bar instead of 5) then underlying application (gnome-terminal) responds to my click and and becomes a top level. So I believe that metacity is responsible for this very annoying bug.
(In reply to comment #14) > I confirm the bug. I observe it on my two linux boxes: Fedora 12 i386 (upgraded > from Fedora 11) and Fedora 12 x86_64 (clean install). This bug is 100% > reproducible on my PCs > > How to reproduce > 1) I use GNOME enviroment > 2) I have launchers on top panel: gnome-terminal and gedit > 3) Click on the gnome-terminal icon on the panel. Maximize gnome-terminal > window. > 4) Click on the gedit icon on the panel. In my case gedit starts maximized > automatically. > 5) Click on the close button (cross) at the top of right corner. > 6) I expect that top level application (gedit) should be closed after 5), but > instead underlying application (gnome-terminal) is closed. > > Actually this bug is observed also with other applications (firefox, kile, > etc). > > If I just click on the title bar instead of 5) then underlying application > (gnome-terminal) responds to my click and and becomes a top level. > > So I believe that metacity is responsible for this very annoying bug. Sounds very straightforward, but I can't reproduce with your instructions either. Can you also attach the output of 'gconftool-2 -R /apps/metacity'. Maybe cross-comparing that to that of Daniel will reveal something. What resolution are you running at? (grasping at straws...)
(In reply to comment #15) > Sounds very straightforward, but I can't reproduce with your instructions > either. Can you also attach the output of 'gconftool-2 -R /apps/metacity'. > Maybe cross-comparing that to that of Daniel will reveal something. > > What resolution are you running at? (grasping at straws...) Fedora 12 i386 (upgraded from Fedora 11) [mkalenkov@sadki ~]$ uname -a Linux sadki 2.6.31.9-174.fc12.i686 #1 SMP Mon Dec 21 06:24:20 UTC 2009 i686 athlon i386 GNU/Linux [mkalenkov@sadki ~]$ cat /etc/fedora-release Fedora release 12 (Constantine) [mkalenkov@sadki ~]$ xrandr --current Screen 0: minimum 320 x 240, current 1280 x 1024, maximum 1280 x 1024 default connected 1280x1024+0+0 0mm x 0mm 1280x1024 50.0* 1280x960 51.0 1024x768 52.0 800x600 53.0 54.0 640x512 55.0 640x480 56.0 57.0 512x384 58.0 400x300 59.0 320x240 60.0 [mkalenkov@sadki ~]$ gconftool-2 -R /apps/metacity /apps/metacity/global_keybindings: cycle_group_backward = disabled switch_to_workspace_1 = disabled switch_to_workspace_2 = disabled switch_to_workspace_3 = disabled switch_to_workspace_11 = disabled switch_to_workspace_12 = disabled switch_to_workspace_6 = disabled switch_to_workspace_4 = disabled switch_to_workspace_7 = disabled switch_to_workspace_9 = disabled switch_to_workspace_8 = disabled show_desktop = <Control><Alt>d switch_to_workspace_10 = disabled cycle_group = <Alt>F6 switch_to_workspace_left = <Control><Alt>Left switch_windows = <Alt>Tab switch_panels = <Control><Alt>Tab switch_to_workspace_down = <Control><Alt>Down switch_to_workspace_5 = disabled switch_windows_backward = disabled switch_to_workspace_right = <Control><Alt>Right cycle_windows_backward = disabled cycle_panels = <Control><Alt>Escape run_command_1 = disabled run_command_2 = disabled run_command_3 = disabled run_command_4 = disabled run_command_5 = disabled run_command_6 = disabled run_command_7 = disabled run_command_8 = disabled switch_group = disabled switch_group_backward = disabled cycle_windows = <Alt>Escape run_command_10 = disabled run_command_11 = disabled run_command_12 = disabled switch_to_workspace_up = <Control><Alt>Up run_command_screenshot = Print panel_main_menu = <Alt>F1 switch_panels_backward = disabled run_command_9 = disabled cycle_panels_backward = disabled run_command_terminal = disabled panel_run_dialog = <Alt>F2 run_command_window_screenshot = <Alt>Print /apps/metacity/keybinding_commands: command_11 = command_12 = command_screenshot = gnome-screenshot command_1 = command_2 = command_3 = command_4 = command_5 = command_6 = command_7 = command_8 = command_9 = command_window_screenshot = gnome-screenshot --window command_10 = /apps/metacity/window_keybindings: minimize = <Alt>F9 begin_resize = <Alt>F8 maximize = disabled move_to_center = disabled move_to_side_e = disabled move_to_workspace_1 = disabled move_to_workspace_2 = disabled move_to_workspace_3 = disabled move_to_workspace_4 = disabled activate_window_menu = <Alt>space toggle_fullscreen = disabled move_to_workspace_6 = disabled move_to_workspace_7 = disabled move_to_workspace_8 = disabled move_to_workspace_9 = disabled move_to_workspace_5 = disabled lower = disabled maximize_horizontally = disabled raise = disabled toggle_shaded = disabled move_to_corner_ne = disabled move_to_workspace_right = <Control><Shift><Alt>Right raise_or_lower = disabled unmaximize = <Alt>F5 move_to_side_w = disabled move_to_side_s = disabled move_to_side_n = disabled move_to_workspace_up = <Control><Shift><Alt>Up toggle_maximized = <Alt>F10 move_to_workspace_left = <Control><Shift><Alt>Left begin_move = <Alt>F7 move_to_workspace_down = <Control><Shift><Alt>Down move_to_corner_nw = disabled close = <Alt>F4 toggle_on_all_workspaces = disabled move_to_corner_sw = disabled maximize_vertically = disabled move_to_corner_se = disabled move_to_workspace_10 = disabled move_to_workspace_11 = disabled move_to_workspace_12 = disabled toggle_above = disabled /apps/metacity/workspace_names: name_1 = name_2 = name_10 = name_11 = name_12 = name_13 = name_14 = name_15 = name_16 = name_8 = name_9 = name_7 = name_5 = name_6 = name_3 = name_4 = /apps/metacity/general: reduced_resources = false auto_raise_delay = 1000 titlebar_font = Liberation Sans Bold 12 application_based = false theme = Nodoka audible_bell = false mouse_button_modifier = <Alt> focus_new_windows = smart compositing_manager = false resize_with_right_button = false new_windows_always_on_top = false titlebar_uses_system_font = false num_workspaces = 4 button_layout = menu:minimize,maximize,close action_middle_click_titlebar = lower no_focus_windows = action_double_click_titlebar = toggle_maximize disable_workarounds = false auto_raise = false visual_bell = true raise_on_click = true focus_mode = click visual_bell_type = fullscreen action_right_click_titlebar = menu [mkalenkov@sadki ~]$
(In reply to comment #15) > Sounds very straightforward, but I can't reproduce with your instructions > either. Can you also attach the output of 'gconftool-2 -R /apps/metacity'. > Maybe cross-comparing that to that of Daniel will reveal something. > > What resolution are you running at? (grasping at straws...) Fedora 12 x86_64 (clean install)[kalenkov@x301 ~]$ uname -a Linux x301 2.6.31.9-174.fc12.x86_64 #1 SMP Mon Dec 21 05:33:33 UTC 2009 x86_64 x86_64 x86_64 GNU/Linux [kalenkov@x301 ~]$ cat /etc/fedora-release Fedora release 12 (Constantine) [kalenkov@x301 ~]$ xrandr --current Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192 LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y axis) 287mm x 180mm 1440x900 60.0*+ 50.0 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 VGA1 disconnected (normal left inverted right x axis y axis) DVI1 disconnected (normal left inverted right x axis y axis) DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) [kalenkov@x301 ~]$ gconftool-2 -R /apps/metacity /apps/metacity/global_keybindings: cycle_group_backward = disabled switch_to_workspace_1 = disabled switch_to_workspace_2 = disabled switch_to_workspace_3 = disabled switch_to_workspace_11 = disabled switch_to_workspace_12 = disabled switch_to_workspace_6 = disabled switch_to_workspace_4 = disabled switch_to_workspace_7 = disabled switch_to_workspace_9 = disabled switch_to_workspace_8 = disabled show_desktop = <Control><Alt>d switch_to_workspace_10 = disabled cycle_group = <Alt>F6 switch_to_workspace_left = <Control><Alt>Left switch_windows = <Alt>Tab switch_panels = <Control><Alt>Tab switch_to_workspace_down = <Control><Alt>Down switch_to_workspace_5 = disabled switch_windows_backward = disabled switch_to_workspace_right = <Control><Alt>Right cycle_windows_backward = disabled cycle_panels = <Control><Alt>Escape run_command_1 = disabled run_command_2 = disabled run_command_3 = disabled run_command_4 = disabled run_command_5 = disabled run_command_6 = disabled run_command_7 = disabled run_command_8 = disabled switch_group = disabled switch_group_backward = disabled cycle_windows = <Alt>Escape run_command_10 = disabled run_command_11 = disabled run_command_12 = disabled switch_to_workspace_up = <Control><Alt>Up run_command_screenshot = Print panel_main_menu = <Alt>F1 switch_panels_backward = disabled run_command_9 = disabled cycle_panels_backward = disabled run_command_terminal = disabled panel_run_dialog = <Alt>F2 run_command_window_screenshot = <Alt>Print /apps/metacity/keybinding_commands: command_11 = command_12 = command_screenshot = gnome-screenshot command_1 = command_2 = command_3 = command_4 = command_5 = command_6 = command_7 = command_8 = command_9 = command_window_screenshot = gnome-screenshot --window command_10 = /apps/metacity/window_keybindings: minimize = <Alt>F9 begin_resize = <Alt>F8 maximize = disabled move_to_center = disabled move_to_side_e = disabled move_to_workspace_1 = disabled move_to_workspace_2 = disabled move_to_workspace_3 = disabled move_to_workspace_4 = disabled activate_window_menu = <Alt>space toggle_fullscreen = disabled move_to_workspace_6 = disabled move_to_workspace_7 = disabled move_to_workspace_8 = disabled move_to_workspace_9 = disabled move_to_workspace_5 = disabled lower = disabled maximize_horizontally = disabled raise = disabled toggle_shaded = disabled move_to_corner_ne = disabled move_to_workspace_right = <Control><Shift><Alt>Right raise_or_lower = disabled unmaximize = <Alt>F5 move_to_side_w = disabled move_to_side_s = disabled move_to_side_n = disabled move_to_workspace_up = <Control><Shift><Alt>Up toggle_maximized = <Alt>F10 move_to_workspace_left = <Control><Shift><Alt>Left begin_move = <Alt>F7 move_to_workspace_down = <Control><Shift><Alt>Down move_to_corner_nw = disabled close = <Alt>F4 toggle_on_all_workspaces = disabled move_to_corner_sw = disabled maximize_vertically = disabled move_to_corner_se = disabled move_to_workspace_10 = disabled move_to_workspace_11 = disabled move_to_workspace_12 = disabled toggle_above = disabled /apps/metacity/workspace_names: name_1 = name_2 = name_10 = name_11 = name_12 = name_13 = name_14 = name_15 = name_16 = name_8 = name_9 = name_7 = name_5 = name_6 = name_3 = name_4 = /apps/metacity/general: visual_bell_type = fullscreen titlebar_font = Sans Bold 13 auto_raise_delay = 500 reduced_resources = false application_based = false theme = Clearlooks mouse_button_modifier = <Alt> focus_new_windows = smart action_double_click_titlebar = toggle_maximize audible_bell = true resize_with_right_button = false new_windows_always_on_top = false compositing_manager = false titlebar_uses_system_font = false num_workspaces = 4 button_layout = menu:minimize,maximize,close action_middle_click_titlebar = lower no_focus_windows = disable_workarounds = false focus_mode = click raise_on_click = true action_right_click_titlebar = menu auto_raise = false visual_bell = false [kalenkov@x301 ~]$
I have found very similar bugs in gnome bugzilla https://bugzilla.gnome.org/show_bug.cgi?id=608139 https://bugzilla.gnome.org/show_bug.cgi?id=608296 https://bugzilla.gnome.org/show_bug.cgi?id=600227 Unfortunately all of them have UNCONFIRMED status. I do confirm all of them!
I also confirm this bug, on an updated F12 i686. It's troublesome in some case, when I click on the "close button" it's not the correct window which is closed !
In fact, it's exactly the "Bug 600227" https://bugzilla.gnome.org/show_bug.cgi?id=600227
Still present in F13 (tested from glx-test-day-2010-04-12.iso).
Confirmed, this is still a very irritating issue with F13ß.
Just for info, my 2 PC (where I have this bug on F12/F13) are running with ATI graphics (R350 and RV770) with free drivers (radeon).
I have more info. I try again on my x86_64 computer with F13 Beta (Gnome LiveDVD). This bug appears ONLY when I maximize the window by double-clicking. If I do Menu > Maximize or if I use the proper button (near the [X] close) I do not have the bug.
Created attachment 408740 [details] Video to show you Sorry for the very very pooor quality of the video, but you'll can anyway see all what you want.
Obviously, the bug is also in RHEL 6 Beta 1.
I have this bug to
I am again able to reproduce it on a third computer (at work), with an Intel G45 (so no relation with ATI video hardware) and the Live Beta F13 i686.
(In reply to comment #28) > I am again able to reproduce it on a third computer (at work), with an Intel > G45 (so no relation with ATI video hardware) and the Live Beta F13 i686. Is it possible to reproduce if you create a new user account and log into that without changing any settings?
I will try that as soon as possible. I can't do it now.
Hello, I am also following this issue as I can reproduce it on my user account in F13 (all updates done today). I am using the "Fedora" theme in the Gnome Desktop Theme choser. I tried on some other users I have for tests in my computer and it was not possible to reproduce this behaviour. They are using the default gnome theme given at the install of gnome as I was not using gnome for those accounts. If some other tests are needed, feel free.
(In reply to comment #29) > Is it possible to reproduce if you create a new user account and log into that > without changing any settings? Yes, I have reproduced this bug for a new user account on my two F12 PCs.
+1 Moreover, no problem when 3D Effects are enabled (I suppose Compiz replaces Metacity).
https://bugzilla.gnome.org/show_bug.cgi?id=599181
CC'ing Alexander who's commit introduced this regression.
So, its seems like its caused by the client-side-windows code in gdk, which metacity uses in a bit uncommon ways (it uses gdk without gtk+). However, knowing that doesn't really make it all that much easier to fix, since its a very large structural change. The problem is probably that the events are delivered in a slightly different order or look slightly different with csw. We need to trace metacity and figure out exactly where it starts acting differently.
Created attachment 417317 [details] Video in highest quality I repost the video in highest quality.
Obviously, this bug present in F13 (x86_64)
I confirm the bug too. It has been there since at least F12 and it's still there in F13. I tried F12 upgraded from F11, fresh install of F12 and F13 upgraded from F12. The bug is still perfectly reproducible on newly created user account with all defaults, I just checked it. IMHO this bug is very SEVERE because it appears in the default configuration (meaning it is visible to many users) and it produces really bad user experience - "what? It's 2010 and the trivial window mousing doesn't work properly in this OS ???".
Created attachment 422363 [details] Output of "gconftool-2 -R /apps/metacity" Attaching output of "gconftool-2 -R /apps/metacity" as well as some other info. Laptop - Dell D630 Latitude [awajda@Calypso Desktop]$ cat /etc/redhat-release Fedora release 13 (Goddard) [awajda@Calypso Desktop]$ uname -a Linux Calypso 2.6.33.5-112.fc13.i686.PAE #1 SMP Thu May 27 02:56:20 UTC 2010 i686 i686 i386 GNU/Linux [awajda@Calypso Desktop]$ xrandr --current Screen 0: minimum 320 x 200, current 1280 x 800, maximum 8192 x 8192 LVDS1 connected 1280x800+0+0 (normal left inverted right x axis y axis) 303mm x 190mm 1280x800 60.0*+ 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 VGA1 disconnected (normal left inverted right x axis y axis) DVI1 disconnected (normal left inverted right x axis y axis) TV1 unknown connection (normal left inverted right x axis y axis) 1024x768 60.0 800x600 60.3 640x480 59.9
(In reply to comment #39) > I confirm the bug too. > > It has been there since at least F12 and it's still there in F13. I tried F12 > upgraded from F11, fresh install of F12 and F13 upgraded from F12. > The bug is still perfectly reproducible on newly created user account with all > defaults, I just checked it. > > IMHO this bug is very SEVERE because it appears in the default configuration > (meaning it is visible to many users) and it produces really bad user > experience - "what? It's 2010 and the trivial window mousing doesn't work > properly in this OS ???". I agree that it's a serious bug, but it hasn't happened to me once for me on 3 different computers in solid usage since F12. And I haven't had any reports of it happening from any of my co-workers on the Red Hat desktop team either. So, apparently it's easily reproducible for a small subset of Metacity users and doesn't happen for anyone else. ("Small subset" could still be many thousands of users.) It's not configuration settings, since it's been described to occur with newly created accounts. Theories I might have: - It's a timing thing only occurs on especially fast or especially slow machines - It only occurs if you click a mouse in some unusual way But I've spent a lot of time trying to follow directions and reproduce it, and gotten nowhere, and it's not worthwhile for me to continue that activity. I also don't think blindly staring at the code is going to reveal what's going wrong. If you think you know how to trigger this - try this: write down your instructions and have a friend that uses GNOME but hasn't previously noticed this bug try to reproduce it following those written instructions. If we figure out what needs to be in those instructions, or what the preconditions are, then we can figure out how to reproduce, and debug and fix.
Reported for Ubuntu too, with some code inside ! https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/494096
OK, the key thing for me seemed to be that I had to double click *slowly* to reproduce the problem. My normal double-click didn't work. I've collected everything together on https://bugzilla.gnome.org/show_bug.cgi?id=599181 - duplicate GNOME bugs, reproduction instructions, the bisected commit reported to introduce the bug. Will work on understanding and fixing soon, though probably not today.
Good new ! Because the most incredible was that you can't reproduce it. I wrote a small post on https://linuxfr.org/ this afternoon, and in less than 4 hours, 17 persons wrote a comment to say that they are able to reproduce the bug (on Fedora / Ubuntu / Mandriva / Arch / Gentoo).
I'm able to reproduce it, but only with Nautilus as the maximized app. I was able to trigger this with the folders in the "Places" Gnome menu (for example, Home Folder, Desktop, or any bookmark), and with nautilus from System Tools > File Browser. I can't reproduce it with anything else, for example from the "Application" Gnome menu or from shortcuts on the panel. The second window can be anything, but I'm mainly using a gnome terminal to test it, with a keyboard shortcut). On my system, the click speed has nothing to do with the bug. (It's on Ubuntu 10.04 64 bits, Gnome 2.30, with metacity, and focus following the mouse) I hope this will help.
Someone on linuxfr have described the problem here (in french) : https://linuxfr.org/comments/1134304.html#1134304 I will try a translation ^^ The problem here is that a click on a window's metacity bar replace the focus on the previous maximized window, it has nothing to do with moving the window. If you change the bar behavior, you can see that the problem occurs only with the "maximize vertical" ("vertically maximize" ? "maximize vertically" ?) and the maximize who also cumultes the "maximize vertical". Something interesting is that the "maximise vertical" is the only action who change the bar position regarding the mouse. So I think that the problem is because te mouse is not where it thinks to be for metacity. Something funny too, is that if you try to resize another window, it will resize the previous window too. The "select windows when the mouse moves over them" doesn't change anything.
There's a build in Koji with an attempt at a fix: http://koji.fedoraproject.org/koji/buildinfo?buildID=177538 (See the upstream details for complete details.) Testing would be much appreciated - I'm pretty sure the patch will fix the bug; I'm less sure it doesn't introduce other problems.
(In reply to comment #47) > There's a build in Koji with an attempt at a fix: > > http://koji.fedoraproject.org/koji/buildinfo?buildID=177538 > > (See the upstream details for complete details.) > > Testing would be much appreciated - I'm pretty sure the patch will fix the bug; > I'm less sure it doesn't introduce other problems. Excellent! You patch fixed the bug (confirmed on my two PCs).
This problem remains in Rawhide. The patch must be applied there too.
*** Bug 539266 has been marked as a duplicate of this bug. ***
(In reply to comment #47) > There's a build in Koji with an attempt at a fix: > > http://koji.fedoraproject.org/koji/buildinfo?buildID=177538 > > (See the upstream details for complete details.) > > Testing would be much appreciated - I'm pretty sure the patch will fix the bug; > I'm less sure it doesn't introduce other problems. 2.30.0-3 seems to fix this problem for me - thanks! I'll carry on using this update and see if I have any problems.
Yes, metacity-2.30.0-3 seems to work fine. Thank You! I'll test it a bit and let you know if I find any other problem.
I can also confirm that metacity-2.30.0-3.fc13.i686 fixes the issue - thanks!
metacity-2.30.0-3.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/metacity-2.30.0-3.fc13
This new version corrects the bug on my computer. Thanks!
metacity-2.30.0-3.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update metacity'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/metacity-2.30.0-3.fc13
metacity-2.30.0-3.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to comment #58) > metacity-2.30.0-3.fc13 has been pushed to the Fedora 13 stable repository. If > problems still persist, please make note of it in this bug report. Reopening: this bug is _not_ fixed in Fedora 12. F12 is still "officially supported", and this bug was originally reported against F12 beta. (btw, I hope this gets fixed in RHEL 6 as well, seeing that recent RHEL 6 betas used Gnome 2.28, which is the same as in F12).
Within the SRPM for metacity-2.28.0-17.el6 (from RHEL6 beta 2), there is this entry within "metacity.spec": * Wed Jun 23 2010 Owen Taylor <otaylor at redhat dot com> - 2.28.0-16 - Add a patch to fix confusion between windows Resolves: rhbz 588926 Bug 588926 points to: https://bugzilla.redhat.com/show_bug.cgi?id=588926 which is basically the RHEL6 version of the present bug. I understand that RHEL is a "paid for" product and deserves first consideration within RH. However, this bug was first discovered in F12. Furthermore, many other bugs reports filed against Fedora by numerous non-RH people go directly towards improving RHEL. How about providing some of the fixes back to Fedora ? In the case of metacity, this doesn't appear to be difficult at all: simply copying metacity-2.28.0-17 from RHEL6 beta2 and providing it as an update to F12 would resolve the issue.
Fedora 14 x86-64 The issue still persists when using GNOME Shell (GNOME 3.0). Exactly the same issue with the same behaviour as described.
Changing the version to "rawhide", so this bug isn't forgotten.
(In reply to comment #62) > Changing the version to "rawhide", so this bug isn't forgotten. This is fine in rawhide, commit was pushed to Mutter in October see last comment of upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=599181#c28