https://blog.seamonkey-project.org/2023/08/04/seamonkey-2-53-17-is-out/
--
"On the last and greatest day of the Feast, Jesus stood and said in a loud voice, 'If anyone is thirsty, let him come to me and drink. Whoever believes in me, as the Scripture said, streams of living water will flow from within him.'" --John 7:37-38. ST:SNW S2 E9 was amusing.
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant wrote:
> https://blog.seamonkey-project.org/2023/08/04/seamonkey-2-53-17-is-out/
>

Thank you Jesus!

Ant wrote:
> https://blog.seamonkey-project.org/2023/08/04/seamonkey-2-53-17-is-out/
>

Did the update here. Patched PrefBar as noted elsewhere before opening it.

I had hopes that it would have fixed the two websites that I need to use
FireFox for at present, but that was not the case. They are:

https://secure07b.chase.com/#/dashboard/overviewAccounts/overview/index
https://cherokeemetro.org/customer-service/billing/

In both cases I get a spinner in SeaMonkey that never stops. I do need
to use PrefBar to set a FireFox 102 UA for Chase to even get that far.

If anyone can get anywhere with either website in SeaMonkey I would like
to know how to do so.

Dave

On 4 Aug 2023 at 03:53:07 CEST, "Ant" <Ant> wrote:

> https://blog.seamonkey-project.org/2023/08/04/seamonkey-2-53-17-is-out/

Great! I'm so happy the contacts from macOS are working again :-)

David H Durgee wrote on 7/8/23 5:45 am:
> Ant wrote:
>> https://blog.seamonkey-project.org/2023/08/04/seamonkey-2-53-17-is-out/
>>
> Did the update here. Patched PrefBar as noted elsewhere before
> opening it.
>
> I had hopes that it would have fixed the two websites that I need to
> use FireFox for at present, but that was not the case. They are:
>
> https://secure07b.chase.com/#/dashboard/overviewAccounts/overview/index

I don't have a Chase acct so couldn't go any further than their System
Requirement page.

Is this what you got, David??

> https://cherokeemetro.org/customer-service/billing/

With this one, I got 'Done' at the bottom of the screen with a rotating
arrow thingee in mid screen ..... until I clicked View -> Use Style ->
None .... which at least got me to a page with what looked like
clickable links but they didn't take me anywhere.

> In both cases I get a spinner in SeaMonkey that never stops. I do
> need to use PrefBar to set a FireFox 102 UA for Chase to even get
> that far.
>
> If anyone can get anywhere with either website in SeaMonkey I would
> like to know how to do so.
>
> Dave
--
Daniel

Daniel65 wrote:
> David H Durgee wrote on 7/8/23 5:45 am:
>> Ant wrote:
>>> https://blog.seamonkey-project.org/2023/08/04/seamonkey-2-53-17-is-out/
>>>
>> Did the update here.  Patched PrefBar as noted elsewhere before
>> opening it.
>>
>> I had hopes that it would have fixed the two websites that I need to
>> use FireFox for at present, but that was not the case.  They are:
>>
>> https://secure07b.chase.com/#/dashboard/overviewAccounts/overview/index
>
> I don't have a Chase acct so couldn't go any further than their System
> Requirement page.
>
> Is this what you got, David??
>

I get that if I use the real UA. If I use PrefBar to set FF102 I get
the spinner and nothing further.

> > https://cherokeemetro.org/customer-service/billing/
>
> With this one, I got 'Done' at the bottom of the screen with a rotating
> arrow thingee in mid screen ..... until I clicked View -> Use Style ->
> None .... which at least got me to a page with what looked like
> clickable links but they didn't take me anywhere.

Will try and see if that gets me any further.

>
>> In both cases I get a spinner in SeaMonkey that never stops.  I do
>> need to use PrefBar to set a FireFox 102 UA for Chase to even get
>> that far.
>>
>> If anyone can get anywhere with either website in SeaMonkey I would
>> like to know how to do so.
>>
>> Dave

Thanks for taking a look. Hopefully someone with a Chase account will
be able to see if they can get it working.

Dave

On 8/3/23 21:53, Ant wrote:
> https://blog.seamonkey-project.org/2023/08/04/seamonkey-2-53-17-is-out/

After unpacking the tarball I did a test launch
in Suse-Leap-15.5 and got this

------------------------------
../seamonkey
(seamonkey:3808): Gtk-WARNING **: 09:03:33.149: Theme parsing error:
gtk-contained.css:32:432: negative values are not allowed.
(seamonkey:3808): Gtk-WARNING **: 09:03:33.163: Theme parsing error:
gtk-contained.css:1512:157: Unit is missing.
(seamonkey:3808): Gtk-WARNING **: 09:03:33.833: Theme parsing error:
gtk-contained.css:32:432: negative values are not allowed.
(seamonkey:3808): Gtk-WARNING **: 09:03:33.846: Theme parsing error:
gtk-contained.css:1512:157: Unit is missing.
------------------------------

Don't know if it matters much, just wanted to note it.
(NB. I intend to use it first under UbuntuStudio)

