We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Crashes on message filters

  • 2 majibu
  • 1 ana tatizo hili
  • 1 view
  • Last reply by nubbix

more options

2014-04-25 03:04:38 gloda.datastore ERROR got error in _asyncTrackerListener.handleError(): 19: constraint failed

Time: 25.04.2014 03:11:40 Error: 2014-04-25 03:11:40 gloda.datastore ERROR got error in _asyncTrackerListener.handleError(): 19: constraint failed

Sourcefile: resource:///modules/gloda/log4moz.js Linje: 688

I get these messages in my debugger both on safe mode and in normal start. I get this when I try to open "message filters" selecting my custom SPAM rule and pressing "edit" Thunderbird halts and shutsdown! When I start it is in default state!

Latest versjon installed.

2014-04-25 03:04:38 gloda.datastore ERROR got error in _asyncTrackerListener.handleError(): 19: constraint failed Time: 25.04.2014 03:11:40 Error: 2014-04-25 03:11:40 gloda.datastore ERROR got error in _asyncTrackerListener.handleError(): 19: constraint failed Sourcefile: resource:///modules/gloda/log4moz.js Linje: 688 I get these messages in my debugger both on safe mode and in normal start. I get this when I try to open "message filters" selecting my custom SPAM rule and pressing "edit" Thunderbird halts and shutsdown! When I start it is in default state! Latest versjon installed.

All Replies (2)

more options

Suluhisho teule

more options

Hi, no I have not

But it seems to be fixed now, I will file a new ticket if the problem re-emerges