Closed Bug 57630 Opened 24 years ago Closed 23 years ago

can't search mail/news messages

Categories

(SeaMonkey :: MailNews: Message Display, defect, P2)

Product:
SeaMonkey
Component:
MailNews: Message Display
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME
Milestone:
Future

People

(Reporter: spam, Assigned: Bienvenu)

Details

(Keywords: regression, Whiteboard: [nsbeta1+ 1/25])

Attachments

(1 file)

nntpio.txt debug
8.39 KB, text/plain
Details 
Linux SEA 2000102021

Attempting to search in a newsgroup for "subject" that "contains" (the defualt
query) doesn't work.

-For each character typed of the searchword i see this in console:

JavaScript error:
 line 0: goDoCommand is not defined

-Then, when hitting Search-button, a popup appears, saying:

NEWS ERROR: A News (NNTP) error occured:Syntax error or bad command

Simoultanously, in console i see:

setting up search..
Saving search element 0
************************************************************
* Call to xpconnect wrapped JSObject produced this error:  *
[Exception... "[JavaScript Error: "gThrobber has no properties" {file:
"chrome://messenger/content/mailWindow.js" line: 238}]
[nsIMsgStatusFeedback::StartMeteors]"  nsresult: "0x80570021
(NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame ::
chrome://messenger/content/SearchDialog.js :: onSearch :: line 154"  data: yes]
************************************************************
************************************************************
* Call to xpconnect wrapped JSObject produced this error:  *
[Exception... "[JavaScript Error: "gThrobber has no properties" {file:
"chrome://messenger/content/mailWindow.js" line: 238}]
[nsIMsgStatusFeedback::StartMeteors]"  nsresult: "0x80570021
(NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame ::
chrome://messenger/content/SearchDialog.js :: onSearch :: line 154"  data: yes]
************************************************************
Kicking it off with mailsearch:#3



-When i now click "cancel" - the only option - yet an error appears:

stopping meteors 1
************************************************************
* Call to xpconnect wrapped JSObject produced this error:  *
[Exception... "[JavaScript Error: "Bundle has no properties" {file:
"chrome://messenger/content/mailWindow.js" line: 259}]
[nsIMsgStatusFeedback::StopMeteors]"  nsresult: "0x80570021
(NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "<unknown>"  data: yes]
************************************************************
QA Contact: esther → laurel
Using 10/24 commercial branch build with linux rh6.0, doesn't work at all for
news, does for mail after several tries.

Regressed since last week.
Keywords: regression, rtm
sorry david, I just don't have time.. I'll stay on the CC list if you have
questions about the UI
Assignee: alecf → bienvenu
adding Seth to cc list in case it's somehow an nntp issue - imap search works
fine. I don't know of any changes in the search code in the past month or two.
Perhaps it's a packaging or jar file issue.
I see the js error on every character typed, but the search works fine and I see
the results. This was on NT.
Status: NEW → ASSIGNED
Seth said news search is working fine on today's Linux NS 6 build. Laurel, can
you make sure it's really not working for you? What did you search for?
Scott, when you get a chance, could you take a gander at the js errors - Seth
say's they're coming from mailWindowOverlay.xul. Thanks!
Well, earlier today it didn't work at all on queries I did like:
-- subject contains test on netscape.test
-- subject contains mail on n.p.m.mail-news

Now I'm getting it to work, but still only sometimes. When it doesn't work, it
really doesn't work.

One thing I noticed is when you search mail having a mail folder selected, then
switch the scope dropdown to a newsgroup and issue the same search (like subject
contains mail) it doesn't work at all on news.  Then even closing the search
dialog, selecting the newsgroup and issue a search doesn't work well (sometimes
works, sometimes doesn't).  It seems to work more reliably if I don't do a mail
search first.

putterman, there are three errors:

