288102 - Thunderbird tries to find URL handler for strings with invalid chars, issues warnings

Status: RESOLVED EXPIRED

(Thunderbird :: Mail Window Front End, defect)

Description

[Dan Mick]

User-Agent:       Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7.6) Gecko/20050323 Firefox/1.0.2
Build Identifier: version 1.0.2 (20050323)

When viewing a mail message, Thunderbird helpfully tries to identify
strings that might be URIs, and linkify them.  Under Gnome, when the
string has invalid characters in it, libgconf will issue a warning about the
invalid characters.

To reproduce, view a mail message with the text "GMT+00:00" in it (or
any of a number of other invalid characters).  This causes this warning
from libgconf:

GConf Error: Bad key or directory name:
"/desktop/gnome/url-handlers/GMT+00/command": `+' is an invalid character in
key/directory names




Reproducible: Always

Steps to Reproduce:
To reproduce, view a mail message with the text "GMT+00:00" in it (or
any of a number of other invalid characters).  This causes a warning
from libgconf in the terminal where Thunderbird was started (i.e.,
presumably to stderr).


Actual Results:  
GConf Error: Bad key or directory name:
"/desktop/gnome/url-handlers/GMT+00/command": `+' is an invalid character in
key/directory names


Expected Results:  
Prevalidate the URI schema doesn't contain illegal characters before calling
libgconf.

Here's a raw stack backtrace, and then one with parameters removed and 
C++ routine names demangled:





libgconf-2.so.4.1.0`gconf_client_get_string
__1cUnsOSHelperAppServicebDExternalProtocolHandlerExists6Mpkcpi_I_+0xd7
__1cZnsExternalProtocolHandlerbAExternalAppExistsForScheme6MrknKnsACString_pi_I_+0x5c
__1cQmozTXTToHTMLConvNShouldLinkify6MrknJnsCString__i_+0xe2
__1cQmozTXTToHTMLConvVCheckURLAndCreateHTML6MrknInsString_3kn0AImodetype_r1_i_+0xdc
__1cQmozTXTToHTMLConvHFindURL6MpkHikI3rnInsString_ri6_i_+0x2aa
__1cQmozTXTToHTMLConvHScanTXT6MpkHiIrnInsString__v_+0x571
__1cQmozTXTToHTMLConvHScanTXT6MpkHIppH_I_+0xa1
0x8f58cf3
0x8f567ca
0x8f56a4d
0x8f5c427
mime_LineBuffer+0x15d
0x8f565fc
0x8f50732
0x8f52b65
0x8f5c427
mime_LineBuffer+0x15d
0x8f55212
mime_display_stream_write+0x112
__1cRnsStreamConverterPOnDataAvailable6MpnKnsIRequest_pnLnsISupports_pnOnsIInputStream_II_I_+0xa7
__1cSnsDocumentOpenInfoPOnDataAvailable6MpnKnsIRequest_pnLnsISupports_pnOnsIInputStream_II_I_+0x26
__1cZnsImapCacheStreamListenerPOnDataAvailable6MpnKnsIRequest_pnLnsISupports_pnOnsIInputStream_II_I_+0x21
__1cRnsInputStreamPumpPOnStateTransfer6M_I_+0xb8
__1cRnsInputStreamPumpSOnInputStreamReady6MpnTnsIAsyncInputStream__I_+0x37
0xbeb74ce5
libxpcom.so`PL_HandleEvent+0x1f
libxpcom.so`PL_ProcessPendingEvents+0x6d
libxpcom.so`__1cQnsEventQdDueueImplUProcessPendingEvents6M_I_+0x3c(97213d0, 
997f628, bf9af346, 997f5e0, 1, 97213d0)
0x8625af2
libglib-2.0.so.0.400.1`g_io_unix_dispatch+0x32
libglib-2.0.so.0.400.1`g_source_callback_funcs
0x8625ae0

libgconf-2.so.4.1.0`gconf_client_get_string
nsOSHelperAppService::ExternalProtocolHandlerExists+0xd7
nsExternalProtocolHandler::ExternalAppExistsForScheme+0x5c
mozTXTToHTMLConv::ShouldLinkify+0xe2
mozTXTToHTMLConv::CheckURLAndCreateHTML+0xdc
mozTXTToHTMLConv::FindURL+0x2aa
mozTXTToHTMLConv::ScanTXT+0x571
mozTXTToHTMLConv::ScanTXT+0xa1
0x8f58cf3
0x8f567ca
0x8f56a4d
0x8f5c427
mime_LineBuffer+0x15d
0x8f565fc
0x8f50732
0x8f52b65
0x8f5c427
mime_LineBuffer+0x15d
0x8f55212
mime_display_stream_write+0x112
nsStreamConverter::OnDataAvailable+0xa7
nsDocumentOpenInfo::OnDataAvailable+0x26
nsImapCacheStreamListener::OnDataAvailable+0x21
nsInputStreamPump::OnStateTransfer+0xb8
nsInputStreamPump::OnInputStreamReady+0x37
0xbeb74ce5
libxpcom.so`PL_HandleEvent+0x1f
libxpcom.so`PL_ProcessPendingEvents+0x6d
libxpcom.so`nsEventQueueImpl::ProcessPendingEvents+0x3c
0x8625af2
libglib-2.0.so.0.400.1`g_io_unix_dispatch+0x32
libglib-2.0.so.0.400.1`g_source_callback_funcs
0x8625ae0

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.