Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.software.seamonkey > #8077 > unrolled thread

Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22

Back to article view | Back to alt.comp.software.seamonkey

Contents

  Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Michael Lueck <mlueck@lueckdatasystems.com> - 2025-11-04 10:07 -0500
    Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 frg <frgrahl@gmx.net> - 2025-11-04 16:23 +0100
      Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Michael Lueck <mlueck@lueckdatasystems.com> - 2025-11-04 11:59 -0500
        Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Daniel70 <daniel47@nomail.afraid.org> - 2025-11-05 19:56 +1100
        Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 R Daneel Olivaw <Danni@hyperspace.vogon.gov.invalid> - 2025-11-05 16:30 +0100
          Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Michael Lueck <mlueck@lueckdatasystems.com> - 2025-11-05 11:48 -0500
    Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Barryedwin1 <mrbarryedw.20@aussiebroadband.com.au> - 2025-11-05 20:32 +0800
    Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Barryedwin1 <mrbarryedw.20@aussiebroadband.com.au> - 2025-11-05 23:08 +0800
      Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Michael Lueck <mlueck@lueckdatasystems.com> - 2025-11-05 12:06 -0500
        Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 frg <frgrahl@gmx.net> - 2025-11-08 13:07 +0100
          Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Barryedwin1 <mrbarryedw.20@aussiebroadband.com.au> - 2025-11-09 01:27 +0800
            Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 frg <frgrahl@gmx.net> - 2025-11-08 19:44 +0100
              Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Michael Lueck <mlueck@lueckdatasystems.com> - 2025-11-08 16:26 -0500
                Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 frg <frgrahl@gmx.net> - 2025-11-17 12:04 +0100
                  Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 R Daneel Olivaw <Danni@hyperspace.vogon.gov.invalid> - 2025-11-17 14:38 +0100
                    Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 frg <frgrahl@gmx.net> - 2025-11-17 17:03 +0100
                      Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 "Paul B. Gallagher" <mozilla@pbg-translations.com> - 2025-11-17 11:10 -0500
                        Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 frg <frgrahl@gmx.net> - 2025-11-17 18:00 +0100
                    Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Daniel70 <daniel47@nomail.afraid.org> - 2025-11-18 20:37 +1100
                  Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Barryedwin1 <mrbarryedw.20@aussiebroadband.com.au> - 2025-11-18 23:30 +0800
              Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Barryedwin1 <mrbarryedw.20@aussiebroadband.com.au> - 2025-11-09 10:09 +0800
        Re: Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22 Michael Lueck <mlueck@lueckdatasystems.com> - 2025-11-08 12:07 -0500

Page 1 of 2  [1] 2  Next page →

#8077 — Consistent crash on graceful program exit when upgraded to SeaMonkey/2.53.22

Greetings,

Seems Mozilla has discontinued their own NNTP server since last I tried to access. Posting this via news.eternal-september.org per the SeaMonkey support options page.

We run Xubuntu Linux. We receive our Mozilla software via the terrific Ubuntuzilla repository. Official Mozilla binary builds, delivered over the APT Repository interface into Xubuntu.

Recently SeaMonkey updated to this build version:

$ dpkg -l | grep seamonkey
ii  seamonkey-mozilla-build                        2.53.22-0ubuntu1                                       amd64        Mozilla Seamonkey, official Mozilla build, packaged for Ubuntu by the Ubuntuzilla 
project.

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0 SeaMonkey/2.53.22
Build identifier: 20251020190652

Since that latest update, each time I exit SeaMonkey, some few seconds later I get prompted to file a crash report as the program (SeaMonkey) crashed while exiting.

Is this a known defect in the latest build?

I am thankful,

-- 
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/

[toc] | [next] | [standalone]

#8078

Michael Lueck wrote:
> Greetings,
> 
> Seems Mozilla has discontinued their own NNTP server since last I tried to 
> access. Posting this via news.eternal-september.org per the SeaMonkey support 
> options page.
> 
> We run Xubuntu Linux. We receive our Mozilla software via the terrific 
> Ubuntuzilla repository. Official Mozilla binary builds, delivered over the APT 
> Repository interface into Xubuntu.
> 
> Recently SeaMonkey updated to this build version:
> 
> $ dpkg -l | grep seamonkey
> ii  seamonkey-mozilla-build                        
> 2.53.22-0ubuntu1                                       amd64        Mozilla 
> Seamonkey, official Mozilla build, packaged for Ubuntu by the Ubuntuzilla 
> project.
> 
> User agent: Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 
> Firefox/128.0 SeaMonkey/2.53.22
> Build identifier: 20251020190652
> 
> Since that latest update, each time I exit SeaMonkey, some few seconds later I 
> get prompted to file a crash report as the program (SeaMonkey) crashed while 
> exiting.
> 
> Is this a known defect in the latest build?
> 
> I am thankful,
> 

I have seen one other post about a shutdown crash under Linux but can not 
reproduce ith with the official x64 build under both OpenSuse and Rocky 8. Try 
if you can reproduce it with the official build.

FRG

[toc] | [prev] | [next] | [standalone]

#8080

Greetings FRG,