************************************************************
* Call to xpconnect wrapped JSObject produced this error:  *
[Exception... "[JavaScript Error: "gThrobber has no properties" {file:
"chrome://messenger/content/mailWindow.js" line: 238}]
[nsIMsgStatusFeedback::StartMeteors]"  nsresult: "0x80570021
(NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame ::
chrome://messenger/content/SearchDialog.js :: onSearch :: line 154"  data: yes]
************************************************************

JavaScript error:
 line 0: goOnEvent is not defined

JavaScript error:
 line 0: goDoCommand is not defined

the look to be coming from mailWindow.js and mailWindowOverlay.xul

(same weirdness we've seen before when using mailWindow and not having a throbber.)

we should at least fix the errors that come on every key stroke.

laurel:

FYI:  here's what I did:

read news in news://news.mozilla.org/netscape.test
search for articles with subject "blah"


what do you mean, it really doesn't work? Do you see the nntp alert error, or do
you just not get any results back? Or does it crash?
I'm not having any problems with any of the scenarios you describe.
No crash, no results back, no NNTP alert.  Window sits there, no progress/barber
pole activity.
searching works fine for me in news on my debug build.  I see the exceptions
Seth mentions but I don't see anything bad happening because of them so I don't
think we need to worry about those for rtm.
This was originally reported against the Linux SEA build.  Is it possible
there's a packaging problem with that type of dist and/or just that platform?
Before this gets minus, is there any theory why Laurel's getting a hang and the
rest of you aren't?
Whiteboard: [rtm need info]
I don't see where Laurel sees a hang. What she saw is indistinguishable from a
search with no hits.
SEA 2000-102621 Linux: The "search mail/news messages" still misbehaves like
originally reported.
rtm-, no provable user effect.
Whiteboard: [rtm need info] → [rtm-]
I can still reproduce this using build 2000110720 on win32.
Sometimes results don't show up at all, dumping javascript errors, sometimes the
results show, dumping even more js errors. All the js errors i get :
goDoCommand not defined, no source file.
gThrobber has no properties, chrome://messenger/content/mailWindow.js
Bundle has no properties, chrome://messenger/content/mailWindow.js
BeginDragThreadTree not defined, no source file.
goOnEvent not defined, no source file.
Fabian
The js errors are, though annoying, irrelevant, I believe.  the real question is
what the nntp error was. I'm not able to reproduce any problems with mail or
news search.
and with sea linux 20001114 i'm still not able to search. Same initial NNTP
error message. In case this might be server dependant:
Telnet'ing the server at port 119 shows:

 NNTPcache server V2.4.0b1 [see www.nntpcache.org]

if you could try turning on nntp protocol logging, that would be very helpful.
Set the following environment variables, start up the client and run the search
that fails, shutdown, and then send me (or attach to this bug) the file
/tmp/nntpio.txt (or whatever path you chose for the tmp file). If you've got a
password protected news server, you should remove the password from the log.

setenv NSPR_LOG_FILE=/tmp/nntpio.txt
setenv NSPR_LOG_MODULES=NNTP:5

thanks, - David
seems to be server dependant.
I tried searching my ISP's server again, same error.
Then searched some groups on other servers - it worked.
Attached file nntpio.txt debug — 

    
    

    
  
Uh oh. Discovered i can't search news.cybercity.no with NC4.75 either.
Same error. I'll try find out what's going on there.

    
    

    
  
sounds like an inter-op bug in the news code.

can you search with other news readers?

    
    

    
  
thanks, I was going to ask if 4.75 worked. My guess is that it's a bug in our
search response parsing code triggered by the search response returned by your
particular server, and that causes us to put up a generic error.

    
    

    
  
Sniffing at it with etherearl, the error IS the search response. It is sent in
clear text FROM the news-server:
"500 Syntax error  or bad command\r\n"
Mozilla passing that on to a dialog-box is the right thing to do. But doesnt'
solve the riddle.
I asked in a newsgroup there whether search somehow was disabled on that server.
I pay for that service - will nag at support later.

    
    

    
  
that error doesn't show up in the protocol log, for some reason.  Was that a
different search session, or are we not logging errors, Seth? (that seems really
unlikely)

    
    

    
  
err.. the error indeed shows up:

1024[8058638]: Sending: XPAT SUBJECT  1- *[Uu][Dd][Mm][Aa]*
1024[8058638]: Sending: XPAT SUBJECT  1- *[Uu][Dd][Mm][Aa]*
1024[8058638]: Next state: NNTP_RESPONSE
1024[8058638]: Receiving: 500 Syntax error or bad command
1024[8058638]: Next state: NNTP_XPAT_RESPONSE
1024[8058638]: Next state: NNTP_ERROR

It's all that is received. It *is* the response to the request. Get it?

    
    

    
  
sorry, I missed that. I guess you did multiple searches - I was looking at the
search at the end, which I guess succeeded.

    
    

    
  
adding mail3 keyword
Keywords: mail3

    
    

    
  
changing priorities
Priority: P3 → P2

    
    

    
  
marking nsbeta1+ and moving to mozilla0.8

Laurel, is this still happening to you?
Keywords: rtm → nsbeta1
Whiteboard: [rtm-] → [nsbeta1+]
Target Milestone: --- → mozilla0.8

    
    

    
  
cc'ing news expert Simon.

    
    

    
  
Can someone summarize? Does this happen on all servers, or just the (likely 
broken) NNTPCache server? And what's the address of a server where I can test 
this?


    
    

    
  
I believe the news-server in the original case, isn't responding to search at
all - it isn't compliant.

However: There are a few other problems, even if that server is horked.
When triggernig the search window from linux build 2001011021 i get this, before
i do anything else:

The root is mailsearch:#1
setMsgDatasourceWindow([xpconnect wrapped nsIRDFDataSource])
error setting DS on [xpconnect wrapped nsIRDFDataSource]: [Exception...
"Component returned failure code: 0x80004002 (NS_NOINTERFACE)
[nsIRDFDataSource.QueryInterface]"  nsresult: "0x80004002 (NS_NOINTERFACE)"
location: "JS frame :: chrome://messenger/content/SearchDialog.js ::
setMsgDatasourceWindow :: line 321"  data: no]
setMsgDatasourceWindow([xpconnect wrapped nsIRDFDataSource])
Selecting news://dark@news.cybercity.no/cybercity.help
id = news://dark@news.cybercity.no/cybercity.help
Setting search scope to 1
..on 0 elements.
Appended a searchattribute
Appended a searchoperator
Appended a searchvalue
createSearchRow: Setting searchScope = 1
Move window by 400,145.2
screen x 23screen y 199

    
    

    
  
it's just the particular server that's having the problem, and generates the
NNTP error. So, it's just likely broken. The java script error is a search front
end problem and beyond my limited comprehension. I don't think I see it when I
search, however.

    
    

    
  
Search messages on news which I've tried using jan12 commercial trunk build,
linux rh6.0 are all OK.  No hiccups, no hangs.  

Just an FYI: Remember folks, we have a known issue where only "contains" works,
all other operator choices don't work with news searches.  (bug 57034)

    
    

    
  
moving to mozilla0.9
Target Milestone: mozilla0.8 → mozilla0.9

    
    

    
  
marking nsbeta1-
Keywords: nsbeta1 → nsbeta1-
Whiteboard: [nsbeta1+] → [nsbeta1+ 1/25]
Target Milestone: mozilla0.9 → Future

    
    

    
  
Smells wfm here... Anyone able to reproduce this bug?

    
    

    
  
WFM 2001071806 Linux.

    
    

    
  
WFM 

Marking RESOLVED:WFM

OS: Linux
Moz Build: 2001071808 
User Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2+) Gecko/20010718
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME

    
    

    
  
Works for me with aug09 commercial trunk build, linux rh6.2
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey

    
  
Component: MailNews: Search → MailNews: Message Display
QA Contact: laurel → search

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






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: