Open Bug 98519 Opened 23 years ago Updated 13 years ago

Skip over local panels that don't exist

Categories

(SeaMonkey :: Sidebar, defect)

defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: bclinger, Unassigned)

References

()

Details

(Whiteboard: [dyn-list])

Attachments

(1 file)

The build:  2001090603 and the one before it - while the program is loading, an
error message indicating the AOL sidebar file is missing is displayed. This
occurs every time the program is started. As a note, I have the mail and browser
functions set to come on when the program begins.
--> sgehani
Assignee: matt → sgehani
what "program" are you talking about?  NS 6?  Mozilla?  Are you sharing a
profile between the two?
Mozilla, build number 2001090603 - and it's an AIM sidebar message. This error
message has been received with this and the last build. It's on two systems, the
other three have not had these two builds installed. On one system the profiles
are shared with 6.1 and on the 2nd, 6.1 was taken off. It is consistent, occurs
every time the program begins.
can we get reproducible steps ?
Sure. Just start the program up and the error message is displayed - every time.
It even shows up in this release,2001090603.
Ben 
Well, more investigation on this has been done and gosh, it's different! So, in
order to reproduce it, do the following stuff. #1 in the preference setup, click
on "appearance" then click on the Navigator & Mozilla Mail boxes, then save it.
#2, close the browser (really stressful). #3, start the program up and see the
error message jump out and say it's missing the xul file (or something like
that). This error has been displayed for this and the last 2 builds. Ben
I cannot reproduce this. Here is what I did:

1) launch netscape(new profile)
2) went in Edit |Preferences | Appearance and enabled Netscape and Mail  
3) click OK on the Pref panel
4) exit/quit browser
5) re-launch

I see the sidebar open in both mail and browser and I do not see
any XUL error message panel.

I was using 9/7 windows build.  
When both are marked and the program restarted, below is the exact message recieved

The error message I am receiving is:
/C:/PROGRAM%20FILES/NETSCAPE/MOZNIGHTLY/BIN/chrome/packages/aim/SidebarPanel.xul
cannot be found. Please check the location and try again.

Now, the file is not on the machine. This also appears with build 2001090603. If
there is a missing file, how about sending it as a file attachment? or making it
available as a download. My next step is to create a bogus file and see what
happens.


Re build 2001090603 and last several releases:

I created a text file, named it SidebarPanel.xul and stuck it in the
.../packages/aim folder, and gosh, the message did not appear. As a note, the
.../pacakages/aim folder did not exist.

S/NETSCAPE/MOZNIGHTLY/BIN/chrome/packages/aim/SidebarPanel.xu
                                 ------------
                                 Does not appear - had to be created.

Now, I've been downloading the "talback" zip file. Would it be better to
download another, such as the installer file? One previous version of the
"installer" file did not allow me to specify the destination folder.
Now, after restarting it, I noticed the error message is gone. However, there
still remains a problem or two. Again, the Mozilla Mail and Navigator are marked
and it'll open only the mail segment as a small window on the upper left of the
screen; the Navigator module does not open up at all. This is consistent with
the previous builds and with the current build just downloaded, 2001090603. As a
result, 2001090603 has been deleted and replaced with an earlier build.
bclinger, are you installing a mozilla build or a commercial build?

also looks like you're saying the Mail window comes up, but the
browser window doesn't come up because of that error message..
is that correct?
The Mozilla build is being installed. With that error message, only the mail
window comes up, the browser window does not. The error message indicates a file
is being looked for and by creating a "dummy file" with the name wanted and
putting in the indicated folder, the error message does not occur and the
program functions normally.
Asa, can you try this out on Mozilla build? thanks.
I suspect this is something about sharing a profile with a Netscape release. AIM
sidebar stuff isn't in Mozilla code. I cannot reproduce. Reporter, is this a
problem on a clean profile?
Well, it's still in this one. I routinely delete the newly created profiles - I
am using the old ones. Hang loose and I'll create a new one. Also as a note, you
gotta have both the Mozilla Mail and Navigator boxes marked in order to get da
message.
BRB
Well, after testing, it appears to happen only with "old" or "existing"
profiles. Newly created profiles created with this build, number 2001091303 are
working just fine. Existing profiles gotta have the file
...\new\chrome\Packages\aim\SidebarPanel.xul.
What I have in the SidebarPanel\xul file is:

