Bug 320736 - No progress indication for copying/moving email messages/folders
Summary: No progress indication for copying/moving email messages/folders
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: folders (show other bugs)
Version: 4.10.3
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-04 21:20 UTC by Geoffrey van Wyk
Modified: 2017-01-07 21:58 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Geoffrey van Wyk 2013-06-04 21:20:35 UTC
When copying or moving email messages or folders from one folder to another within KMail, there is no indication that the copying or moving has started or what its status is.

Such progress indication could be in the status bar or in a dialog.

Reproducible: Always

Steps to Reproduce:
1. Select a folder or messages.
2. On the Edit menu, click Copy or Cut.
3. Select the destination folder.
4. On the Edit menu, click Paste.
Actual Results:  
The copying/moving does work upon inspection.

Expected Results:  
During the copying/moving there is no indication of whether the process has started or what the progress is.
Comment 1 Joe Biden 2013-08-25 03:09:59 UTC
It also fails badly, by telling you about the filename (garbled in Maildir goblegook) when it fails...Why it fails? Output says:

"(knotify4:22466): GStreamer-CRITICAL **: gst_poll_free: assertion `set != NULL' failed

(knotify4:22466): GStreamer-CRITICAL **: gst_poll_write_control: assertion `set != NULL' failed

(knotify4:22466): GStreamer-CRITICAL **: gstsystemclock: write control failed in wakeup_async: 24:Too many open files


(knotify4:22466): GStreamer-CRITICAL **: gst_poll_free: assertion `set != NULL' failed
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x78004c5
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x78004c5
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 18 (X_ChangeProperty)
  Resource id:  0x78004c5
Ignoring source as no aboutToFinish handling is in progress. 
Ignoring source as no aboutToFinish handling is in progress. 
Nepomuk search service not available! 
"
Comment 2 Christoph Thielecke 2014-02-07 12:51:36 UTC
Still present in 4.12.1
Comment 3 Denis Kurz 2016-09-24 17:52:45 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 21:58:35 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.