Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

Crashes on message filters

  • 2 Mbohovái
  • 1 oguereko ko apañuái
  • 1 Hecha
  • Mbohovái ipaháva 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.

Ñemoĩporã poravopyre

Do you have a crash ID?

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

Emoñe’ẽ ko mbohavái ejeregua reheve 👍 0

Opaite Mbohovái (2)

christ1
christ1
  • Top 25 Contributor
more options

Ñemoĩporã poravopyre

Do you have a crash ID?

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

nubbix
nubbix Porandu apoha
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