frg wrote:
> Michael Lueck wrote:
>>
>> We run Xubuntu Linux. We receive our Mozilla software via the terrific Ubuntuzilla repository. Official Mozilla binary builds, delivered over the APT Repository interface into Xubuntu.
>>
>> Recently SeaMonkey updated to this build version:
>>
>> $ dpkg -l | grep seamonkey
>> ii  seamonkey-mozilla-build 2.53.22-0ubuntu1                                       amd64        Mozilla Seamonkey, official Mozilla build, packaged for Ubuntu by the Ubuntuzilla project.
>>
> 
> I have seen one other post about a shutdown crash under Linux but can not reproduce ith with the official x64 build under both OpenSuse and Rocky 8. Try if you can reproduce it with the official build.



Ubuntuzilla is a repository package of the official Mozilla binary builds delivered via APT Repository interface.

I am not aware of a more official way to run Mozilla SeaMonkey on Xubuntu than that.

Please kindly advise.

I am thankful,

-- 
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/

[toc] | [prev] | [next] | [standalone]

#8088

On 5/11/2025 3:59 am, Michael Lueck wrote:
> Greetings FRG,
> frg wrote:
>> Michael Lueck wrote:
>>>
>>> We run Xubuntu Linux. We receive our Mozilla software via the 
>>> terrific Ubuntuzilla repository. Official Mozilla binary builds, 
>>> delivered over the APT Repository interface into Xubuntu.
>>>
>>> Recently SeaMonkey updated to this build version:
>>>
>>> $ dpkg -l | grep seamonkey
>>> ii  seamonkey-mozilla-build 
>>> 2.53.22-0ubuntu1                                       amd64        
>>> Mozilla Seamonkey, official Mozilla build, packaged for Ubuntu by the 
>>> Ubuntuzilla project.
>>
>> I have seen one other post about a shutdown crash under Linux but can 
>> not reproduce ith with the official x64 build under both OpenSuse and 
>> Rocky 8. Try if you can reproduce it with the official build.
> 
> Ubuntuzilla is a repository package of the official Mozilla binary 
> builds delivered via APT Repository interface.
> 
> I am not aware of a more official way to run Mozilla SeaMonkey on 
> Xubuntu than that.
> 
> Please kindly advise.
> 
> I am thankful,
> 
I used to use SeaMonkey Suite on a MageiaLinux installation I had. 
Mageia did supply Firefox as part of its OS Installation but not SeaMonkey.

So when I wanted to run SeaMonkey, I downloaded the SeaMonkey Linux 
release from the SeaMonkey-project web-page 
https://www.seamonkey-project.org/releases/ and did the installation of 
that file onto my Home Mount point. (I think I could have installed it 
on my System mount point but never tried.)

Can you do similar with your Ubuntuzilla OS??
-- 
Daniel70

[toc] | [prev] | [next] | [standalone]

#8092

Michael Lueck wrote:
> Greetings FRG,
> 
> frg wrote:
>> Michael Lueck wrote:
>>>
>>> We run Xubuntu Linux. We receive our Mozilla software via the 
>>> terrific Ubuntuzilla repository. Official Mozilla binary builds, 
>>> delivered over the APT Repository interface into Xubuntu.
>>>
>>> Recently SeaMonkey updated to this build version:
>>>
>>> $ dpkg -l | grep seamonkey
>>> ii  seamonkey-mozilla-build 
>>> 2.53.22-0ubuntu1                                       amd64        
>>> Mozilla Seamonkey, official Mozilla build, packaged for Ubuntu by the 
>>> Ubuntuzilla project.
>>>
>>
>> I have seen one other post about a shutdown crash under Linux but can 
>> not reproduce ith with the official x64 build under both OpenSuse and 
>> Rocky 8. Try if you can reproduce it with the official build.
> 
> 
> 
> Ubuntuzilla is a repository package of the official Mozilla binary 
> builds delivered via APT Repository interface.
> 
> I am not aware of a more official way to run Mozilla SeaMonkey on 
> Xubuntu than that.
> 
> Please kindly advise.
> 
> I am thankful,
> 

Seamonkey has dependencies which sometimes - on the face of it - do not 
make sense.  Taking Rust for instance, the Rust developers frequently 
break things so your Rust level should be >= x and <= y.  Unfortunately 
https://www.seamonkey-project.org/doc/system-requirements does not say 
what x and y are for Rust.
There is no guarantee that the Xubuntu maintainers know about any 
restrictions.  about:buildconfig will tell you what was used, maybe it 
would help if you posted out output from that page here so FRG (for 
instance) can take a look at it.

Daniel70 told you where you can find the "official build" but I have to 
admit I don't know how to install that Linux version.

[toc] | [prev] | [next] | [standalone]

#8094

Greetings Daneel,

R Daneel Olivaw wrote:
> 
> There is no guarantee that the Xubuntu maintainers know about any restrictions.


So you are suspecting that the latest official build of Mozilla SeaMonkey is now somehow not quite compatible with Xubuntu 22.04 LTS?


