From: daniel47@somewhere.someplaceelse   
      
   On 5/09/2025 7:27 am, frg wrote:   
   > Daniel70 wrote:   
   >> On 4/09/2025 9:54 pm, frg wrote:   
   >>> Daniel70 wrote:   
   >>>> On 4/09/2025 5:02 am, bey24thgfdhg wrote:   
   >>>>> Dave Yeo wrote:   
   >>>>>> bey24thgfdhg wrote:   
   >>>>>>> Dave Yeo wrote:   
   >>>>>>>> bey24thgfdhg wrote:   
   >>>>>>>>> When I sent the "Testing" message above I had launched SM from the   
   >>>>>>>>> command line with seamonkey --mail to see if the crash resulted   
   >>>>>>>>> in an   
   >>>>>>>>> error message. It did and the message was "Segmentation fault   
   >>>>>>>>> (core   
   >>>>>>>>> dumped)".   
   >>>>>>>>   
   >>>>>>>> Does your SM create a crash report? I've been out of the loop   
   >>>>>>>> too long   
   >>>>>>>> and am not very knowledgeable about the most recent SM's or the   
   >>>>>>>> Linux   
   >>>>>>>> versions. The crash report may point to the segfault though it   
   >>>>>>>> takes   
   >>>>>>>> skill to figure out why. Same if there is a core file produced   
   >>>>>>>> by the   
   >>>>>>>> crash (probably not due to permissions) which can be attached to   
   >>>>>>>> GDB   
   >>>>>>>> and examined if you have the skill set. I don't have that skill.   
   >>>>>>>> Dave   
   >>>>>>>   
   >>>>>>> Are the developers not members of this group?   
   >>>>>>   
   >>>>>> The volunteer developers are members. Being volunteers, they spend   
   >>>>>> their time how they like on what interests them. If one doesn't   
   >>>>>> step up, well you're on your own.   
   >>>>>> Dave   
   >>>>>   
   >>>>> Understood. Is there an issue tracker for SeaMonkey where I can   
   >>>>> post this bug?   
   >>>>   
   >>>> Yes, there is/was one .... used to be on Bugzilla   
   >>>> https://www.bugzilla.org/ but I don't have a specific link for   
   >>>> SeaMonkey Faults.   
   >>>>   
   >>>> Is there even a specific SeaMonkey list or do 'we' just piggy-back   
   >>>> on the Mozilla or Firefox/Thunderbird lists??   
   >>>>   
   >>>> Maybe someone else can be more specific.   
   >>>   
   >>> https://bugzilla.mozilla.org/buglist.cgi?bug_status=UNCONFIR   
   ED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&chfiel   
   from=2018-01-01&chfieldto=Now&f1=component&list_id=15949575&o1=n   
   tequals&product=SeaMonkey&query_format=advanced&resolution=-   
   --&v1=Web%20Compatibility&order=changeddate%20DESC%2Cpriority%2C   
   ug_severity&query_based_on=   
   >>>   
   >>> Chances that startup crashes without a crash id are even looked at is   
   >>> almost zero.   
   >>>   
   >>> Same for crashes of distribution builds. Prerelease builds depends if   
   >>> someone else can reproduce. Linux configurations are infinite and I   
   >>> have seen some crashes personally caused by downlevel or broken other   
   >>> components.   
   >>>   
   >>> Multiple files are usually caused by files locked by third party   
   >>> applications usually virus scanners but ymmv.   
   >>>   
   >>> FRG   
   >>   
   >> Thank you, FRG.   
   >>   
   >> By-the-By, when I click that link, the "M Bugzilla" bar partially   
   >> obscures the "Product SeaMonkey" line   
   >   
   > It is broken. You need another browser for it. Even then usability is   
   > down compared to the old site revisions but that is the new normal for   
   > websites using the latest "standards" these days.   
   >   
   > FRG   
   >   
   > frg   
   >   
   >   
   Ah!! Thank you, FRG, worked with FF   
   --   
   Daniel70   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)