Re: Bug report: Balsa closing unexpectedly after receiving mail

[Francisco Ortiz Santini <ortizsantini prtc net>]

On 2003.09.26 11:15, Emmanuel Allaud wrote:
> OK thank you it will enable us to trace the problem more efficiently.

Ok, I have tried Balsa several times, always starting from the console  
with the --sync option. So far, I haven't received exactly the previous  
odd behavior, but variances of the same. Here they are so far:

1. The "HtmlCss-WARNING" messages always appear immediately I request  
Balsa to check for new messages. If there are no new messages to  
download, Balsa continues to operate normally. Indeed, if I command  
Balsa to check again for new messages the warnings do not repeat  
itselves.
2. On several occasions Balsa segfaulted. When that happened, the input  
was the following (additional spaces between warnings deleted to save  
space):
-------------------------------------------------------------------------------------------------------------
[francisco@localhost francisco]$ balsa --sync
opening Correo..
N_decl is: 5
(balsa:7940): HtmlCss-WARNING **: Unhandled property: 353 tab-interval
(balsa:7940): HtmlCss-WARNING **: Unhandled property: 80 page
(balsa:7940): HtmlCss-WARNING **: Unhandled property: 319 mso-style- 
parent
(balsa:7940): HtmlCss-WARNING **: Unhandled property: 320 mso- 
pagination
(balsa:7940): HtmlCss-WARNING **: Unhandled property: 322 mso-fareast- 
font-family
(balsa:7940): HtmlCss-WARNING **: Unhandled property: 323 mso-fareast- 
language
(balsa:7940): HtmlCss-WARNING **: Unhandled property: 345 mso-style- 
name
(balsa:7940): HtmlCss-WARNING **: Unhandled property: 348 mso-gram-e
(balsa:7940): HtmlCss-WARNING **: Unhandled property: 345 mso-style- 
name
(balsa:7940): HtmlCss-WARNING **: Unhandled property: 346 mso-spl-e
(balsa:7940): HtmlCss-WARNING **: Unhandled property: 319 mso-style- 
parent
(balsa:7940): HtmlCss-WARNING **: Unhandled property: 320 mso- 
pagination
(balsa:7940): HtmlCss-WARNING **: Unhandled property: 322 mso-fareast- 
font-family
(balsa:7940): HtmlCss-WARNING **: Unhandled property: 323 mso-fareast- 
language
Xlib: unexpected async reply (sequence 0xbcfa)!
(balsa:7940): Gtk-CRITICAL **: file gtkstyle.c: line 669  
(gtk_style_finalize): assertion `style->attach_count == 0' failed
[francisco@localhost francisco]$
---------------------------------------------------------------------------------------------------------------

3. On other occasions, Balsa just friezed while downloading new  
messages and I was forced to kill it after waiting for more than five  
minutes. Here is the input:

-------------------------------------------------------------------------------------------------------
[francisco@localhost francisco]$ balsa --sync
opening Correo..
N_decl is: 5
 (balsa:7592): HtmlCss-WARNING **: Unhandled property: 353 tab-interval
(balsa:7592): HtmlCss-WARNING **: Unhandled property: 80 page
(balsa:7592): HtmlCss-WARNING **: Unhandled property: 319 mso-style- 
parent
(balsa:7592): HtmlCss-WARNING **: Unhandled property: 320 mso- 
pagination
(balsa:7592): HtmlCss-WARNING **: Unhandled property: 322 mso-fareast- 
font-family
(balsa:7592): HtmlCss-WARNING **: Unhandled property: 323 mso-fareast- 
language
(balsa:7592): HtmlCss-WARNING **: Unhandled property: 345 mso-style- 
name
(balsa:7592): HtmlCss-WARNING **: Unhandled property: 348 mso-gram-e
(balsa:7592): HtmlCss-WARNING **: Unhandled property: 345 mso-style- 
name
(balsa:7592): HtmlCss-WARNING **: Unhandled property: 346 mso-spl-e
 (balsa:7592): HtmlCss-WARNING **: Unhandled property: 319 mso-style- 
parent
(balsa:7592): HtmlCss-WARNING **: Unhandled property: 320 mso- 
pagination
(balsa:7592): HtmlCss-WARNING **: Unhandled property: 322 mso-fareast- 
font-family
(balsa:7592): HtmlCss-WARNING **: Unhandled property: 323 mso-fareast- 
language
The program 'balsa' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for  
operation)'.
  (Details: serial 36044 error_code 2 request_code 55 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error()  
function.)
Killed
[francisco@localhost francisco]$
----------------------------------------------------------------------------------------------------------

4. On this particular occasion when Balsa friezed, and before killing  
it, I noticed that all 9 messages downloaded were reported in my  
"Correo" mailbox (that's my Inbox renamed to Spanish). When I started  
Balsa again, some messages were distributed in several mailboxes by the  
filters, but those pesky worm messages about "Microsoft critical  
patches" etc. remained in the Inbox. It appears to me that the friezing  
occured while Balsa was trying to distribute the massages with the  
filters, although the worm messages might not be filtered because the  
nasty guy sending them is always changing the sender or the subject.

I really hope this report helps for something. Let me know if anything  
else is needed.

Francisco