> about:buildconfig will tell you what was used, maybe it would help if you posted out output from that page here so FRG 
> (for instance) can take a look at it.


Output on my Xubuntu 22.04 LTS system:

Build Configuration
SeaMonkey 2.53.22 - 20251020190652
SeaMonkey source
https://gitlab.com/seamonkey-project/seamonkey-2.53-comm/tree/2_53_22_final
Platform source
https://gitlab.com/seamonkey-project/seamonkey-2.53-mozilla/tree/2_53_22_final

The latest information on building SeaMonkey can be found at https://www.seamonkey-project.org/dev/.
Build platform
Target
x86_64-pc-linux-gnu
Build tools
Compiler 	Version 	Compiler flags
/home/seabld/.mozbuild/sccache/sccache /usr/bin/gcc -std=gnu99 	8.5.0 	-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -fno-strict-aliasing -ffunction-sections -fdata-sections 
-fno-math-errno -pthread -pipe
/home/seabld/.mozbuild/sccache/sccache /usr/bin/g++ 	8.5.0 	-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wall -Wempty-body -Wignored-qualifiers -Woverloaded-virtual -Wpointer-arith 
-Wsign-compare -Wtype-limits -Wunreachable-code -Wwrite-strings -Wno-invalid-offsetof -Wc++1z-compat -Wduplicated-cond -Wimplicit-fallthrough -Wno-error=maybe-uninitialized 
-Wno-error=deprecated-declarations -Wno-error=array-bounds -Wno-error=free-nonheap-object -Wno-error=multistatement-macros -Wno-error=class-memaccess -Wno-error=unused-but-set-variable -Wformat 
-Wformat-overflow=2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno 
-pthread -pipe -g -freorder-blocks -O2 -fomit-frame-pointer -funwind-tables
/home/seabld/.rustup/toolchains/1.73.0-x86_64-unknown-linux-gnu/bin/rustc 	1.73.0 	
Configure options
--enable-application=comm/suite MOZILLA_OFFICIAL=1 --enable-update-channel=release --disable-tests --with-ccache=/home/seabld/.mozbuild/sccache/sccache CC=gcc CXX=g++ --enable-irc 
--enable-dominspector --enable-js-shell --with-l10n-base=../../../../l10n-56 --with-google-location-service-api-keyfile=/builds/google-api.key 
--with-google-safebrowsing-api-keyfile=/builds/google-api.key --with-crashreporter-url=https://seamonkey_project.bugsplat.com/post/bp/crash/postBP.php MAKE=/usr/bin/gmake



So should I be checking various packages to see that there are matches? If so, which ones?



> Daniel70 told you where you can find the "official build" but I have to admit I don't know how to install that Linux version.


The Ubuntuzilla packager downloads the official builds from Mozilla, the repackages the binaries in an Ubuntu compatible APT delivery package. The Ubuntuzilla process does not recompile anything.... 
all straight official Mozilla binaries.

I am thankful,

-- 
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/

[toc] | [prev] | [next] | [standalone]

#8090

Michael Lueck wrote on 4/11/25 11:07 pm:
> Greetings,
> 
> Seems Mozilla has discontinued their own NNTP server since last I tried 
> to access. Posting this via news.eternal-september.org per the SeaMonkey 
> support options page.
> 
> We run Xubuntu Linux. We receive our Mozilla software via the terrific 
> Ubuntuzilla repository. Official Mozilla binary builds, delivered over 
> the APT Repository interface into Xubuntu.
> 
> Recently SeaMonkey updated to this build version:
> 
> $ dpkg -l | grep seamonkey
> ii  seamonkey-mozilla-build                        
> 2.53.22-0ubuntu1                                       amd64        
> Mozilla Seamonkey, official Mozilla build, packaged for Ubuntu by the 
> Ubuntuzilla project.
> 
> User agent: Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 
> Firefox/128.0 SeaMonkey/2.53.22
> Build identifier: 20251020190652
> 
> Since that latest update, each time I exit SeaMonkey, some few seconds 
> later I get prompted to file a crash report as the program (SeaMonkey) 
> crashed while exiting.
> 
> Is this a known defect in the latest build?
> 
> I am thankful,
> 
I've also been seeing this oddness for the past few months.
Linux-6.14.0-33-generic | Ubuntu-24.04.3_LTS | X11 SM-2.54.22->23
(it also happens on the Wayland desktop).
That Crash_Reporter after-popup seems erratic, and only seems to happen 
when another Ubuntu distro's app is open (e.g. Firefox).
System Monitor says SeaMonkey has shut down fully and cleanly, and 
doesn't list SeaMonkey as having any sort of problem.
As SM crashes go, it doesn't seem to be anything of the sort, with just 
this popup "SeaMonkey e.V. Crash Reporter" pane appearing a few seconds 
after SeaMonkey shuts down cleanly - after successfully-saving all 
recent Composer work and any downloading files, etcetera, and as noted - 
a clean proper shutdown. Apart from the Crash_Reporter popup, it does 
not interfere with a working SeaMonkey.
The Crash_Reporter appears to operate in its own app, extant of 
SeaMonkey itself.
Ubuntu X11 opens SeaMonkey cleanly with Mail&News heading s in 
Boldface-text, but subsequent SM instances lose the headings' Boldface 
text, which makes me think that Ubuntu - even on X11 desktop - is using 
some core Wayland distro-code - even underneath the X11 desktop - 
because of the missing boldface-text headings when selecting the Wayland 
desktop.

