Xubuntu 11.04 on various HP machines 32/64 bit. Mousepad does not close when hitting the Close button. Mousepad version used is 0.2.16 from normal Xubuntu repository. No alpha or beta version installed. Leafpad on Xubuntu works perfectly, hence using it in place of Mousepad.
Compiled from the git repository from git.xfce.org and I couldn't produce the error. I clicked both the close button of the window manager and File>Close from within the mousepad menu bar. I'm running Ubuntu 11.10 i686. Perhaps it's a mistake on Ubuntu's end. Since I'm compiling from source, I feel that the close feature within mousepad has been correctly implemented. Is anyone having this problem?
This problem is on Xubuntu 11.04 i686. No idea if on Xubuntu 11.10 it has been fixed, i haven't tried that yet.
Hello, I have a similar issue. mousepad delay close when copy text (CTRL+C) with clipman running at boot. mousepad close after some seconds. If not run clipman at boot, mousepad copy text and close without delay. Tested under Salix XFCE 13.1 32 bits kernel 2.6.33.20 mousepad 0.2.16 Salix XFCE 13.37 64 bits kernel 2.6.37.6 mousepad 0.2.16 Regards
I'm using Xubuntu 12.04 (not Ubuntu 12.04 with added xubuntu-desktop or xfce4 packages) and Mousepad has been swapped with Leafpad. Leafpad always worked perfectly with Xubuntu from version 11.04 (not Ubuntu with added xubuntu-desktop or xfce4 packages).
Confirming this intermittent bug on Debian Squeeze Xfce with Mousepad Version: 0.2.16-4. Hard to reproduce and only occurs occassionally. It generally only happens when there are unsaved changes (empty doc). The prompt to save comes up and after pressing "No", Mousepad stays open when it should be closing. The error can repeat itself numerous times before finally closing (or never does). Random and probably unhelpful: I remember distinctly getting Mousepad to close by un-Maximizing the window and then trying the close procedure again. I haven't a clue why that would factor in, so maybe it was dumb luck?
I can't reproduce this bug in version 0.3.0, maybe this rewritten version has fixed the problem. Please check.
Closing as fixed since it can't be reproduced with lastest version, which is a total re-write of version this bug is about, and which is no longer maintained or supported. Please feel free to re-open and update the version on this bug or make a new report if you experience it still in latest version.