Description of problem: when using the windowshade feature to 'roll-up' the window but leave the title bar visible, either by using the scrollwheel-up on the titlebar, or clicking the up-arrow decoration, gvim immediately crashes. Version-Release number of selected component (if applicable): vim-X11-8.0.1030-1.fc25.x86_64 Installed environment groups: Xfce Desktop How reproducible: everytime Steps to Reproduce: 1. be in xfce and open a file in gvim via a terminal 2. mouseover titlebar and scroll-wheel-up, or click the windowshade icon in the titlebar Actual results: error as follows is presented in terminal BadMatch (invalid parameter attributes) Vim: Got X error Vim: Finished. Expected results: normal windowshade action Additional Info: other windows will windowshade properly. only vim-X11 seems to be affected
Hi Scott, thank you for reporting this issue. Would you mind trying the newest Vim update for f25, if it helps? It is in updates-testing repository.
The issue happens only with default window manager, xfwm4. If you change your window manager to e.g. compiz, the issue isn't there.
xfwm4 communicates differently with Vim, when Vim is compiled with gtk3. I'm not certain how to debug its communication, but what I captured by dbus-monitor: $ dbus-monitor --session Vim compiled with gtk3: signal time=1508159275.762763 sender=org.freedesktop.DBus -> destination=:1.104 serial=5 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost string ":1.104" signal time=1508159275.762781 sender=org.freedesktop.DBus -> destination=(null destination) serial=121 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string ":1.104" string ":1.104" string "" signal time=1508159275.768510 sender=:1.23 -> destination=(null destination) serial=133 path=/org/xfce/SessionClients/290a55d72_a7a4_448a_846e_6ff01e3a3e28; interface=org.xfce.Session.Client; member=StateChanged uint32 0 uint32 7 Vim compiled with gtk2: no messages captured Because communication ends with X error, so I think error can be in communication between xfwm4 and x server. Attaching output of strace and reassigning to xorg-x11, if they know more about it.
Created attachment 1339295 [details] Strace
vim-common-2:8.0.1030-1.fc25.x86_64 update still has the same issue
The issue is also present in Fedora 26 with vim-X11-8.0.1187-1.f26.x86_64
This problem does not show up in the latest vim-X11 that came out for Fedora 23 (vim-X11-7.4.1868-1), but is present in the latest version on Fedoras 24 (vim-X11-8.0.617-1), 25 (vim-X11-8.0.1171-1) and 26 (vim-X11-8.0.1187-1).
(In reply to Zdenek Dohnal from comment #3) > xfwm4 communicates differently with Vim, when Vim is compiled with gtk3. Greg, I'm sorry I didn't explicitly say it. This bug exists since VIm started to be compiled with gtk3 (I guess Vim started to compile with gtk since f22).
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug is still present in Fedora 27 (maintainer please bump version to reflect this).
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This bug is still present in Fedora 29 (maintainer please bump version to reflect this). vim-X11-8.1.1099-1.fc29.x86_64
Created attachment 1555182 [details] backtrace when the error is caught According the backtrace, the error comes from libX11/Gtk...
BadMatch means that the client (gvim, here) sent an invalid request to the server. libX11 is innocent, it's just reporting that gvim did something wrong. Reassigning to vim.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.