On Jun 29, 8:45 pm, Lee <ler...@gmail.com> wrote:
> On 6/29/10, Jaqui <jaquigreenl...@gmail.com> wrote:
>
>
>
> > On Jun 28, 2:01 pm, Beverly Howard <b...@bevhoward.com> wrote:
> >>  >> how to get the flawed ui* design Seamonkey 2 series to completely
> >> shut down when all windows closed? <<
>
> >> It is a bug, but it appears to be related to specific os installs.
>
> >> I have had the same problem on an XPProSP2 Tablet Edition computer for
> >> years with no resolution.
>
> >> It appears to be related to the combination of windows open when
> >> seamonkey is shut down, but I have been unable to track a reproducible
> >> set of steps to report it.
>
> >> THIS DOES NOT HAPPEN ON SEVERAL OTHER XPPROSP2 non tablet computers
> >> running the same SM versions.
>
> >>  >> I should NOT have to reboot the os to shut the suite down. <<
>
> >> Don't need to... close seamonkey, open task manager, processes from all
> >> users, sort by image name and end all seamonkey.exe processes... not
> >> elegant, but only takes a few seconds after you do it a dozen or so
> >> times ;-)
>
> >> Beverly Howard
>
> > ~chuckle~
> > This is on a GNU/Linux system, I don't own a copy of windows. :D
> > and unfortunately, the distro uses KDE4 so the process manager is no
> > longer available.
> > [ completely separate issue there, KDE4.x is directly comparable to
> > windows vista ( useless ), but it won't be killed off by the devs,
> > they think no usability is a good thing. ]
>
> > I went hunting for the process manager, to specifically shut down the
> > seamonkey processes, not available with the KDE4.x UI any more. Even
> > went searching through the 10,000 packages in the package manger, not
> > available for install. Which means the only way to shut seamonkey down
> > completely is to reboot the system.
>
> Probably an ignorant question, but can't you
>   su
> to become root,
>   ps -elf | grep seamonkey
> to find the pid & then
>   kill -9 <seamonkey pid>
> to shut SM down?
>
> Lee

yup. I could.
found out that it is the email / newsgroup client that is causing the
tsr activity, if I don't use it then seamonkey doesn't stay resident
in memory actively checking mail and newsgroups.

gonna have to think about getting a debug enabled build, both for this
and to try to get a core from the random crashes of seamonkey.  if I
can handle the stupid message bars long enough to get one. those
things are why I refused to ever USE firefox, seamonkey going with
them will drive me away from it also very soon.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to