535758 - 'error occurred updating the button_next command' during TB 3.1a1pre startup

Status: RESOLVED WORKSFORME

(Thunderbird :: General, defect)

Description

[Valery Kondakoff]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2b5) Gecko/20091204 Firefox/3.6b5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a1pre) Gecko/20091217 Shredder/3.1a1pre

I'm receiving three following errors during TB startup:

Error: An error occurred updating the button_next command: TypeError: this._treeElement is undefined
Source File: chrome://global/content/globalOverlay.js
Line: 86

What may cause this? I see the same errors when trying to start TB in safe mode.

Reproducible: Always

Comment 1

[Joe Sabash [:JoeS1]]

In 20091215 Shredder/3.1a1pre I get 3 errors
button_previous, button_next, button_compact
All on startup.
But the buttons function normally.

Comment 2

[Nomis101]

This is also reported in Bug 533586.
I also see the same message on OS X for button_previous, button_next, button_compact after installing the iLeopard Mail Theme.

Comment 3

[bitmancer.bassplayer]

It's still there!

Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.6) Gecko/20091221 Shiretoko/3.5.6

An error occurred executing the button_next command
[Exception... "'[JavaScript Error: "SelectFolder is not defined" {file: "chrome://messenger/content/msgViewNavigation.js" line: 242}]' when calling method: [nsIController::doCommand]"  nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame :: chrome://global/content/globalOverlay.js :: goDoCommand :: line 86"  data: yes]

Comment 4

[Joe Sabash [:JoeS1]]

These errors are getting in the way of other bug triage.
Confirming in:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2pre) Gecko/20100122 Lanikai/3.1b1pre ID:20100122032008

Comment 5

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

Console errors probably don't want to be in 3.1 final?

Comment 6

[Dan Mosedale (:dmosedale, :dmose)]

Indeed, we'd like them to be gone, but this isn't so bad that we'd hold the release if it were the last bug standing.

Comment 7

[Wayne Mery (:wsmwk)]

came across this in a posting that confuses the poster

Comment 8

[Wayne Mery (:wsmwk)]

IS this and bug 533586 still seen?

Comment 9

[Nomis101]

(In reply to Wayne Mery (:wsmwk, NI for questions) from comment #8)
> IS this and bug 533586 still seen?

I can see some errors, but not this specific one described here anymore.

Comment 10

[Wayne Mery (:wsmwk)]

Nomis101, thanks. WFM per comment 9.