Ambassador 1.0.0 Error Console.

Board for discussions around the Ambassador chat client and extension.

Moderator: Isengrim

Locked
Latitude
Banned user
Banned user
Posts: 597
Joined: 2016-03-21, 18:28

Ambassador 1.0.0 Error Console.

Post by Latitude » 2018-09-18, 14:10

Is this normal?

Image

It is the startup time.
Last edited by Latitude on 2018-09-18, 14:11, edited 1 time in total.

User avatar
New Tobin Paradigm
Knows the dark side
Knows the dark side
Posts: 7516
Joined: 2012-10-09, 19:37
Location: Just beyond the Lament Configuration

Re: Ambassador 1.0.0 Error Console.

Post by New Tobin Paradigm » 2018-09-18, 15:31

It isn't a problem. Let's hope you don't create a third thread for Pale Moon... This is bordering on spam.
Last edited by New Tobin Paradigm on 2018-09-18, 15:31, edited 1 time in total.
Image
- Welcome to the worst nightmare of all... reality! -

User avatar
Isengrim
Board Warrior
Board Warrior
Posts: 1209
Joined: 2015-09-08, 22:54
Location: 127.0.0.1
Contact:

Re: Ambassador 1.0.0 Error Console.

Post by Isengrim » 2018-09-18, 16:26

Latitude wrote:Is this normal?
Yes.

To elaborate, some parts of ChatZilla were designed to integrate with SeaMonkey, and Ambassador still has a few of those pieces in place. They don't currently do anything, but they get loaded and in turn attempt to load a browser file that doesn't exist.

I'm not sure what the other message means, and I can't find any broken functionality that would point to what causes it.
Linux Mint 19.3 Cinnamon (64-bit), Debian Bullseye (64-bit), Windows 7 (64-bit)
"As long as there is someone who will appreciate the work involved in the creation, the effort is time well spent." ~ Tetsuzou Kamadani, Cave Story

User avatar
New Tobin Paradigm
Knows the dark side
Knows the dark side
Posts: 7516
Joined: 2012-10-09, 19:37
Location: Just beyond the Lament Configuration

Re: Ambassador 1.0.0 Error Console.

Post by New Tobin Paradigm » 2018-09-18, 16:31

Do this:
http://xref.palemoon.org/uxp-trunk/source/application/palemoon/themes/windows/moz.build
http://xref.palemoon.org/uxp-trunk/source/application/palemoon/themes/windows/communicator/

That will fix the two chrome package issues.. As for not finding the default skin chrome.manifest.. Ignore it.
Last edited by New Tobin Paradigm on 2018-09-18, 16:34, edited 4 times in total.
Image
- Welcome to the worst nightmare of all... reality! -

Locked