From: mrbarryedw.20@aussiebroadband.com.au   
      
   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!~   
      
   "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.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)