Still, it has only appeared over the past couple of months ~~
I've been just explaining it as a conflict between Ubuntu's basically 
Wayland-optimised distro, and a basically core-X11 app-suite like 
SeaMonkey. I think Xubuntu would also still have that core-Ubuntu code 
as its base, so we are seeing similar or same phenomena. HTH

[toc] | [prev] | [next] | [standalone]

#8091

Michael Lueck wrote on 4/11/25 11:07 pm:
> Greetings,
> 
> Seems Mozilla has discontinued their own NNTP server since last I tried 
> to access. Posting this via news.eternal-september.org per the SeaMonkey 
> support options page.
> 
> We run Xubuntu Linux. We receive our Mozilla software via the terrific 
> Ubuntuzilla repository. Official Mozilla binary builds, delivered over 
> the APT Repository interface into Xubuntu.
> 
> Recently SeaMonkey updated to this build version:
> 
> $ dpkg -l | grep seamonkey
> ii  seamonkey-mozilla-build                        
> 2.53.22-0ubuntu1                                       amd64        
> Mozilla Seamonkey, official Mozilla build, packaged for Ubuntu by the 
> Ubuntuzilla project.
> 
> User agent: Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 
> Firefox/128.0 SeaMonkey/2.53.22
> Build identifier: 20251020190652
> 
> Since that latest update, each time I exit SeaMonkey, some few seconds 
> later I get prompted to file a crash report as the program (SeaMonkey) 
> crashed while exiting.
> 
> Is this a known defect in the latest build?
> 
> I am thankful,
> 
I've also been seeing this oddness for the past few months.
Linux-6.14.0-33-generic | Ubuntu-24.04.3_LTS | X11 SM-2.54.22->23
(it also happens on the Wayland desktop).
That Crash_Reporter after-popup seems erratic, and only seems to happen 
when another Ubuntu distro's app is open (e.g. Firefox).
System Monitor says SeaMonkey has shut down fully and cleanly, and 
doesn't list SeaMonkey as having any sort of problem.
As SM crashes go, it doesn't seem to be anything of the sort, with just 
this popup "SeaMonkey e.V. Crash Reporter" pane appearing a few seconds 
after SeaMonkey shuts down cleanly - after successfully-saving all 
recent Composer work and any downloading files, etcetera, and as noted - 
a clean proper shutdown. Apart from the Crash_Reporter popup, it does 
not interfere with a working SeaMonkey.
The Crash_Reporter appears to operate in its own app, extant of 
SeaMonkey itself.
Ubuntu X11 opens SeaMonkey cleanly with Mail&News heading s in 
Boldface-text, but subsequent SM instances lose the headings' Boldface 
text, which makes me think that Ubuntu - even on X11 desktop - is using 
some core Wayland distro-code - even underneath the X11 desktop - 
because of the missing boldface-text headings when selecting the Wayland 
desktop.

Still, it has only appeared over the past couple of months ~~
I've been just explaining it as a conflict between Ubuntu's basically 
Wayland-optimised distro, and a basically core-X11 app-suite like 
SeaMonkey. I think Xubuntu would also still have that core-Ubuntu code 
as its base, so we are seeing similar or same phenomena. HTH

And the Good News keeps on coming!~
<https://www.phoronix.com/news/GNOME-Mutter-Drops-X11>
"GNOME 50 will continue supporting XWayland clients (apps / games) but 
moving forward strictly for Wayland-based desktop sessions.
After the X11 path was disabled by default in the GNOME 49 release, the 
whole X11 backend code is being outright removed for the GNOME 50 cycle."
I'm on Gnome 46, so I wonder how much disabled/removed X11 code, is 
being backwardly removed?
Unfortunately, the last that I heard, SeaMonkey has no XWayland support 
builtin. Possibly explains my boldface display problems. HTH and that my 
take on it is not FUD.

[toc] | [prev] | [next] | [standalone]

#8095

Greetings Barry,


Barryedwin1 wrote:
> 
> Still, it has only appeared over the past couple of months ~~
> I've been just explaining it as a conflict between Ubuntu's basically Wayland-optimised distro, and a basically core-X11 app-suite like SeaMonkey. I think Xubuntu would also still have that 
> core-Ubuntu code as its base, so we are seeing similar or same phenomena. HTH
> 
> And the Good News keeps on coming!~
> <https://www.phoronix.com/news/GNOME-Mutter-Drops-X11>
> "GNOME 50 will continue supporting XWayland clients (apps / games) but moving forward strictly for Wayland-based desktop sessions.
> After the X11 path was disabled by default in the GNOME 49 release, the whole X11 backend code is being outright removed for the GNOME 50 cycle."
> I'm on Gnome 46, so I wonder how much disabled/removed X11 code, is being backwardly removed?
> Unfortunately, the last that I heard, SeaMonkey has no XWayland support builtin. Possibly explains my boldface display problems. HTH and that my take on it is not FUD.


