Bug 456201 - "Ctrl+C" to kill thunderbird will get get message "Unknown message:Panel"
"Ctrl+C" to kill thunderbird will get get message "Unknown message:Panel"
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: thunderbird (Show other bugs)
i386 Linux
low Severity low
: rc
: ---
Assigned To: Gecko Maintainer
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2008-07-22 02:22 EDT by Yolkfull Chow
Modified: 2008-10-21 18:43 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 642655 (view as bug list)
Last Closed: 2008-10-21 18:43:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Yolkfull Chow 2008-07-22 02:22:50 EDT
Description of problem:
"Ctrl+C" to kill thunderbird in terminal or other usage such as "thunderbird
-news" will get error message "Unknown message: Panel".

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. launch thunderbird or with any options such as "thunderbird -compose" in terminal
2. "Ctrl +C" to kill the process
Actual results:
Get some error messages

Expected results:
There should have none error messages

Additional info:
Comment 1 Matěj Cepl 2008-07-22 13:03:37 EDT
Cannot reproduce on RHEL5 with thunderbird-
Comment 2 Matěj Cepl 2008-07-22 16:53:06 EDT
Sorry, I overlooked the verison of your package.
Comment 3 Matěj Cepl 2008-07-22 17:05:29 EDT
Cannot reproduce even with the same version as you have. Do you have any
extensions for thunderbird loaded? Can you reproduce it even with -safe-mode
parameter on the command line?
Comment 4 Matěj Cepl 2008-09-18 11:28:07 EDT
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Comment 5 Matěj Cepl 2008-10-21 18:43:01 EDT
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.


Note You need to log in before you can comment on or make changes to this bug.