Closed Bug 173963 Opened 23 years ago Closed 23 years ago

Icon of Mozilla.app appear to be a Classic Application

Categories

(SeaMonkey :: Build Config, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
mozilla1.3beta

People

(Reporter: jm-ambroise, Assigned: jj.enser)

References

Details

Icon of Mozilla.app build 2002101103 appear to be a Classic Application and a Command+I on the Icon show: type: Application Classic But it is a Mac OS X Application, not a Classic Application and when Mozilla is launch, it is a Mac OS X Application who is launched, not a Classic Application (Classic is not launched and not running) !!!! And Mozilla.app contain all the elements of the elements of Mac OS X Application of Mozilla. Funny no ????
reassign to jj for investigation.
Assignee: seawood → jj
Summary: Icon of Mozilla.app appear to be a Classic Application → Icon of Mozilla.app appear to be a Classic Application
Target Milestone: --- → mozilla1.3beta
What I see after downloading today's build is that the application has a *generic* application icon, instead of the "M" custom icon. Jean-Marie, is that what you mean by "classic app icon" ? Also, is today's the first build you see this? was yesterday's build ok? As to the Get info window, I see "Kind: Application", as expected. Aki, I believe this could be realted to your checkin of mozilla.plst . I took a look at the plst file in the build and it contains some binary data at the end, as I suspected and mentioned in bug 173355
Yes, I have a generic application instead of the "M" custom icon but when I make a get info on this icon, it's say me that this is a Classic Application, and there is a Memory field who not appear in a Carbon or Cocoa Application get info. And yes, I have already this problem with yesterday build. Thanks J.J. for your fast and good work !!! yeah.... I hope this problem will be resolved rapidly ;-))
For me, the Mozilla application displays the old Mozila icon it has on OS 9, but is still an OS X application.
It will be resolved soon: I already fixed my local copy. After "cleaning up" the Info.plst file (deleting the garbage binary data at the begining and the end of the file) and duplicating my mozilla folder, the duplicate copy displays the 32-bit icon as it should. Aki: disregard my last suggestion, you haven't checked in the file yet so it can't be you! Leaf: I now believe this problem is related to the fact that we removed the -kb options on that file, which seems to expose some binary data in the file that was previously ignored... or something like that. This should be resolved once Aki checks in the 1.2b version, without the garbage in it :-) creating bug dependency on 173355 Thanks for flagging this, Jean-Marie! Bonjour chez vous.
Status: UNCONFIRMED → NEW
Depends on: 173355
Ever confirmed: true
De rien J.J., Thanks and regards. Bye ;-))
I have modify the info.plist as you have made and it works fine !!! I have the great "M" Icon. Very good JJ ;-)))
*** Bug 174077 has been marked as a duplicate of this bug. ***
What's happen ? You have not fix this problem in the build 2002101303, you have just to "cleaning up" the Info.plist file in Mozilla.app (deleting the garbage binary data at the begining and the end of the file). I have done this on the file on my copy of Mozilla and it's works fine for me and as said J.J. What it's the problem for the builds you make ??? There is really a bug when the new build is make ;-((( I hope you solve this problem, it's really strange, "bizarre in French", no ????
An interesting side effect of this.... DragThing (which has a replacement for the dock, among other things) shows a badge in the lower left corner of running applications that are running in Classic. Mozilla shows the (9) badge in the corner as if it were a Classic app despite it not launching Classic to run it. This is obviously because of this bug, so whenever this gets checked in, it'll be fixed I'm sure. I'm using the 2002101009 build, and I get a generic folder icon rather than a generic application icon, but the rest of the symptoms are the same.
Confirming the same error in all recent OSX builds. Last week it was showing as a generic application; this week it is showing as a generic folder (bundle?).
This needs to be fixed far, far sooner than 1.3 beta.
Read my additionnal comment #9: As said JJ, you have just to "cleaning up" the Info.plist file in Mozilla.app (deleting the garbage binary data at the begining and the end of the file). I have done this on the file on my copy of Mozilla and it's works fine (you must quit your session in Mac OS X and relogin). That's all ;-)) The Info.plist file in new builds of Mozilla is still have the same problem, nobody at Mozilla can't modify this file ???? I don't understand ??? ;-((
Everybody calms down please. I've mentioned a dependency on 173355, which also related to the file mozilla.plst. Whenever Asasaki checks in the fix for 173355, which should happen real soon, it will automatically take care of this one. Please verify and/or comment here if you still see the problem _after_ 173355 has been fixed.
confirming: fix checked in as part of 173355 - and looks good. Marking fixed now. Please verify with tomorrow's nightly build (20021015)
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
yes, I confirm, the bug is resolved in build 2002101503. Yeah... ;-))
Thanks Jean-Marie. In the future, remember to change the bug status to "VERIFIED". (just above the 'submit' button. It helps organizing bugs. Doing so now.
Status: RESOLVED → VERIFIED
fixed on the MOZILLA_!_0_BRANCH
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.