Description of problem: In xfwm4-4.4, when an application becomes unresponsive and the user tries to close its window, the window does not close and the unresponsive application keeps running. xfwm4 4.6 beta adds a new dialog that pops up when the user tries to close an application that isn't responding. I have backported those patches to the latest stable xfwm4-4.4.3 release in Fedora. Version-Release number of selected component (if applicable): 4.4.3 How reproducible: Always. Steps to Reproduce: 1. App becomes unresponsive 2. Try to close app 3. Actual results: App doesn't close Expected results: App should close Additional info: These patches make unresponsive apps close. Please consider adding them to xfwm4-4.4.3 package. Thanks.
Created attachment 323313 [details] xfwm4-4.4.3-terminate-if-not-responding-backport-from-4.6.patch Backported patch to implement "terminate if not responding" dialog from 4.6 beta.
Created attachment 323315 [details] xfwm4-4.4.3-terminate-if-not-responding-backport-from-4.6-language.patch Language updates for dialog.
Created attachment 323316 [details] specfile update And a specfile for the patches. I bumped it to 4.4.3-2 and added a changelog.
This is nice and a cool feature, but why does it merit backporting to the stable release? Hopefully 4.6 will be out before too long and we will get the new feature then.
Created attachment 323365 [details] xfwm4-4.4.3-terminate-if-not-responding-backport-from-4.6-language.patch fix: "anguage updates" -> "language updates"
(In reply to comment #4) > This is nice and a cool feature, but why does it merit backporting to the > stable release? > > Hopefully 4.6 will be out before too long and we will get the new feature then. Thanks. It helps usability, and 4.6 may be some time off. Will Fedora upgrade to 4.6?
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Jayson, what is the status of this bug? I can see your changes in the changelog: * Wed Nov 12 2008 Jayson King <dev> - 4.4.3-2 - backport "terminate if not responding" patches from 4.6 but I can't find the patches in CVS and I can't find 4.4.3-2 in koji.
> Jayson, what is the status of this bug? I use my own custom packages for xfce, so I don't know. > I can see your changes in the changelog: That's just in the .spec file I made to build the package with the patches. It probably should not have had that changelog in it, I guess.
Well, if you guys think it's worth backporting to 4.4.3, I guess we can. 4.6 has it though and that will be in f11. What are your thoughts Christoph?
(In reply to comment #9) > That's just in the .spec file I made to build the package with the patches. It > probably should not have had that changelog in it, I guess. If you check something in, please build it. If you just need it locally, don't use our CVS. (In reply to comment #10) > What are your thoughts Christoph? I tested the patch and the only thing I did not like about it was that it was introducing untranslated strings, but this got fixed, with the language.patch, so I'd like to push this to F9 and F10. In fact I stumbled over this bug while working on Xfce 4.4.3 for F9.
> If you check something in, please build it. If you just need it locally, don't use our CVS. What are you talking about? I didn't use the CVS, I don't even have write access to it.
xfwm4-4.4.3-2.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/xfwm4-4.4.3-2.fc10
xfwm4-4.4.3-2.fc10 has been pushed to the Fedora 10 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 xfwm4'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-3109
xfwm4-4.4.3-2.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.