Closed
Bug 765029
Opened 12 years ago
Closed 12 years ago
Messages containing GMT+NN in the Date: header display an error when opened - "Bad key or directory name"
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 541130
People
(Reporter: max, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1171.0 Safari/537.1 Steps to reproduce: Received a message with the Date: header looking as follows: Date: June 14, 2012 6:33:21 PM GMT+03:00 Actual results: Any time such a message is opened, the following error is displayed: Bad key or directory name: "/desktop/gnome/url-handlers/GMT+03/command": `+' is an invalid character in key/directory names Bad key or directory name: "/desktop/gnome/url-handlers/GMT+03/command": `+' is an invalid character in key/directory names Expected results: The error appears consistently if a Date: header containing GMT+NN is present in the message itself or in an attached message. Messages with Date: headers specifying the timezone as +NNNN do not cause a problem. The platform is Linux/Ubuntu 10.04 amd64
Comment 1•12 years ago
|
||
The error message is phenomenon of bug 541130. Particularity of this bug is "GMT+03: in Date: header".
Updated•12 years ago
|
Summary: Messages containing GMT+NN in the Date: header display an error when opened → Messages containing GMT+NN in the Date: header display an error when opened -
Updated•12 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Messages containing GMT+NN in the Date: header display an error when opened - → Messages containing GMT+NN in the Date: header display an error when opened - "Bad key or directory name"
Comment 3•12 years ago
|
||
Confirmed: Bad key or directory name: "/desktop/gnome/url-handlers/GMT+01/command": `+' is an invalid character in key/directory names
Comment 4•12 years ago
|
||
I have the same error, it is however strange that it may or may not happen in mails received from the same person... In my case it is GMT+01 that causes the error to appear TB17.0 and Ubuntu 10.04.4 LTS
Updated•12 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•