1392824 - [10.13] Firefox Dock icon defaults to System Icon

Status: RESOLVED DUPLICATE of bug 493503

(Core :: Widget: Cocoa, defect, P2)

Description

[Marcia Knous [:marcia]]

Attachment: Screenshot of what should be the Firefox icon using 10.13

Might be 10.13 specific (running B7), using Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:55.0) Gecko/20100101 Firefox/55.0, 20170814073321

STR:
1. Running 54.0.1, perform a manual update to 55
2. Update downloads, see attached screenshot

I rebooted my system and restarted the browser several times, but the icon remains.

A quick test using 10.12.6 and I did not see the same issue.

Comment 1

[Marcia Knous [:marcia]]

Adding Markus in case he has some ideas.

Comment 2

[Markus Stange [:mstange]]

I don't have any ideas. We may need to reach out to Apple for this.

Comment 3

[Marcia Knous [:marcia]]

Before I reach out to Apple, Andrei can you confirm you see the same thing using Beta 7 on your 10.13 test machine?

Comment 4

[Alexandru Simonca [:asimonca], Release Desktop QA]

Hello Marcia,
I tried reproducing this issue but I did not get the same result. I have a 2017 MacBook Pro with touchbar and macOS 10.13 Beta 7 installed. I installed 54.0.1 and then updated it from "about". The icon is not changed.
I have a screenshot here: http://imgur.com/a/A43NF

Comment 5

[Marcia Knous [:marcia]]

Unfortunately, I am now seeing this with Beta as well, updating from Beta 5 to Beta 6.

Comment 6

[Jim Mathies [:jimm]]

ni to spohl to see if he has any ideas. also moving to shell int.

Comment 7

[Stephen A Pohl [:spohl]]

Funky things have happened with macOS' icon cache before. Does this reproduce if Firefox is not kept in the Dock, close Firefox and reopen?

If you can still reproduce, it would be interesting to see what happens when the icon cache is cleared. There are some instructions on how to do this here:
https://apple.stackexchange.com/questions/225024/reset-icon-cache-on-macbook

Comment 8

[Marcia Knous [:marcia]]

I have not seen this since the report. For now I will close as WFM, but I will keep on eye on things as we progress on this new OS.

Comment 9

[Marcia Knous [:marcia]]

This cropped up again in Beta 10, reopening for now.

Comment 10

[Stephen A Pohl [:spohl]]

Could you run through the suggestion in comment 7 and let me know what happens?

Comment 11

[Marcia Knous [:marcia]]

When I try to run that command in Terminal I get "Operation not permitted (it does ask for my password). I also tried rebooting my machine and the icon that shows for Beta is still the system icon.

Comment 12

[Marcia Knous [:marcia]]

(In reply to Marcia Knous [:marcia - use ni] from comment #11)
> When I try to run that command in Terminal I get "Operation not permitted
> (it does ask for my password). I also tried rebooting my machine and the
> icon that shows for Beta is still the system icon.

Looks as if https://gist.github.com/fabiofl/5873100 has some information on how to work around this error.

Comment 13

[Stephen A Pohl [:spohl]]

Did https://gist.github.com/fabiofl/5873100#gistcomment-2232236 fix the issue for you?

Comment 14

[Marcia Knous [:marcia]]

(In reply to Stephen A Pohl [:spohl] from comment #13)
> Did https://gist.github.com/fabiofl/5873100#gistcomment-2232236 fix the
> issue for you?

Haven't tried yet - will later tonight after my work day is done.

Comment 15

[Marcia Knous [:marcia]]

(In reply to Stephen A Pohl [:spohl] from comment #13)
> Did https://gist.github.com/fabiofl/5873100#gistcomment-2232236 fix the
> issue for you?

Yes, it did work. I rebooted and the beta icon is back.

Comment 16

[Marcia Knous [:marcia]]

But after doing a Mac system update to Version 4, as well as a Beta update, the issue is back. So even if resetting the icon cache worked once, it hasn't fully resolved the issue.

Comment 17

[Marcia Knous [:marcia]]

[Tracking Requested - why for this release]: Not sure we can do much about this, but nominating in case we want to investigate this further. We also haven't had any other reports of this, so wondering what is unique about my setup that might be causing it if it is an aberration.

Comment 18

[Stephen A Pohl [:spohl]]

This is known to affect people who test numerous different versions of Firefox in a disproportionate number. There is a lot of interaction between the icon cache, bundle identifiers, us changing icons for the same bundle identifiers etc that can cause this issue. Most users are not expected to ever run into it since they only run one channel of Firefox at any given time.

Comment 19

[Marcia Knous [:marcia]]

(In reply to Stephen A Pohl [:spohl] from comment #18)
> This is known to affect people who test numerous different versions of
> Firefox in a disproportionate number. There is a lot of interaction between
> the icon cache, bundle identifiers, us changing icons for the same bundle
> identifiers etc that can cause this issue. Most users are not expected to
> ever run into it since they only run one channel of Firefox at any given
> time.

Based on this, I will withdraw my tracking nom.

Comment 20

[Eric Rescorla (:ekr)]

Hmm.... I don't think this is a matter of running a lot of versions of Firefox. I hacven't run !Nightly in quite some time (Weeks?) and it just happened on update.

Comment 21

[Joe Hildebrand [:jhildebrand] (UTC-6)]

ekr is in a state similar to me when I had this issue.  His app is "/Applications/FirefoxNightly.app", with no space.  Fresh installs go into a directory that does have a space.  Perhaps this is unrelated except for timing.

I've also NI'd Asa, since I know he's fielded questions from several users with this issue.

Comment 22

[Stephen A Pohl [:spohl]]

This will be addressed by bug 493503. See bug 493503 comment 16.

Comment 23

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

Seeing this in 61.0a1 (2018-04-11) (64-bit) on 10.13.4 when I updated this morning. If bug 493503 is fixing this, can this be resolved as a dupe?

Comment 24

[Stephen A Pohl [:spohl]]

(In reply to Emma Humphries, Bugmaster ☕️ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #23)
> Seeing this in 61.0a1 (2018-04-11) (64-bit) on 10.13.4 when I updated this
> morning. If bug 493503 is fixing this, can this be resolved as a dupe?

Yes, let's do that.