From: daniel47@somewhere.someplaceelse   
      
   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.   
   --   
   Daniel70   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)