The error message I am receiving is:
/C:/PROGRAM%20FILES/NETSCAPE/MOZNIGHTLY/BIN/chrome/packages/aim/SidebarPanel.xu
cannot be found. Please check the location and try again.

So, it appears the file it is looking for, SidebarPanel.xul is just a plain ole
text file.
I get the message when I start using a Shortcut containg
"F:\mozilla.org\Mozilla\mozilla.exe -mail" .

In response to: Additional Comments From Asa Dotzler 2001-09-13 22:55, I
searched for "sidebarpanel" string in my user profile, and found the following
lines in
file C:\Windows\Application
Data\Mozilla\Profiles\jones.peter\ce8o6fvh.slt\panels.rdf :

 <RDF:Description about="urn:sidebar:panel:im-panel"
                   NC:title="Buddy List"
                   NC:content="chrome://aim/content/SidebarPanel.xul" />

(There were noise hits in the Cache directory resulting from my searching the
bug database for the message text.)
  
I propose to change "aim" to "communicator" and see what happens. I'll do that
using in Edit in Binary mode to avoid inserting carriage returns in the file.
There seemed to be only four returns in the file I downloaded, which has a
creation date of August 15, 2001.

My patch worked! Suggest marking this as Resolved. I don't have the privilege.


To summarize:

1. Open the
C:\Windows\Application Data\Mozilla\Profiles\<username>\ce8o6fvh.sltpanels.rdf
file in Edit, using Binary mode.

2. Correct the third line: *

   <RDF:Description about="urn:sidebar:panel:im-panel"
             NC:title="Buddy List"
-            NC:content="chrome://aim/content/SidebarPanel.xul" />
+            NC:content="chrome://communicator/content/SidebarPanel.xul" />

* Because Edit/Binary fills the screen with consecutive characters including CR
and LF, you won't actually see the text laid out as above. I've also shifted the
"NC" lines left a bit for display purposes. No need to actually do that when
actually patching the file.


Additional note: When this bug hit me, the mail folder that I normally have open
closed itself, and I wondered if I had lost my mail. However, when I reopened
the folder, I saw my mail files with question marks being replaced with message
counts. Whew!

The root of the problem is that we should stat local panel files and skip them
or remove them from the panels.rdf datasource if they don't exist.  Changing
summary to reflect problem and taking for 0.9.6.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Priority: -- → P2
Summary: During the initiation process an error message indicating problem with sidebar is displayed → Skip over local panels that don't exist
Target Milestone: --- → mozilla0.9.6
This is one of the problems being addressed by the proposal (still under
construction) at:
<http://mozilla.org/xpapps/sidebar/proposals/dyn-list.html>
Moving to mozilla0.9.7.
Whiteboard: [dyn-list]
Target Milestone: mozilla0.9.6 → mozilla0.9.7
*** Bug 110446 has been marked as a duplicate of this bug. ***
[dyn-list] bugs -> mozilla0.9.8
Target Milestone: mozilla0.9.7 → mozilla0.9.8
Target Milestone: mozilla0.9.8 → mozilla0.9.9
-> mozilla1.0
Priority: P2 → P3
Target Milestone: mozilla0.9.9 → mozilla1.0
Transferring nsbeta1 nomination from bugscape 11973.
Keywords: nsbeta1
nsbeta1- per ADT triage team
Keywords: nsbeta1nsbeta1-
Target Milestone: mozilla1.0 → mozilla1.2
*** Bug 121940 has been marked as a duplicate of this bug. ***
*** Bug 211122 has been marked as a duplicate of this bug. ***
*** Bug 214499 has been marked as a duplicate of this bug. ***
*** Bug 144095 has been marked as a duplicate of this bug. ***
*** Bug 159284 has been marked as a duplicate of this bug. ***
*** Bug 246465 has been marked as a duplicate of this bug. ***
The missing SidebarPanel.xul message is displayed when installing the BASE 
version of Netscape 7.2 which does not include the "Component Instant 
Messenger" (NIM.xpi) or when creating a custom install and not including it.

The missing file is located in the AIM.JAR in the NIM.XPI file. 
Product: Browser → Seamonkey
Assignee: samir_bugzilla → nobody
Status: ASSIGNED → NEW
Priority: P3 → --
QA Contact: sujay → sidebar
Target Milestone: mozilla1.2alpha → ---
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
Still valid.
Unfortunately, the URL is 404 by now.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows ME → All
Hardware: x86 → All
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: