Cross-posted to alt.comp.software.seamonkey and alt.os.linux.mageia as
I'm not sure what caused my problem.
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 SeaMonkey/2.53.15 Build identifier: 20230108172623
on MageiaLinux 6 with KDE Desktop/ on a Dual-booting (Win7/MGALinux 6)
HP 6730 Laptop.
Last night, after about an hours working, I closed my SeaMonkey ('X' in
top right of all three SM screens) .... but didn't shut-down my computer
... and, about 5 minutes later, I realised I had forgotten to do
something so clicked on my SeaMonkey Desktop icon to restart the program .... and got a message
Quote
SeaMonkey is already running, but is not responding. To open a new
window, you must first close the existing SeaMonkey process, or restart
your system.
End Quote
SeaMonkey was not showing on my task-bar. So I waited .... 10 mins, same message .... 30 mins, same message. Eventually I gave up and shut down
the Laptop and went to bed.
1. On Linux, if I wanted to force a program closure, where would I go?? (In Win7, I think it's via Ctrl/Alt/Del)
2. In SeaMonkey and/or Linux, where might I find any error messages which might tell me what my problem is/was??
TIA
Daniel65 wrote:
Cross-posted to alt.comp.software.seamonkey and alt.os.linux.mageia
as I'm not sure what caused my problem.
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
SeaMonkey/2.53.15 Build identifier: 20230108172623
on MageiaLinux 6 with KDE Desktop/ on a Dual-booting (Win7/MGALinux
6) HP 6730 Laptop.
Last night, after about an hours working, I closed my SeaMonkey
('X' in top right of all three SM screens) .... but didn't
shut-down my computer ... and, about 5 minutes later, I realised I
had forgotten to do something so clicked on my SeaMonkey Desktop
icon to restart the program .... and got a message
Quote SeaMonkey is already running, but is not responding. To open
a new window, you must first close the existing SeaMonkey process,
or restart your system. End Quote
SeaMonkey was not showing on my task-bar. So I waited .... 10 mins,
same message .... 30 mins, same message. Eventually I gave up and
shut down the Laptop and went to bed.
1. On Linux, if I wanted to force a program closure, where would
I go?? (In Win7, I think it's via Ctrl/Alt/Del)
2. In SeaMonkey and/or Linux, where might I find any error
messages which might tell me what my problem is/was??
TIA
This gets asked every few months, and I must admit I thought you were
one of the people who had asked it before. If you want to see if
Seamonkey is still running as a zombie after you have terminated it,
open a command-line window and
ps aux | grep -e monkey
That will give you one (good) or three (bad) entries. If it is three
then the first two of them will contain the a path to a "seamonkey"
file (assuming there is no other program containing "monkey" in its
name). The last entry will be the grep line itself. Take the
"seamonkey" line which has used the most time (the two time values
are start hh:mm and time used) and "kill" the process-id (the number
on the left).
In my case, myusr 3768 0.0 0.0 15176 3264 ? S 09:55
0:00 /bin/sh /usr/bin/seamonkey myusr 3773 4.7 8.6 4196428
1357632 ? Sl 09:55 6:02 /usr/lib64/seamonkey/seamonkey-bin
myusr 9956 0.0 0.0 7720 764 pts/1 S+ 12:01 0:00 grep
--color=auto -e monkey
seamonkey-bin has used 6:02, so you want to issue "kill 3773".
Don Spam's Reckless Son wrote on 23/3/23 10:09 pm:
Daniel65 wrote:
Cross-posted to alt.comp.software.seamonkey and alt.os.linux.mageia
as I'm not sure what caused my problem.
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
SeaMonkey/2.53.15 Build identifier: 20230108172623
on MageiaLinux 6 with KDE Desktop/ on a Dual-booting (Win7/MGALinux
6) HP 6730 Laptop.
Last night, after about an hours working, I closed my SeaMonkey
('X' in top right of all three SM screens) .... but didn't
shut-down my computer ... and, about 5 minutes later, I realised I
had forgotten to do something so clicked on my SeaMonkey Desktop
icon to restart the program .... and got a message
Quote SeaMonkey is already running, but is not responding. To open
a new window, you must first close the existing SeaMonkey process,
or restart your system. End Quote
SeaMonkey was not showing on my task-bar. So I waited .... 10 mins,
same message .... 30 mins, same message. Eventually I gave up and
shut down the Laptop and went to bed.
1. On Linux, if I wanted to force a program closure, where would
I go?? (In Win7, I think it's via Ctrl/Alt/Del)
2. In SeaMonkey and/or Linux, where might I find any error
messages which might tell me what my problem is/was??
TIA
This gets asked every few months, and I must admit I thought you were
one of the people who had asked it before. If you want to see if
Seamonkey is still running as a zombie after you have terminated it,
open a command-line window and
ps aux | grep -e monkey
That will give you one (good) or three (bad) entries. If it is three
then the first two of them will contain the a path to a "seamonkey"
file (assuming there is no other program containing "monkey" in its
name). The last entry will be the grep line itself. Take the
"seamonkey" line which has used the most time (the two time values
are start hh:mm and time used) and "kill" the process-id (the number
on the left).
In my case, myusr 3768 0.0 0.0 15176 3264 ? S 09:55
0:00 /bin/sh /usr/bin/seamonkey myusr 3773 4.7 8.6 4196428
1357632 ? Sl 09:55 6:02 /usr/lib64/seamonkey/seamonkey-bin >> myusr 9956 0.0 0.0 7720 764 pts/1 S+ 12:01 0:00 grep
--color=auto -e monkey
seamonkey-bin has used 6:02, so you want to issue "kill 3773".
So, in my case, ....
[daniel@localhost ~]$ ps aux | grep -e monkey
daniel 3275 8.3 35.2 4356784 1389556 ? Sl 18:48 17:50 /home/daniel/seamonkey_2/SeaMonkey_2_53_6/seamonkey/seamonkey
--sm-client-id 1028c1d320b210000167948698700000031840012
daniel 7856 0.0 0.0 12296 864 pts/0 S+ 22:21 0:00 grep
--color -e monkey
[daniel@localhost ~]$ ^C
[daniel@localhost ~]$
So I'm guessing you would call that 'one (good)' entry
Your reply copy/pasted to my Linuxstuff file .... so, hopefully, I don't
ask again!! ;-(
Daniel65 wrote:
Don Spam's Reckless Son wrote on 23/3/23 10:09 pm:
Daniel65 wrote:
Cross-posted to alt.comp.software.seamonkey and alt.os.linux.mageia
as I'm not sure what caused my problem.
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
SeaMonkey/2.53.15 Build identifier: 20230108172623
on MageiaLinux 6 with KDE Desktop/ on a Dual-booting (Win7/MGALinux
6) HP 6730 Laptop.
Last night, after about an hours working, I closed my SeaMonkey
('X' in top right of all three SM screens) .... but didn't
shut-down my computer ... and, about 5 minutes later, I realised I
had forgotten to do something so clicked on my SeaMonkey Desktop
icon to restart the program .... and got a message
Quote SeaMonkey is already running, but is not responding. To open
a new window, you must first close the existing SeaMonkey process,
or restart your system. End Quote
SeaMonkey was not showing on my task-bar. So I waited .... 10 mins,
same message .... 30 mins, same message. Eventually I gave up and
shut down the Laptop and went to bed.
1. On Linux, if I wanted to force a program closure, where would >>>> I go?? (In Win7, I think it's via Ctrl/Alt/Del)
2. In SeaMonkey and/or Linux, where might I find any error
messages which might tell me what my problem is/was??
TIA
This gets asked every few months, and I must admit I thought you were
one of the people who had asked it before. If you want to see if
Seamonkey is still running as a zombie after you have terminated it,
open a command-line window and
ps aux | grep -e monkey
That will give you one (good) or three (bad) entries. If it is three
then the first two of them will contain the a path to a "seamonkey"
file (assuming there is no other program containing "monkey" in its
name). The last entry will be the grep line itself. Take the
"seamonkey" line which has used the most time (the two time values
are start hh:mm and time used) and "kill" the process-id (the number
on the left).
In my case, myusr 3768 0.0 0.0 15176 3264 ? S 09:55
0:00 /bin/sh /usr/bin/seamonkey myusr 3773 4.7 8.6 4196428
1357632 ? Sl 09:55 6:02 /usr/lib64/seamonkey/seamonkey-bin >>> myusr 9956 0.0 0.0 7720 764 pts/1 S+ 12:01 0:00 grep
--color=auto -e monkey
seamonkey-bin has used 6:02, so you want to issue "kill 3773".
So, in my case, ....
[daniel@localhost ~]$ ps aux | grep -e monkey
daniel 3275 8.3 35.2 4356784 1389556 ? Sl 18:48 17:50 >> /home/daniel/seamonkey_2/SeaMonkey_2_53_6/seamonkey/seamonkey
--sm-client-id 1028c1d320b210000167948698700000031840012
daniel 7856 0.0 0.0 12296 864 pts/0 S+ 22:21 0:00 grep
--color -e monkey
[daniel@localhost ~]$ ^C
[daniel@localhost ~]$
So I'm guessing you would call that 'one (good)' entry
Your reply copy/pasted to my Linuxstuff file .... so, hopefully, I
don't ask again!! ;-(
Process 3275 has been open since 18:48 and has accumulated 17:50. You
only have one seamonkey process, I have two during normal operation
although one just sits there.
If you had previusly closed Seamonkey when you got that display, you
would need to kill 3275 to finish the job. I never "kill" unless normal methods have failed.
on MageiaLinux 6 with KDE Desktop/ on a Dual-booting (Win7/MGALinux
6) HP 6730 Laptop.
[daniel@localhost ~]$ ps aux | grep -e monkey
daniel 3275 8.3 35.2 4356784 1389556 ? Sl 18:48 17:50 /home/daniel/seamonkey_2/SeaMonkey_2_53_6/seamonkey/seamonkey
--sm-client-id 1028c1d320b210000167948698700000031840012
Daniel65 wrote:
on MageiaLinux 6 with KDE Desktop/ on a Dual-booting
(Win7/MGALinux
6) HP 6730 Laptop.
[daniel@localhost ~]$ ps aux | grep -e monkey
daniel   3275 8.3 35.2 4356784 1389556 ?    Sl Â
18:48Â 17:50
/home/daniel/seamonkey_2/SeaMonkey_2_53_6/seamonkey/seamonkey
--sm-client-id 1028c1d320b210000167948698700000031840012
Can you clarify:
How did you install it?
How do you start it (not sure where that "client id" is coming from)?
When you exit, you should use "File | Quit" (not the 'X') unless
you are sure there's only a single window open.
gerry 666uk wrote:
Daniel65 wrote:
on MageiaLinux 6 with KDE Desktop/ on a Dual-booting (Win7/MGALinux
6) HP 6730 Laptop.
[daniel@localhost ~]$ ps aux | grep -e monkey
daniel   3275 8.3 35.2 4356784 1389556 ?    Sl  18:48Â
17:50
/home/daniel/seamonkey_2/SeaMonkey_2_53_6/seamonkey/seamonkey
--sm-client-id 1028c1d320b210000167948698700000031840012
Can you clarify:
How did you install it?
How do you start it (not sure where that "client id" is coming from)?
When you exit, you should use "File | Quit" (not the 'X') unless you
are sure there's only a single window open.
I bet there is a linux option to only allow one instance of the program
to run.
Probably very complicated and might take time to figure out, but linux allows complete control of your computer.
There's probably a man page somewhere.
Try "barking up the wrong tree".
Daniel has clearly installed it "locally", the /home/daniel/seamonkey_2/SeaMonkey_2_53_6/seamonkey/seamonkey is a
honking great clue. Note that his user-agent says he is running 2.53.15 and not 2.53.6.
His system only shows one instance, mine shows two but that is because
one of them is a "start process" which starts the other one. I killed
the start process once and the other one - the real problem - continued.
Note that the programs being executed on my system have different names
and are in different directories, not much scope for enforcing "allow it
to run once only" there.
In Daniel's first post he says he gets an "already running" error. This shows that Seamonkey itself checks to see if it is already running, no
need to farm this out to Linux.
On 2023-03-24 04:52, Don Spam's Reckless Son wrote:
Try "barking up the wrong tree".
Daniel has clearly installed it "locally", the
/home/daniel/seamonkey_2/SeaMonkey_2_53_6/seamonkey/seamonkey is a
honking great clue. Note that his user-agent says he is running
2.53.15 and not 2.53.6.
His system only shows one instance, mine shows two but that is
because one of them is a "start process" which starts the other
one. I killed the start process once and the other one - the real
problem - continued. Note that the programs being executed on my
system have different names and are in different directories, not
much scope for enforcing "allow it to run once only" there.
In Daniel's first post he says he gets an "already running" error.
This shows that Seamonkey itself checks to see if it is already
running, no need to farm this out to Linux.
To start with, Daniel is running Mageia 6, which has been EOL since September 2019. He should install the current version, Mageia 8.
Mageia dropped Seamonkey, then called Iceape,
from their repos in April 2020, because of lack of a maintainer.
Users are advised that if they want it, they should download it and
install it themselves. Since version 2.53.15 was released in January
2023, this may be what Daniel has done, but not necessarily. From the Seamonkey website:
"Automatic upgrades from previous 2.53.x versions are enabled for
this release, but if you have problems with it upgrading or you need
to upgrade from a version earlier than 2.53.5, please download the
full installer from the downloads section and install SeaMonkey
2.53.15 manually over the previous version."
So it is quite possible that he has been receiving automatic updates
since version 2.53.6.
There is currently a new package request to restore Seamonkey to the
under development Mageia 9, but nothing has come of it. Yet. It has
been said in a comment in the package request that the version
downloaded from the vendor works just fine in Mageia 9, so it
probably works in Mageia 8, as well.
I repeat: Daniel needs to install Mageia 8.
TJ
There is currently a new package request to restore Seamonkey to the
under development Mageia 9, but nothing has come of it. Yet. It has
been said in a comment in the package request that the version
downloaded from the vendor works just fine in Mageia 9, so it
probably works in Mageia 8, as well.
I repeat: Daniel needs to install Mageia 8.
TJ
Yes, TJ ..... one day!! I have downloaded it and burnt it to DVD (12
months or more ago!!), but, as 'they' say .... 'If it ain't broken,
don't fix it!!'
On 2023-03-25, Daniel65 <daniel47@nomail.afraid.org> wrote:
There is currently a new package request to restore Seamonkey to the
under development Mageia 9, but nothing has come of it. Yet. It has
been said in a comment in the package request that the version
downloaded from the vendor works just fine in Mageia 9, so it
probably works in Mageia 8, as well.
I repeat: Daniel needs to install Mageia 8.
TJ
Yes, TJ ..... one day!! I have downloaded it and burnt it to DVD (12
months or more ago!!), but, as 'they' say .... 'If it ain't broken,
don't fix it!!'
Except the suggestion is that Mga8 IS broken and you have been running
into the sharp shards while trying to run Seamonkey.
Mageia dropped Seamonkey, then called Iceape,
No. SeaMonkey directly followed from Mozilla Suite .... Iceape was then
an off-shoot of SeaMonkey Suite.
William Unruh wrote on 25/3/23 3:11 pm:
On 2023-03-25, Daniel65 <daniel47@nomail.afraid.org> wrote:Oh!! Well, just as well that I'm still on MGA6 then, William! ;-P
There is currently a new package request to restore Seamonkey to the
under development Mageia 9, but nothing has come of it. Yet. It has
been said in a comment in the package request that the version
downloaded from the vendor works just fine in Mageia 9, so it
probably works in Mageia 8, as well.
I repeat: Daniel needs to install Mageia 8.
TJ
Yes, TJ ..... one day!! I have downloaded it and burnt it to DVD (12
months or more ago!!), but, as 'they' say .... 'If it ain't broken,
don't fix it!!'
Except the suggestion is that Mga8 IS broken and you have been running
into the sharp shards while trying to run Seamonkey.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 371 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 174:46:56 |
| Calls: | 7,915 |
| Files: | 12,983 |
| Messages: | 5,797,723 |