Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Crashes on message filters

  • 2 replies
  • 1 has this problem
  • 16 views
  • Last reply by nubbix

nubbix
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.

Chosen solution

Do you have a crash ID?

https://support.mozilla.org/en-US/kb/Mozilla-Crash-Reporter#w_viewing-crash-reports

Read this answer in context 👍 0

All Replies (2)

christ1
christ1
  • Top 25 Contributor
more options

Chosen Solution

Do you have a crash ID?

https://support.mozilla.org/en-US/kb/Mozilla-Crash-Reporter#w_viewing-crash-reports

nubbix
nubbix Question owner
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