Xubuntu 22.04 LTS appears to come with a mix of GNOME version components....


$ dpkg -l | grep "gnome"
ii  gnome-accessibility-themes                     3.28-1ubuntu3                                          all          High Contrast GTK+ 2 theme and icons
ii  gnome-desktop3-data                            42.9-0ubuntu1                                          all          Common files for GNOME desktop apps
ii  gnome-disk-utility                             42.0-1ubuntu1                                          amd64        manage and configure disk drives and media
ii  gnome-font-viewer                              41.0-2                                                 amd64        font viewer for GNOME
ii  gnome-keyring                                  40.0-3ubuntu3                                          amd64        GNOME keyring services (daemon and tools)
ii  gnome-keyring-pkcs11:amd64                     40.0-3ubuntu3                                          amd64        GNOME keyring module for the PKCS#11 module loading library
ii  gnome-menus                                    3.36.0-1ubuntu3                                        amd64        GNOME implementation of the freedesktop menu specification
ii  gnome-mines                                    1:40.1-1                                               amd64        popular minesweeper puzzle game for GNOME
ii  gnome-software                                 41.5-2ubuntu2                                          amd64        Software Center for GNOME
ii  gnome-software-common                          41.5-2ubuntu2                                          all          Software Center for GNOME (common files)
ii  gnome-software-plugin-snap                     41.5-2ubuntu2                                          amd64        Snap support for GNOME Software
ii  gnome-sudoku                                   1:42.0-1                                               amd64        Sudoku puzzle game for GNOME
ii  gnome-system-tools                             3.0.0-9.1ubuntu1                                       amd64        Cross-platform configuration utilities
ii  gnome-themes-extra:amd64                       3.28-1ubuntu3                                          amd64        Adwaita GTK+ 2 theme — engine
ii  gnome-themes-extra-data                        3.28-1ubuntu3                                          all          Adwaita GTK+ 2 theme — common files
ii  gnome-themes-standard                          3.28-1ubuntu3                                          all          Adwaita GTK+ 2 theme — engine - transitional package
ii  language-pack-gnome-en                         1:22.04+20240902                                       all          GNOME translation updates for language English
ii  language-pack-gnome-en-base                    1:22.04+20240902                                       all          GNOME translations for language English
ii  language-selector-gnome                        0.219.1                                                all          Language selector frontend for Ubuntu
ii  libgnome-desktop-3-19:amd64                    42.9-0ubuntu1                                          amd64        Utility library for the GNOME desktop - GTK 3 version
ii  libgnome-games-support-1-3:amd64               1.8.2-1build1                                          amd64        library for common functions of GNOME games
ii  libgnome-games-support-common                  1.8.2-1build1                                          all          library for common functions of GNOME games (common files)
ii  libgnome-menu-3-0:amd64                        3.36.0-1ubuntu3                                        amd64        GNOME implementation of the freedesktop menu specification
ii  libpam-gnome-keyring:amd64                     40.0-3ubuntu3                                          amd64        PAM module to unlock the GNOME keyring upon login
ii  libreoffice-gnome                              1:7.3.7-0ubuntu0.22.04.10                              amd64        office productivity suite -- GNOME integration
ii  libsoup-gnome2.4-1:amd64                       2.74.2-3ubuntu0.6                                      amd64        HTTP library implementation in C -- GNOME support library
ii  network-manager-gnome                          1.24.0-1ubuntu3                                        amd64        network management framework (GNOME frontend)
ii  network-manager-pptp-gnome                     1.2.10-1                                               amd64        network management framework (PPTP plugin GNOME GUI)
ii  pinentry-gnome3                                1.1.1-1build2                                          amd64        GNOME 3 PIN or pass-phrase entry dialog for GnuPG
ii  policykit-1-gnome                              0.105-7ubuntu3                                         amd64        authentication agent for PolicyKit


Looks to be the highest GNOME component version comes from GNOME 42.

I am thankful,

-- 
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/

[toc] | [prev] | [next] | [standalone]

#8116

Michael Lueck wrote:
> Greetings Barry,
...

I have an ubuntu 22.4 LTS vm left which I now and then use for tests. Use 
Rocky Linux 8 vm for building and OpenSuse Leap 1.56 (16 bahhh) as a backup 
server. I updated the vm to the latest level and unpacked the official package 
into the 22.4 opt/seamonkey directory using a root account and ran it under my 
normal user. I was unable to confim the exit crash in any way.

Is the crash listed under about:crashes? If yes can you post the crash id.

Exit crash might be a timeout or the system blocking access to files. Bad 
extension or some old data which piled up too. I would try with a new profile 
too for testing.

Over time would be wise to a distribution which still supports the x11 layer. 
Not enough devs around to make Wayland support happen in the near future. We 
are not alone with this but not something I like.

I dislike wayland and the way linux systems in general go with obscure 
undocumented stuff, endless changes switching things back and forth, dumbing 
down the ui to mobile style or a bad Windows copycat, not careing one bit 
about api compatibility but that is another story and just a personal rant.

