keySequence is undefined

[tailgate89]

Ever since I upgraded to Zimbra 2.0, I've encountered problems. The most recent, I keep getting the same message keySequence is undefined. This recent problem has really hamstrung my email usage. Please advise.

[jmhe]

can you attach a screenshot? and steps to reproduce this problem? thanks.

[tailgate89]

Screen shot attached. Not much to say on steps...I open my email and whenever I try to click on any of the top tabs (minus mail or calendar - at times), I receive the error message.

[phoenix]

Originally Posted by tailgate89

Screen shot attached. Not much to say on steps...I open my email and whenever I try to click on any of the top tabs (minus mail or calendar - at times), I receive the error message.

Do you have any anti-virus/spyware/malware blocker running that may be interfering with ZD?

[tailgate89]

Since I have Zimbra Desktop on both my home and work cpu and have two completely different anti-virus running on both cpus and the same error is occurring, it may be safe to rule that out.

[phoenix]

Originally Posted by tailgate89

Since I have Zimbra Desktop on both my home and work cpu and have two completely different anti-virus running on both cpus and the same error is occurring, it may be safe to rule that out.

You may be correct but what about trying it with the a/v disabled just to make sure? You also haven't provided any details of which operating system is used nor whether it's a 32bit or 64bit system.

[tailgate89]

Tried shutting off a/v, same error appeared. Running 32bit. Windows xp

[tailgate89]

msg: this.__keySequence is undefined
fileName: http://127.0.0.1:1088/zimbra/js/Star...v=101011163938
lineNumber: 8763
message: this.__keySequence is undefined
name: TypeError
stack: ()@http://127.0.0.1:1088/zimbra/js/Startup1_1_all.js?v=101011163938:8763 ("TV",(void 0))@http://127.0.0.1:1088/zimbra/js/Startup1_2_all.js?v=101011163938:17215 ("COMPOSE2")@http://127.0.0.1:1088/zimbra/js/Startup1_2_all.js?v=101011163938:16930 ([object Object])@http://127.0.0.1:1088/zimbra/js/Startup1_2_all.js?v=101011163938:19008 ([object Object])@http://127.0.0.1:1088/desktop/login.jsp?at=ae7b1e27-b840-4390-9e5b-c4b1d5c5514b:675 ([object Object])@http://127.0.0.1:1088/zimbra/js/Startup1_1_all.js?v=101011163938:3098 ("SELECTION",[object Object])@http://127.0.0.1:1088/zimbra/js/Startup1_1_all.js?v=101011163938:2937 ("SELECTION",[object Object])@http://127.0.0.1:1088/zimbra/js/Startup1_1_all.js?v=101011163938:9676 ([object Object])@http://127.0.0.1:1088/zimbra/js/Startup1_2_all.js?v=101011163938:10600 ([object Object])@http://127.0.0.1:1088/desktop/login.jsp?at=ae7b1e27-b840-4390-9e5b-c4b1d5c5514b:675 ([object Object])@http://127.0.0.1:1088/zimbra/js/Startup1_1_all.js?v=101011163938:3098 ("SELECTION",[object Object])@http://127.0.0.1:1088/zimbra/js/Startup1_1_all.js?v=101011163938:2937 ("SELECTION",[object Object])@http://127.0.0.1:1088/zimbra/js/Startup1_1_all.js?v=101011163938:9676 ([object Object])@http://127.0.0.1:1088/zimbra/js/Startup1_1_all.js?v=101011163938:13407 ([object Object])@http://127.0.0.1:1088/zimbra/js/Startup1_1_all.js?v=101011163938:13534 ([object Object])@http://127.0.0.1:1088/desktop/login.jsp?at=ae7b1e27-b840-4390-9e5b-c4b1d5c5514b:675 ([object Object])@http://127.0.0.1:1088/zimbra/js/Startup1_1_all.js?v=101011163938:3098 ("onmouseup",[object Object])@http://127.0.0.1:1088/zimbra/js/Startup1_1_all.js?v=101011163938:2937 ("onmouseup",[object Object])@http://127.0.0.1:1088/zimbra/js/Startup1_1_all.js?v=101011163938:9676 ([object MouseEvent],"onmouseup",[object Object],[object Object])@http://127.0.0.1:1088/zimbra/js/Startup1_1_all.js?v=101011163938:10663 ([object MouseEvent],[object Object],[object Object])@http://127.0.0.1:1088/zimbra/js/Startup1_1_all.js?v=101011163938:10595 ([object MouseEvent])@http://127.0.0.1:1088/zimbra/js/Startup1_1_all.js?v=101011163938:10545

[jmhe]

it's this bug and we just fixed it for coming 2.0.1 release;

https://bugzilla.zimbra.com/show_bug.cgi?id=53138

[tailgate89]

Thats great news.....so when in 2.0.1 release?