kmail "send queued messages" grayed out inappropriately

Bug #511524 reported by Tim Holy
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
KDE PIM
Unknown
Medium
kdepim (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kdepim

Steps to reproduce this problem:
1. Put your network in some state where you can't send email (e.g., disconnect from the cable or wireless).
2. Compose a message to yourself and send it. After a while you will get the dialog saying the message can't be sent, and will be placed in your outbox
3. Under the file menu, you will now see that "Send queued messages" and "Send queued messages via..." will be enabled. If, at this point, you chose one of them, everything would be fine.
4. However, in this case don't do it right away: navigate to another folder, read some messages, etc.
5. Now check the file menu again: "Send queued messages" and "Send queued messages via..." will now be greyed out, even though that message is still queued in your outbox. You can send the message by selecting your outbox, which will re-enable those two menu options.

I would think that the proper behavior would be to enable "Send queued messages" and "Send queued messages via..." anytime there are messages waiting in your outbox.

ProblemType: Bug
Architecture: i386
Date: Sat Jan 23 04:40:49 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kontact
Package: kontact 4:4.3.2-0ubuntu6
ProcEnviron:
 LANGUAGE=en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SourcePackage: kdepim
Uname: Linux 2.6.31-17-generic i686
XsessionErrors: (polkit-gnome-authentication-agent-1:27500): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Tim Holy (holy-wustl) wrote :
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!

Changed in kdepim (Ubuntu):
status: New → Invalid
Revision history for this message
P (p92) wrote :

Hey jonathan
this seems the new policy of kubuntu to demand users to open bug directly upstream. In this case why is these only a "report a bug" button in applications that is exclusive to launchpad ?
Is there a web page to discuss this subject instead of here ?

Revision history for this message
P (p92) wrote :

I agree totally with this wish, and was about to declare the same incident :)

Revision history for this message
P (p92) wrote :

Declared upstream and linked

Changed in kdepim:
status: Unknown → New
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

The change was made after 9.10 was released, and unfortunately it's not something that can really be changed post release as it isn't important enough to justify forcing a several-megabyte update on people.

Revision history for this message
Tim Holy (holy-wustl) wrote :

I kind of agree with PascalCavy's comment #3. You might be better off letting that "Report a Bug..." menu entry connect users straight to KDEbugs and bypassing Launchpad.

In principle, I don't think it's unreasonable for Kubuntu to "hijack" the KDE bug report feature; but given that you've decided to do so, it would seem incumbent upon the project to then manage any bug reports, passing them upstream as needed. Otherwise, you may be doing more harm than good. There is no way a typical user can be expected to figure out whether it is a KDE bug or a Kubuntu bug. Given that KDE is the one maintaining the source tree, really it's better if _they_ get the bug reports and then can decide whether it's a Kubuntu-specific problem. I'd much rather see problems fixed in the source tree, once and for all, than just for one specific release of Kubuntu.

Revision history for this message
In , P (p92) wrote :

Version: 1.12.4 (using KDE 4.3.5)
OS: Linux
Installed from: Ubuntu Packages

I have set up my outbox to not automatically send messages. I also have added a "send queued messages" button in my kmail toolbar.

Let's compose messages and send them, they are all waiting in outbox.

Now if my current folder in the outbox, the button is active to "send queued messages".

But as soon as I go to another folder (usually inbox), the button is inactive and greyd out.

Expected behaviour : the "send queued messages" button should be active whenever message_count(outbox) > 0

Revision history for this message
In , P (p92) wrote :

With :

Qt : 4.6.1
Plate-forme de développement de KDE : 4.4.00 (KDE 4.4.0)
KMail : 1.13.0

the behaviour is a little bit better but there are still some cases where the button is grayed out when it should'nt be.

Revision history for this message
In , Montel-3 (montel-3) wrote :

I can confirm this bug in kde 4.4.5 too.
I tried to fix it, but there is a pb in outbox->count(), never correctly updated.
Don't know why yet.
=> it"s a pb

Revision history for this message
In , P (p92) wrote :

Still true in 4.5.5

Revision history for this message
In , P (p92) wrote :

please change this to CONFIRMED

Changed in kdepim:
importance: Unknown → Medium
Revision history for this message
In , Montel-3 (montel-3) wrote :

Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.

Changed in kdepim:
status: New → Unknown
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.