FRG

[toc] | [prev] | [next] | [standalone]

#8118

frg wrote on 8/11/25 8:07 pm:
> 
> Michael Lueck wrote:
>> Greetings Barry,
> ...
> 
> I have an ubuntu 22.4 LTS vm left which I now and then use for tests. 
> Use Rocky Linux 8 vm for building and OpenSuse Leap 1.56 (16 bahhh) as a 
> backup server. I updated the vm to the latest level and unpacked the 
> official package into the 22.4 opt/seamonkey directory using a root 
> account and ran it under my normal user. I was unable to confim the exit 
> crash in any way.
> 
> Is the crash listed under about:crashes? If yes can you post the crash id.

Currently on :-
U-24-04.3 X11 SeaMonkey 2.53.23 beta 1 pre -20251104212101

Tell the truth, I mostly have the crash reporter pane disabled (all 
boxes unchecked), but the last one listed under the heading:
"Submitted Crash Reports"
Report ID 	Date Submitted 	
123491 	5/11/25, 8:18 pm 	
<https://app.bugsplat.com/v2/crash?database=seamonkey_project&id=123491>

Opening an account there says this is an unknown crash report - ergo it 
is blank ..

Did I mention that for me, it is an erratic bug!

I just now tried everything I could to reproduce the crash popup, and 
needless to say, nothing!
As usual, U-24-04.3 system monitor says everything SeaMonkey is closing 
down cleanly with no artifacts other than the popup crash reporter

> 
> Exit crash might be a timeout or the system blocking access to files. 
> Bad extension or some old data which piled up too. I would try with a 
> new profile too for testing.
> 
X11 Nothing to report- clean shutdown - no popup crash reporter.

> Over time would be wise to a distribution which still supports the x11 
> layer. Not enough devs around to make Wayland support happen in the near 
> future. We are not alone with this but not something I like.
> 
Wise words indeed! Yes, I'll need to do this. I live inside SM Composer!

Actually, with Gnome effectively dumping X11, and Qt already on Wayland 
- Xubuntu is the X11 version of Ubuntu - so it seems we are looking for 
an obscure X11 desktop environment as well as a X11 centric distro that 
supports my handful of essential apps, though the banks, governments, 
etcetera, may mean I have to use a mainstream distro for compatibility.
Surely is a conundrum. Seems I will just have to diversify out of the 
single environment option. Might even be safer actually.

Switching to:-
U-24-04.3 Wayland SeaMonkey 2.53.23 beta 1 pre -20251104212101

Even with a few other apps running concurrently, a clean shutdown with 
no crash popup and system-monitor says everything SeaMonkey is good- no 
residuals.


I'm feeling it may be a system timeout on SM, as my profile is:-
16,260 items, totalling 5.2 GB,
albeit my system is:-
ASUS Pro WS X570-ACE AMD Ryzen™ 9 3900X × 24 32.0-GiB-DDR4 2.5TB NVMe
so the hardware shouldn't bottleneck it.

For me, it is not a problem - it's more of a microscopic niggle.
Always the way. When you want something to happen - it does not.

> I dislike wayland and the way linux systems in general go with obscure 
> undocumented stuff, endless changes switching things back and forth, 
> dumbing down the ui to mobile style or a bad Windows copycat, not 
> careing one bit about api compatibility but that is another story and 
> just a personal rant.
> 
> FRG

Can't argue with that! You are not exactly an island in those 
sentiments. Comprehensive computing seems to make way for 
specialisation. Smartphones are commodities that like the gap between 
rich and poor, the gap between power computerisation and commodity 
computing becomes even wider with time. Proprietorialism and security 
also now seem to be identical. Ownership can't value public freedom.

I surely do hope a Linux-distro does optimise for X11, but I guess 
progress has to be accommodated too. We just need to find solutions.

Thanks for all you've done for SM and myself as a user, seems entirely 
inadequate. We don't say it enough, but you and your fellow devs efforts 
are genuinely valued and appreciated by we users. Much appreciated. Barry.

[toc] | [prev] | [next] | [standalone]

#8119

Barryedwin1 wrote:
> frg wrote on 8/11/25 8:07 pm:
>>
>> Michael Lueck wrote:
>>> Greetings Barry,
>> ...
>>
>> I have an ubuntu 22.4 LTS vm left which I now and then use for tests. Use 
>> Rocky Linux 8 vm for building and OpenSuse Leap 1.56 (16 bahhh) as a backup 
>> server. I updated the vm to the latest level and unpacked the official 
>> package into the 22.4 opt/seamonkey directory using a root account and ran 
>> it under my normal user. I was unable to confim the exit crash in any way.
>>
>> Is the crash listed under about:crashes? If yes can you post the crash id.
> 
> Currently on :-
> U-24-04.3 X11 SeaMonkey 2.53.23 beta 1 pre -20251104212101
> 
> Tell the truth, I mostly have the crash reporter pane disabled (all boxes 
> unchecked), but the last one listed under the heading:
> "Submitted Crash Reports"
> Report ID     Date Submitted
> 123491     5/11/25, 8:18 pm
> <https://app.bugsplat.com/v2/crash?database=seamonkey_project&id=123491>
> 
> Opening an account there says this is an unknown crash report - ergo it is 
> blank ..
> 
> Did I mention that for me, it is an erratic bug!

