Multiple entries in messaging menu

Thank you for your bug report.
Could you please run Thunderbird from the command line and report any error messages that you get when it crashes?
Could you also report any error messages from the Error console? (Tools->Error console)
Thanks in advance!

Running from the command line I get a crash with a "Segmentation fault" and am left with an orphaned Thunderbird Indicator menu section. The next restart of TB I get another section.

Could you please test this again using the latest version?
Thanks in advace!

Latest version of TB or Thunderbird Indicator? I'm currently using 3.1.7pre of TB with 1.1 Indicator and it is still happening.

I have the same problem. I had issued a killall TB from the command line (no crash) and discovered a duplicate entry in the messaging menu upon reloading TB. TB 3.1.7 with indicator applet 1.1

I'm hitting this on xul-ext-indicator 1.3.1-0ubuntu1

Here's how it looks for me, when I've closed thunderbird.

I'm experiencing this same issue after having to kill an instance of Thunderbird yesterday. The entry has persisted between sessions (i.e. a reboot doesn't rid me of it). I vaguely recall something similar happening a while back, and having to issue a command to clear the errant entry. However, I can't for the life of me recall what that command was and Google has not been my friend on this one.

Anyone have any ideas how one might flush out a persistent, yet erroneous entry from the messaging menu?

Eureka!

I've managed to remove the erroneous entry from the messaging menu by typing the following into a terminal:

ps aux | grep thunderbird

This gave the following output:

ch2lah 2868 0.0 0.5 208492 20412 ? S Feb21 0:00 python /<email address hidden>/python/indicator.py thunderbird.tbindicator.default-fifo867
ch2lah 27950 0.0 0.0 8960 876 pts/1 S+ 01:13 0:00 grep --color=auto thunderbird

Which clearly shows an erroneous background process (possible a vestige of the session of Thunderbird that I unceremoniously killed) with a PID of 2868. After killing that process (sudo kill 2868) and removing/re-adding the indicator-applet the erroneous extra entry was gone. I hope that at least enables the rest of you to rid yourselves of those pesky duplicates.

Kind Regards,

Lee Hyde.

Hi,
I added a few lines to indicator.py & the problem is taken care of... well mostly.
Developer: Please try this & let me know, if it is useful.

1. Add "import time" at the start of the script, where different external modules are imported.

2. After the line:
if __name__ == "__main__":

Add below code:
----------------------
    #Kill previous orphan instances
    os.system("bash -c \"eval `ps -ef | grep \\\"indicator.py\\\" | grep -v grep | awk '{if (($3==1) && ($1 == \\\"%s\\\")) printf \\\"kill -9 %%d;\\\", $2}'`\"" % getpass.getuser())
    time.sleep(1)

    #Exit, if new window is opened from same thunderbird window (there may exist better ways of doing it.)
    fp = open("/tmp/.tbIndicator.lock", 'w')
    try:
        fcntl.lockf(fp, fcntl.LOCK_EX | fcntl.LOCK_NB)
    except IOError:
        #os.system("zenity --info --text='could not get lock' &")
        sys.exit(0)
----------------------

tried & tested with most corner cases, which I could think of. Please check from your end. :-)

Hi,
I added a few lines to indicator.py & the problem is taken care of... well mostly.
Developer: Please try this & let me know, if it is useful.

1. Add "import time, fcntl, getpass" at the start of the script, where different external modules are imported.

2. After the line:
if __name__ == "__main__":

Add below code:
----------------------
    #Kill previous orphan instances
    os.system("bash -c \"eval `ps -ef | grep \\\"indicator.py\\\" | grep -v grep | awk '{if (($3==1) && ($1 == \\\"%s\\\")) printf \\\"kill -9 %%d;\\\", $2}'`\"" % getpass.getuser())
    time.sleep(1)

    #Exit, if new window is opened from same thunderbird window (there may exist better ways of doing it.)
    fp = open("/tmp/.tbIndicator.lock", 'w')
    try:
        fcntl.lockf(fp, fcntl.LOCK_EX | fcntl.LOCK_NB)
    except IOError:
        #os.system("zenity --info --text='could not get lock' &")
        sys.exit(0)
----------------------

tried & tested with most corner cases, which I could think of. Please check from your end. :-)
You may also check the patch attached.