On Wednesday 09 July 2008 13:23:26 Stuart Sears wrote:
> Lisi wrote:
> > On Wednesday 09 July 2008 11:06:41 Chris Smith wrote:
> >> Lisi wrote:
> >>> Did that, and did mv 59uwmlpn.default again. Now if I try to start
> >>> Thunderbird, I have:
> >>>
> >>> <quote> Thunderbird is already running but is not responding. To open
> >>> a new window you must first close the existing Thunderbird process, or
> >>> restart your system. </quote>
> >>
> >> look inside 59uwmlpn.default for a link called 'lock' and delete it.
> >> There may also be an empty file called '.parentlock', I don't know if
> >> that also needs to be deleted.
> >
> > The only file that I can see with *lock* is blocklist.xml. I don't
> > expect that that is it?
>
> no, I doubt it.
>
> does thunderbird appear in the output of ps -ef | grep thunder ?
<quote>
[root@Dozy peter]# ps -ef | grep thunder
root 4095 4055 0 17:32 pts/3 00:00:00 grep --color thunder
[root@Dozy peter]# kill 4095 4055
bash: kill: (4095) - No such process
[root@Dozy peter]# kill 4055
[root@Dozy peter]# ps -ef | grep thunder
root 4097 4055 0 17:33 pts/3 00:00:00 grep --color thunder
[root@Dozy peter]# ps -ef | grep thunderbird
root 4099 4055 0 17:33 pts/3 00:00:00 grep --color thunderbird
[root@Dozy peter]# kill 9 4055
bash: kill: (9) - No such process
[root@Dozy peter]# kill 4055
[root@Dozy peter]#
</quote>
At that point I again tried to launch Thunderbird, and got the same error
message as before. :-(
Lisi