This is a null pointer crash. You are running openWith. I know this one can 
cause a recursive loop problem and a crash if you try it on the wrong link 
type. Forgot which one but I think mailto or another non standard scheme. 
There are a few other old ones but can't say if they are still safe. Element 
Hiding Helper might need an update.

To make matters worse we broke BugSplat reporting. Version number is bad in 
the crashes. I didn't have time to even look at BugSplat lately and only do it 
when something is reported so never saw it. Doh. Suspect a fast 2.53.23 is 
needed soon :) Doh

>> Over time would be wise to a distribution which still supports the x11 
>> layer. Not enough devs around to make Wayland support happen in the near 
>> future. We are not alone with this but not something I like.
>>
> Wise words indeed! Yes, I'll need to do this. I live inside SM Composer!

Worst case if we go out of business you can tuck it into a vm. But don't plan to.

> I'm feeling it may be a system timeout on SM, as my profile is:-
> 16,260 items, totalling 5.2 GB,
> albeit my system is:-
> ASUS Pro WS X570-ACE AMD Ryzen™ 9 3900X × 24 32.0-GiB-DDR4 2.5TB NVMe
> so the hardware shouldn't bottleneck it.
> 

Do a bookmarks integrity check and maybe nuke Offline Website Data and cookies 
one time. I have set to do these two every time I close SM but some might 
prefer not to do.

> Can't argue with that! You are not exactly an island in those sentiments. 
> Comprehensive computing seems to make way for specialisation. Smartphones are 
> commodities that like the gap between rich and poor, the gap between power 
> computerisation and commodity computing becomes even wider with time. 
> Proprietorialism and security also now seem to be identical. Ownership can't 
> value public freedom.

/rant on
In the 90ies and start of 2000 it was fun and I updated constantly. I love 
testing new stuff but the new stuff became dull over time. Now its just ui 
dumbing down and putting more freedom to configure things into a box and lock 
it. Every website redesign I have seen in the last years was bad when it comes 
usability on the desktop. 90pt font sizes, no content, endless drivel about 
how eco friendly even the most eco unfriendly company is instead of real news 
and so on. AI is the next level. We search for you and you just need to 
believe us. Takes away basic skills over time. I really thing AI can help like 
in testing stuff or checking results for anomalies among lots of other things 
but it is not intelligence and won't be for a long time if ever.

> 
> I surely do hope a Linux-distro does optimise for X11, but I guess progress 
> has to be accommodated too. We just need to find solutions.

Whatever progress means this day.

/rant off


> Thanks for all you've done for SM and myself as a user, seems entirely 
> inadequate. We don't say it enough, but you and your fellow devs efforts are 
> genuinely valued and appreciated by we users. Much appreciated. Barry.

I am selfish and SeaMonkey is my browser for almost 30 years now since 
Netscape 2 on OS/2. So doing code work. On the sites it still works it is 
still the most usable and best. Only Vivaldi comes somewhat close but lacks 
some stuff.

FRG

[toc] | [prev] | [next] | [standalone]

#8120

Greetings FRG,

frg wrote:
> 
> I am selfish and SeaMonkey is my browser for almost 30 years now since Netscape 2 on OS/2. 



Yes, Netscape / Firefox on OS/2.... and now I run OS/3.... GNU Linux!

Brave Browser became my primary browser a few years back.

SeaMonkey for email due to Thunderbird pulling this stunt and never resolving it....

[Bug 81141] [RFE] Ability to rebuild msf files on demand

The core developers refused to build in some way to do a global integrity check on all of the msf files unless someone could document a repeatable way to mess up msf files.


OS/2 lives on in a VirtualBox VM.

I am thankful,

-- 
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/

[toc] | [prev] | [next] | [standalone]

#8158

Crash should be fixed in latest nightly. Shooting for a fast 2.53.23 next.

FRG

Michael Lueck wrote:
> Greetings FRG,
> 
> frg wrote:
>>
>> I am selfish and SeaMonkey is my browser for almost 30 years now since 
>> Netscape 2 on OS/2. 
> 
> 
> 
> Yes, Netscape / Firefox on OS/2.... and now I run OS/3.... GNU Linux!
> 
> Brave Browser became my primary browser a few years back.
> 
> SeaMonkey for email due to Thunderbird pulling this stunt and never resolving 
> it....
> 
> [Bug 81141] [RFE] Ability to rebuild msf files on demand
> 
> The core developers refused to build in some way to do a global integrity 
> check on all of the msf files unless someone could document a repeatable way 
> to mess up msf files.
> 
> 
> OS/2 lives on in a VirtualBox VM.
> 
> I am thankful,
> 

[toc] | [prev] | [next] | [standalone]

#8159

