Closed Bug 545993 Opened 16 years ago Closed 16 years ago

Local folder is locked after drag and drop of news article to local folder. If folder is in pop account, new messages are blocked with message "This folder is being processed ..."

Categories

(Thunderbird :: Folder and Message Lists, defect)

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED
Thunderbird 3.1b2

People

(Reporter: usenet_2007, Assigned: Bienvenu)

References

()

Details

(Whiteboard: [gs])

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 After copying a downloaded news message to a local mail folder the destination folder can't be displayed. No mail can be downloaded from the mail account the destination folder belongs to. When copying two messages in sequence the second one will not be copied to the destination folder after restarting TB. This happens silently, no error message was shown. Reproducible: Always I consider this bug as critical even if it can be circumvented by using menu commands, because a part of the application actually does hang and in some situations data in the destination folder is lost.
Same happens with: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a2pre) Gecko/20100212 Mnenhy/0.8.0pre6 Shredder/3.2a1pre ID:20100212032649 While copying via menu 'Message - Copy to' Shredder freezes for a certain amount of time whereas 'Status Bar' shows 'Determining which messages to index'. Drag&Drop of a newgsroup message into a local folder ends up with the target folder not being able to display at all unless you restart Shredder. 'Activity Manager' does not show an activity at all.
(In reply to comment #0) > After copying a downloaded news message to a local mail folder the destination > folder can't be displayed. No mail can be downloaded from the mail account the > destination folder belongs to. you mean you've lost the ability to get new mail? > When copying two messages in sequence the second one will not be copied to the > destination folder after restarting TB. This happens silently, no error message > was shown. and the message is gone from the original folder, correct? do you see it in the destination folder if you right-click folder and do reindex? bit about ""Determining which messages to index" is similar to bug 540952
Version: unspecified → 3.0
(In reply to comment #2) wOULD YOU MIND READING CAREFULLY AND DOING A TEST BEFORE ASKING ANY - JUST TIME CONSUMING - QUESTIONS? tHANK YOU. (i WROTE OF COPYING, NOT OF MOVING. oNLY A /PART/ OF THE APPLICATION HANGS. i SEE NO SIMILARITY TO BUG 540952.) (bY THE WAY, I'M NOT A TB USER, I REPORTED THE BUG /FOR OTHERS AND FOR YOU/.)
(In reply to comment #3) 1. take a deep breath and relax. It is not polite to yell. people sometimes simply misread the comments. 2. Just because you or someone else can reproduce doesn't mean anyone else can. However, it is reproducible (3.1a1 for me). presumably, comment 0 is about a pop account, but it doesn't say. If it is a pop account folder (or at least for Inbox) one gets a dialog box of This folder is being processed. Please wait until processing is complete to get new messages. If it's just any old local folder (not in a pop account), the folder still gets locked. I have one question for both of you - did this happen in v3.0, i.e. prior to 3.0.1?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Lock after drag and drop of news message to local mail folder → Local folder is locked after drag and drop of news article to local folder. If folder is in pop account, new messages are blocked
Summary: Local folder is locked after drag and drop of news article to local folder. If folder is in pop account, new messages are blocked → Local folder is locked after drag and drop of news article to local folder. If folder is in pop account, new messages are blocked with message "This folder is being processed ..."
(In reply to comment #4) > (In reply to comment #3) > 1. take a deep breath and relax. It is not polite to yell. people sometimes > simply misread the comments. I did not yell - that's just your /interpretation/. I hate the any-thing-goes style of beginning sentences with a lower case letter. (And in German writing nouns with a minuscule.) To me, /that/ is not polite. That's what I wanted to react on. (But you didn't get it...) If /you/ can use /any/ orthography (intentionally), why shouldn't anybody else do the same? > 2. Just because you or someone else can reproduce doesn't mean anyone else can. And? Did you try and comment on not being able to reproduce? > However, it is reproducible (3.1a1 for me). presumably, comment 0 is about a > pop account, but it doesn't say. If it is a pop account folder (or at least for > Inbox) one gets a dialog box of > This folder is being processed. Please wait until processing is complete to > get new messages. In the test it was a /pop/ account folder. But as you could reproduce something at least seemingly related - does it matter? > If it's just any old local folder (not in a pop account), the folder still gets > locked. Ok, you even found a more general case. > I have one question for both of you - did this happen in v3.0, i.e. prior to > 3.0.1? As I told you already, I'm not a TB user. I wanted to try TB as a replacement for SeaMonkey-Mail, for better co-operation with Firefox, but the bug found is a show stopper to me.
I believe this is specific to drag drop, but is reproducible, and I would say it's a blocker.
Assignee: nobody → bienvenu
blocking-thunderbird3.1: --- → beta2+
Oh, extra special, we leave the inbox summary file invalid when we do this, so on startup, it has to reparse.
Whiteboard: [gs]
Wayne asked why this bug happened with drag+drop but not the menu commands. I believe the answer is that dragging the news message is trying to do a move, where it should be doing a copy, because you can't move news messages, since you can't delete them. So the drag drop code needs to check the source and require a copy if you can't delete from the source.
Status: NEW → ASSIGNED
Whiteboard: [gs] → [gs][patch in progress]
Attached patch proposed fix — — Splinter Review
this just makes sure we don't do a move if the source folder can't delete messages.
Attachment #431107 - Flags: review?(mkmelin+mozilla)
Whiteboard: [gs][patch in progress] → [gs][has patch for review mkmelin]
Attachment #431107 - Flags: review?(mkmelin+mozilla) → review+
OS: Windows 7 → All
Hardware: x86 → All
Whiteboard: [gs][has patch for review mkmelin] → [gs][has patch]
Target Milestone: --- → Thunderbird 3.1b2
We're resetting the blocking flag for 3.1 on this bug and instead setting the wanted-thunderbird+ flag. We have too many blocking-3.1 bugs, to the point where it doesn't mean much, and managing the list is making it hard to actually work on closing bugs, which helps no one. Thunderbird 3.1's primary purpose is to allow us to offer a prompted major update to Thunderbird 2 users, to ensure their continued ability to safely use Thunderbird. Thunderbird 2 is built on an outdated version of Gecko, and our long-term ability to maintain the users' safety for Thunderbird 2 users is limited. If you think this bug meets the requirements below, please renominate with a detailed explanation of how it meets the following two criteria, and we will reconsider. To qualify, this bug must either: a) make the upgrade experience from TB2 very painful for a large number of users or b) be a new, reproducible, severe quality issue (eg dataloss, frequent crashes) Just because this bug doesn't block TB3.1 doesn't mean it can't or won't make the release. Once they're done with their blockers (if any), we encourage developers to keep working on non-blocking bugs, and to try to land them as early in the cycle as possible, as non-blocking bugs will become increasingly difficult to land in the later stages of the cycle.
blocking-thunderbird3.1: beta2+ → ---
Flags: wanted-thunderbird+
More and more I get the impression, this bug report is a write-only text area, at least for programmers, to practice writing skills a bit... (Please forgive. It's just too tiring to repeat almost everything twice or three times that was stated clearly already.) To David, comments 9 and 10: I don't think your patch will fix this bug, because the blocking happens at the destination folder not at the source. For the destination copying and moving are the same. And just _requiring_ a copy where the user already tries to initiate a _copy_ anyway doesn't help either. To Dan, comment 11: Comment 1 states: "Reproducible: Always I consider this bug as critical even if it can be circumvented by using menu commands, because a part of the application actually does hang and in some situations data in the destination folder is lost." This fulfills at least b), probably a) also. I won't think of trying Thunderbird again as a daily MUA for even the tenth of a second before this bug is fixed. If you really have so many severe bugs that you want to weed out bugs of the present kind as blockers for TB 3.1 that would mean that quite a lot went wrong in the development of TB... (Too much concentration on new, "shiny" features instead of quality assurance.)
(In reply to comment #12) > > To David, comments 9 and 10: > I don't think your patch will fix this bug, because the blocking happens at the > destination folder not at the source. For the destination copying and moving > are the same. > And just _requiring_ a copy where the user already tries to initiate a _copy_ > anyway doesn't help either. Ueli, tomorrow's 3.1 b2pre build will have the fix in it, and I invite you to try it. I tend to agree with you that this should be a blocker bug, but since it had a reviewed patch that fixes the bug, I didn't see much point in arguing about it. Fix checked in. I don't think mozmill lets us do drag drop, nor can we do news, so a unit test isn't feasible at this point.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Whiteboard: [gs][has patch] → [gs]
Flags: in-litmus?
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: