«Another program wants to install» SeaMonkey default & Modern themes

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
6 years ago
6 years ago

People

(Reporter: tonymec, Unassigned)

Tracking

({regression})

Trunk
regression
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

+++ This bug was initially created as a clone of Bug #863300 +++

At first startup after a nightly upgrade, I get two new tabs,

"Another program wants to install an extension: SeaMonkey Modern theme" /usr/local/seamonkey/extensions/modern@themes.mozilla.org.xpi — and the same for SeaMonkey default, /usr/local/seamonkey/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi, in both cases with an unticked checkbox labeled (quoting from memory) "Allow this installation", a "Continue" button, and some text saying that I can at any time change my mind by going to the add-ons manager.

Ticking the checkbox then "Continue" enables the built-in theme in question, disabling my preferred third-party theme.
Clicking "Continue" with the checkbox left unticked leaves my third-party theme enabled.
In both cases, both built-in themes are visible in the add-ons manager afterwards.

See also bug 863300 comment #3 and #4.

I first saw this bug after installing the 2013-04-19 nightly built from comm-central changeset 7ec742c695b8 (upgrading from the previous nightly); I saw it again on the 2013-04-20 nightly built from comm-central changeset 27503b22e289 (upgrading from an hourly built on the same c-c changeset). Upgrading from the 2013-04-19 nightly to the hourly did not show the bug.

Comment 1

6 years ago
I think this is just fallout from bug 863300 and not a valid bug in itself. (When the Addons Manager loses track of the themes from the broken build, then finds them again on the next nightly, it thinks that the themes were installed by another program.)
(In reply to neil@parkwaycc.co.uk from comment #1)
> I think this is just fallout from bug 863300 and not a valid bug in itself.
> (When the Addons Manager loses track of the themes from the broken build,
> then finds them again on the next nightly, it thinks that the themes were
> installed by another program.)

Well, I saw this between two nightlies which were both shortly earlier than the fix for bug 863300 and also between an hourly and a nightly which were both newer, but not between an older nightly and a newer hourly. :-?
P.S. I'll keep this nightly (not replace it by an hourly), and if tomorrow the next nightly doesn't show the bug I suppose we can close this WFM. If it does, then this is a real bug.
P.P.S.
Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 SeaMonkey/2.20a1 ID:20130420003001 c-c:27503b22e289 m-c:dd03d42b01b1

Comment 5

6 years ago
> I think this is just fallout from bug 863300 and not a valid bug in itself. 
I agree. Under normal circumstances this won't happen at all.
Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 SeaMonkey/2.20a1 ID:20130421003001 c-c:1637ab8d5a01 m-c:0d50cb959c46

Problem has disappeared again. Both built-in themes are visible as expected in both "Appearance" and "Recent updates" tabs of the add-ons manager. => WFM
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.