frg wrote:
> Crash should be fixed in latest nightly. Shooting for a fast 2.53.23 next.
> 
> FRG
> 

Not a 2.53.22.1?  It's been a while since we've had a .1 version, 
although 2.53.18.1 was followed by 2.53.18.2 a few weeks later.

[toc] | [prev] | [next] | [standalone]

#8160

R Daneel Olivaw wrote:
> frg wrote:
>> Crash should be fixed in latest nightly. Shooting for a fast 2.53.23 next.
>>
>> FRG
>>
> 
> Not a 2.53.22.1?  It's been a while since we've had a .1 version, although 
> 2.53.18.1 was followed by 2.53.18.2 a few weeks later.

A few issues fixed which require changes in older stuff. Too much hassle to 
back out and do incremental updates on top.

frg

[toc] | [prev] | [next] | [standalone]

#8161

frg wrote:

> R Daneel Olivaw wrote:
>> frg wrote:
>>> Crash should be fixed in latest nightly. Shooting for a fast 2.53.23 
>>> next.
>>>
>>> FRG
>>>
>>
>> Not a 2.53.22.1?  It's been a while since we've had a .1 version, 
>> although 2.53.18.1 was followed by 2.53.18.2 a few weeks later.
> 
> A few issues fixed which require changes in older stuff. Too much hassle 
> to back out and do incremental updates on top.

Thank you for all your hard work.

 From my perspective, the top priority is our inability to handle 
ReCAPTCHA and Cloudflare challenges, which makes many websites 
inaccessible (in my recent experience, 20% or more). Is there any hope 
of fixing that on the horizon?

-- 
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher

[toc] | [prev] | [next] | [standalone]

#8162

Paul B. Gallagher wrote:
> frg wrote:
> 
>> R Daneel Olivaw wrote:
>>> frg wrote:
>>>> Crash should be fixed in latest nightly. Shooting for a fast 2.53.23 next.
>>>>
>>>> FRG
>>>>
>>>
>>> Not a 2.53.22.1?  It's been a while since we've had a .1 version, although 
>>> 2.53.18.1 was followed by 2.53.18.2 a few weeks later.
>>
>> A few issues fixed which require changes in older stuff. Too much hassle to 
>> back out and do incremental updates on top.
> 
> Thank you for all your hard work.
> 
>  From my perspective, the top priority is our inability to handle ReCAPTCHA 
> and Cloudflare challenges, which makes many websites inaccessible (in my 
> recent experience, 20% or more). Is there any hope of fixing that on the horizon?
> 

ReCaptcha is fixed since 10/30. Clownflare is total crap. Might be fixed when 
I am able to get optional chaining back in the wip branch but unsure. It is 
not a company but a custom denial of service for minor browsers.

FRG

[toc] | [prev] | [next] | [standalone]

#8164

On 18/11/2025 12:38 am, R Daneel Olivaw wrote:
> frg wrote:
>> Crash should be fixed in latest nightly. Shooting for a fast 2.53.23 
>> next.
>>
>> FRG
> 
> Not a 2.53.22.1?  It's been a while since we've had a .1 version, 
> although 2.53.18.1 was followed by 2.53.18.2 a few weeks later.

Reminds me to ask, sarcastically, "2.53.23!! When are we ever going to 
see SM Ver 3.0.x.x?? ;-P".

And reminds mt, too, to through a few dollars in the Bit-Bucket!!

https://www.seamonkey-project.org/donate/

Bugger!! I was gunna donate vis Paypal .... but due to having been 
SCAMMED I've had to cancel my Credit Card. New one on the way, so I hope 
you guys can hang on for a bit.

Keep up the good work!! ;-P
-- 
Daniel70

[toc] | [prev] | [next] | [standalone]

#8165

frg wrote on 17/11/25 7:04 pm:
> Crash should be fixed in latest nightly. Shooting for a fast 2.53.23 next.
> 
> FRG
> 
> Michael Lueck wrote:
>> Greetings FRG,
>>
>> frg wrote:
>>>
>>> I am selfish and SeaMonkey is my browser for almost 30 years now 
>>> since Netscape 2 on OS/2. 
>>
>>
>>
>> Yes, Netscape / Firefox on OS/2.... and now I run OS/3.... GNU Linux!
>>
>> Brave Browser became my primary browser a few years back.
>>
>> SeaMonkey for email due to Thunderbird pulling this stunt and never 
>> resolving it....
>>
>> [Bug 81141] [RFE] Ability to rebuild msf files on demand
>>
>> The core developers refused to build in some way to do a global 
>> integrity check on all of the msf files unless someone could document 
>> a repeatable way to mess up msf files.
>>
>>
>> OS/2 lives on in a VirtualBox VM.
>>
>> I am thankful,
>>
> 
SeaMonkey/2.53.23, Build identifier: 20251116212007
Mon 17 November 2025 21∶02∶13 ~> Tue 18 Nov 2025 23:26:07 AWST (GMT+8)
Over 24 hours, multiple shutdowns = no crash reporter popups.
Seems like a hard fix. HTH Barry.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | alt.comp.software.seamonkey

csiph-web