Description of problem: Pan overreacts if try to Close before finished perusing new postings Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Request New Headers (new message bodies appear in some newsgroups) 2. Before finishing perusing new postings, hit the Close button. 3. Pan responds with e.g. "You tried to close window "Pan: uk.telecom.mobile" from application "pan" (Process ID: 50898) but the application is not responding. Do you want to terminate this application? Warning: Terminating the application will close all of its child windows. Any unsaved data will be lost" 4. Offers 2 choices: Terminate or Wait Longer (If one waits a few minutes, it does close.) Comment: Would be much more helpful to say e.g. "Closing..." with a dynamic time bar
Closing Pan prematurely could be caused e.g. by carelessness or perhaps due an external domestic situation that needs urgent attention, but with hindsight it should be just minimised rather than closed...]
N.B. Same thing happens with Pan 0.145 on Mga7.
]$ pan (pan:5454): Gtk-WARNING **: 17:30:08.930: Theme parsing error: gtk.css:7:33: Failed to import: Error opening file /home/mab/.config/gtk-3.0/window_decorations.css: No such file or directory GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name news.pan.NZB was not provided by any .service files (pan:5454): Gtk-WARNING **: 17:30:09.293: Unable to parse accelerator '<constrol>O' for action 'import-tasks' (pan:5454): GLib-GObject-CRITICAL **: 17:30:11.840: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Existing Quarks: 7: [Xref] (refcount 1) [Newsgroups] (refcount 1) [From] (refcount 1) [Message-ID] (refcount 1) [Subject] (refcount 1) [Message-Id] (refcount 1) [References] (refcount 1)
N.B. After re-starting Pan I noticed the postings I had read still showed the number of message bodies to be read, although in each case if I tried to select them the (numbers) just disappeared...
See also https://bugs.mageia.org/show_bug.cgi?id=14806
[That bug is ancient, so I closed it!] Thank you for the report, and for confirming the problem in Mageia 7 also, showing it is not new. I am not sure this is a bug: - "Pan objects to being closed before all new postings have been read" - "Offers 2 choices: Terminate or Wait Longer" - "If one waits a few minutes, it does close" all seem reasonable reactions in the light of interrupting it in the middle of sorting itself out. The application seems to work sensibly in the circumstances: it does not look to be doing anything wrong, unless you regard comment 4 as an error rather than just 'that is how it functions'. Does anything get lost? If so, please re-open the bug accordingly. It does not look worth it. As for your suggestion "Would be much more helpful to say e.g. "Closing..." with a dynamic time bar" that is for upstream chez Gnome. Do that if you wish.
Status: NEW => RESOLVEDWhiteboard: (none) => MGA7TOOCC: (none) => lewyssmithResolution: (none) => INVALID