Closed Bug 40590 Opened 24 years ago Closed 24 years ago

Sidebar panels do not show

Categories

(SeaMonkey :: Sidebar, defect, P3)

PowerPC
Mac System 8.5
defect

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: amusil, Assigned: slamm)

Details

Download and launch todays build (05252000).

Sidebar panels are blank.
Keywords: dogfood, smoketest
I ran the Mac installer, but it dies right when it tries to extract the files.
I downloaded the entire package instead, and I see the Sidebar panels. However,
the panels with chrome URLs fail to load is that what you are seeing?
No, I'm just getting a large blank space with no tabs at all.  Could just be a 
bad installer?
working fine for me.
It isn't a smoketest blocker if the smoketesters don't see it, or if it's a
result of bad packaging (or, in this case, some combination).
Keywords: smoketest
So we don't hold the tree closed for bad packaging?  What does QA use to test 
with for these verification builds?
shrir - so are you seeing the buddy list panel show up in the sidebar as well?  
How about the IM icon on the task bar?
Yes, I can see it the buddy list panel in the Sidebar. But I do not see IM icon 
on taskbar.
shrir - did you use the installer?
nope. I used the netscape6-mac.sea.bin file
Can you test this with the installer?  Is there a particular reason you didn't 
use the installer - seems like we should be using that for all smoketests, right?
Alex, I usually use the installer for my testing. But with bug 39749 present, I 
did not use it. All smoketesters (browser group) do use the installer for 
smoketesting. I tried the installer for today's build, but it is not working on 
my machine. I will give it a try again (with different settings) and see if it 
works .Thnx.
ok, I have this working in my local build now that I pulled.  guess it's just an 
installer problem that really sucks.

Marking invalid.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
vrfy
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.