kmail "send queued messages" grayed out inappropriately
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
ProcVersionSign
SourcePackage: kdepim
Uname: Linux 2.6.31-17-generic i686
XsessionErrors: (polkit-
Changed in kdepim: | |
status: | Unknown → New |
Changed in kdepim: | |
importance: | Unknown → Medium |
Changed in kdepim: | |
status: | New → Unknown |
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!