--
Every day of the week I boot a different (Linux) OS. Provisionally for
each system /home/userMe is a link to a directory on a remote data
drive. My email client Sylpheed has a link in every /home/userMe
directory pointing to a single directory on another remote data drive. I
nominate Sylpheed for the Nobel prize of Compuke-Conviviality and expect
every one of my OS'es and apps to behave this way or soon be gone from
my computer.

bad sector wrote:
> On 8/3/23 21:53, Ant wrote:
>> https://blog.seamonkey-project.org/2023/08/04/seamonkey-2-53-17-is-out/
>
> After unpacking the tarball I did a test launch
> in Suse-Leap-15.5 and got this
>
> ------------------------------
> ./seamonkey
> (seamonkey:3808): Gtk-WARNING **: 09:03:33.149: Theme parsing error:
> gtk-contained.css:32:432: negative values are not allowed.
> (seamonkey:3808): Gtk-WARNING **: 09:03:33.163: Theme parsing error:
> gtk-contained.css:1512:157: Unit is missing.
> (seamonkey:3808): Gtk-WARNING **: 09:03:33.833: Theme parsing error:
> gtk-contained.css:32:432: negative values are not allowed.
> (seamonkey:3808): Gtk-WARNING **: 09:03:33.846: Theme parsing error:
> gtk-contained.css:1512:157: Unit is missing.
> ------------------------------
>
> Don't know if it matters much, just wanted to note it.
> (NB. I intend to use it first under UbuntuStudio)
>
>

I went a different route, add the Mozilla Test repository using
zypper addrepo -cfp 99
'http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_$releasever/'
mozilla
and then get it from there using YaST - Software - Versions

1. the line works as given (assuming it does not overflow into two lines)
2. It normally takes less than 24 hours before a new version is
available there.

I don't know why Tristan is not adding Seamonkey to the "normal"
repositories, maybe he's still doing that for Leap 15.4.
I also don't know what will happen when Seamonkey ceases being made
available on the Mozilla site, something which is apparently going to
happen fairly soon.

On 2023-08-25, bad sector wrote:

> On 8/3/23 21:53, Ant wrote:
>> https://blog.seamonkey-project.org/2023/08/04/seamonkey-2-53-17-is-out/
>
> After unpacking the tarball I did a test launch
> in Suse-Leap-15.5 and got this
>
> ------------------------------
> ./seamonkey
> (seamonkey:3808): Gtk-WARNING **: 09:03:33.149: Theme parsing error:
> gtk-contained.css:32:432: negative values are not allowed.
> (seamonkey:3808): Gtk-WARNING **: 09:03:33.163: Theme parsing error:
> gtk-contained.css:1512:157: Unit is missing.
> (seamonkey:3808): Gtk-WARNING **: 09:03:33.833: Theme parsing error:
> gtk-contained.css:32:432: negative values are not allowed.
> (seamonkey:3808): Gtk-WARNING **: 09:03:33.846: Theme parsing error:
> gtk-contained.css:1512:157: Unit is missing.
> ------------------------------
>
> Don't know if it matters much, just wanted to note it.
> (NB. I intend to use it first under UbuntuStudio)

Those - unless I'm mistaken - look like warnings/errors related to the
gtk+3 theme. If you have other gtk+3 applications you can test, can you
check if you get the same messages when starting these applications from
a terminal or terminal emulator?

Are you using any gtk+3 theme that does not come with gtk+3 itself?
Gtk+3 sadly has sometimes introduced breaking changes in the new (new
compared to gtk+2) theming approach, and so themes installed separately
or installed manually under $HOME may need to be updated.

--
Nuno Silva

Nuno Silva wrote:
> On 2023-08-25, bad sector wrote:
>
>> On 8/3/23 21:53, Ant wrote:
>>> https://blog.seamonkey-project.org/2023/08/04/seamonkey-2-53-17-is-out/
>>
>> After unpacking the tarball I did a test launch
>> in Suse-Leap-15.5 and got this
>>
>> ------------------------------
>> ./seamonkey
>> (seamonkey:3808): Gtk-WARNING **: 09:03:33.149: Theme parsing error:
>> gtk-contained.css:32:432: negative values are not allowed.
>> (seamonkey:3808): Gtk-WARNING **: 09:03:33.163: Theme parsing error:
>> gtk-contained.css:1512:157: Unit is missing.
>> (seamonkey:3808): Gtk-WARNING **: 09:03:33.833: Theme parsing error:
>> gtk-contained.css:32:432: negative values are not allowed.
>> (seamonkey:3808): Gtk-WARNING **: 09:03:33.846: Theme parsing error:
>> gtk-contained.css:1512:157: Unit is missing.
>> ------------------------------
>>
>> Don't know if it matters much, just wanted to note it.
>> (NB. I intend to use it first under UbuntuStudio)
>
> Those - unless I'm mistaken - look like warnings/errors related to the
> gtk+3 theme. If you have other gtk+3 applications you can test, can you
> check if you get the same messages when starting these applications from
> a terminal or terminal emulator?
>
> Are you using any gtk+3 theme that does not come with gtk+3 itself?
> Gtk+3 sadly has sometimes introduced breaking changes in the new (new
> compared to gtk+2) theming approach, and so themes installed separately
> or installed manually under $HOME may need to be updated.
>

That's also a reason to install packages from repositories, they take
account of dependencies.