Closed Bug 1524762 Opened 6 years ago Closed 6 years ago

External APP no longer opens TB 65.0b4 to send e-mails

Categories

(Thunderbird :: Untriaged, defect)

Product:
Thunderbird
Component:
Untriaged
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: nolanktx, Unassigned)

Details

Attachments

(5 files)

TB-warningbanner.JPG
20.72 KB, image/jpeg
Details
E5430-specs.JPG
40.32 KB, image/jpeg
Details
TB_MS-Error-Log-Data_022019.txt
4.69 KB, text/plain
Details
TB_MS-Error-Log-Data_022119.txt
4.73 KB, text/plain
Details
Debug_Log4OM.JPG
42.39 KB, image/jpeg
Details

User Agent: Mozilla/5.0 (Windows NT 10.0; rv:65.0) Gecko/20100101 Firefox/65.0

Steps to reproduce:

External app I use generates PDF reports and invokes default email client (TB) to configure and send the email with PDF file either attached or link inserted in message to recipient/client.

Actual results:

My external app has been working flawlessly doing the above until TB 65.0b4 was installed. Now I get a flag message noting than an external program is attempting to access TB and do I agree or not.
I clicked OK and TB shut down and does not send emails.
I reinstalled 65.0b3 and my app's access is restored and functioning again.

Expected results:

External app should have brought up TB and brought a 'write email panel' to the forefront so I could ensure all is in order, make modifications to the message if needed and then click 'send'.
Again ... this has been working fine until 65.0b4 was installed.

Attached image TB-warningbanner.JPG —

Warning flag presented by TB 65.0b4 when external APP reaches out to TB to send a message.

I have tested this several times and 65.0b4 provides warning flag that external APP is accessing TB and asking for yes/no to proceed. Once I click YES, TB just shuts down.

I've reverted back to TB 65.0b3 and my APP is able to enable TB and complete the process of sending the e-mail with file link inserted or PDF attached.

I've attached a JPG of the warning flag I get from TB 65.0b4. Once the response is made TB just shuts down.

I've tested with TB both in an OFF condition and and ON condition (IE: running the background).

Regards - Nolan K.
Plano, TX

I've tested again with TB 66.0b1 and the same routine happens. When my external program calls for TB to send an e-mail the warning banner I added above appears and when I click OK TB simply shuts down.

Works fine with TB 65.0b3 ...

Hiccup appeared with TB 65.0b4

Regards - Nolan K.
Plano, TX

Yes, we've introduced MAPI changes in TB 65 b3 and TB 65 b4:
https://www-stage.thunderbird.net/en-US/thunderbird/65.0beta/releasenotes/

You're confirming that the first batch in beta 3 was fine, so that's promising.

Are you using a 32bit or 64 bit version of TB? Can you try TB 66 beta 2 (due out soon) which reverts one of the changes.

Mike, does this report ring a bell? Related to bug 1509918 which is about registration.

I've also had reports that with the set of MAPI changes people also get:
"Either there is no default mail client or the current mail client cannot fulfill the messaging request. Please run Microsoft Outlook and set it as the default mail client".

Flags: needinfo?(mikekaganski)

The message looks like some unexpected data comes in lpOriginator of MapiMessage(W) struct (which would explain to me why TB thinks that there's an unauthorized attempt - trying to set "From:" to some data other than current account). This might be related to the crashes we saw - why some unexpected data comes there? memory corruption?

I badly miss a way to reproduce any of the problems myself :-( - is that an application available for testing?

Flags: needinfo?(mikekaganski)

All,

I'm using a 32 bit version of TB.

You can easily replicate the hiccup simply by right-clicking on a file from Windows Explorer or other file manager application (I usually choose a jpg or pdf) and select "Send To" then "Mail Recipient". I get the same warning banner and once I click "OK" TB will close down.

I have TB running on two different laptops and experience the same with both units. Also allows me to keep on set at 65.0b3 so I can continue to get some of my consulting work done where I ship out documents using the MAPI routine.

Thanks so much for looking at this.

Cheers - Nolan K.
Plano, TX

PS: Sorry for me having two logins, but I'm in the process of changing e-mail addresses so ended up with two entries due to that as I just could not change the first e-mail address ... unless I missed that button in the profile.

@Mike: Looks like the W-API is be-W-itched ;-)

@Nolan: Yes, you can change your e-mail address at BMO somewhere in the settings.

@Jorg: Found the spot, changed it, confirmed it. Will keep fingers crossed the ticket will track to the new e-mail.

(In reply to u633214 from comment #6)

I'm using a 32 bit version of TB.

You can easily replicate the hiccup simply by right-clicking on a file from Windows Explorer or other file manager application (I usually choose a jpg or pdf) and select "Send To" then "Mail Recipient". I get the same warning banner and once I click "OK" TB will close down.

If it were that easy.
http://youtu.be/VG7tCCSmjUY?hd=1

Something crucial is missing.

Here's the same on Win10: http://youtu.be/NTV01Yo-eKc?hd=1

Attached image E5430-specs.JPG —

@Mike - The wonderment of computers for sure. ;-)

Could there be some strange setting I've made on both of my laptops that cause that or maybe a rogue MAPI related file?

I have Thunderbird selected as the default E-mail APP.
I have "Microsoft Office Professional Plus 2016 - en-us" installed as well.
Just completed the recent cumulative MS update yesterday on both laptops as well.

I've attached a screen clip of the specs from my 'main' laptop that I use as the daily-driver.

FWIW - I noted that when you did the routine to Mail To that send/write e-mail panel popped to the top of the stack of APPs you had open/running. That does not happen on my laptop. I note a flashing/glowing on the TB icon in the tray and mouse over and then have to select that newly established send/write panel to bring it to the top. I'm pretty sure that is a Windows setting I have to tweak somewhere.

Cheers - Nolan K.

Hmm... 32-bit OS. Need to test that.

Nolan, we'll be shipping TB 60.5.2 with some MAPI changes soon, could you try these versions for me:

32bit: https://queue.taskcluster.net/v1/task/SDiVr61sQCqiZnqMmwlFaQ/runs/0/artifacts/public/build/install/sea/target.installer.exe
64bit: https://queue.taskcluster.net/v1/task/Vw7-kZSGTValUggFd08GMQ/runs/0/artifacts/public/build/install/sea/target.installer.exe

The latter works fine for me on Win10 64bit, I haven't tried the former.

Mike - The 32bit version worked fine.

I tested via the Mail To from inside Windows Explorer and also my inspection report software that takes the same route.
Both worked just fine.

I'm still searching why that called for "write/send" panel in TB doesn't pop to the top of the stack, but that is another issue.

Cheers - Nolan K.

Nolan, thanks for testing, how about the latest TB 66 beta 2:
https://archive.mozilla.org/pub/thunderbird/candidates/66.0b2-candidates/build2/win32/en-US/Thunderbird%20Setup%2066.0b2.exe

I guess on a 32bit OS you can't run 64 executables?

Jorg,

I tried (just to verify) but 64Bit exe's won't run under 32Bit OS. Got banner advising same.

I installed the TB 66 beta 2 and did the tests and it worked fine from both the Mail To approach in Explorer and from the inspection software I use for reports.

Looking good.

Cheers - Nolan K.

FWIW - I recall a many-month issue Microsoft had with MAPI use when they did a huge release approximately in April/May-2018.

When selecting a file via Mail To, etc. it (Windows 10) would always default to Outlook. Made no difference if one selected TB as the default e-mail client or not. It was a strange problem and seemed to manifest itself with a few different varieties depending upon one's OS version, etc..

I found a lot of chatter/complaints for several months and then (all of a sudden) it was repaired/corrected with an OS update in July or August. I don't even recall if there were any file notes about the correct either, but the problem disappeared so that now the user could actually make TB the default client or a "quill pen" if desired ... :-) ..

Cheers - Nolan K.

OK, thanks for testing, you have two working versions to choose from then: 60.5.2 and 66 beta 2.

Damn. Installed a Win10 Pro 1809 x32 en_US anew; installed TB 65.0b4; and they happily work! :-( Upgraded to 66.0b1 - and they continue to work.

Jorg: is that possible to add some logging to the binaries, and ask Nolan to test again? Just logging the struct data from MAPI DLL and from the W-API to some external text files would help alot IIUC? Binaries must be built for release, like the betas, to make sure we catch the problem...

Hmm, there's MAPI logging, that's all I know.

Ah by the way, in LibreOffice, we have this wiki [1] to help users to prepare a backtrace and minidumps of the crash. Possibly it could be useful here? Nolan, could you please try to produce a minidump of thunderbird.exe (65.0b4 or 66.0b1) when it crashes? Sending it here could hopefully enable me to load it to a debugger and see the problematic data?

[1] https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg

Error log with event 02/20/19 from my backup laptop. This is from the MS Event Viewer.

Error log from my main laptop right after I updated it to TB 66.0b1 just a few minutes ago.

Attached image Debug_Log4OM.JPG —

On my backup laptop (I use mostly for my ham radio hobby) I have an application known as: Log4OM ... It is written by a fellow in Italy and I'm part of the beta testing of that application. It logs calls made on our ham radios and has a bunch of connections to various APPs for a more integrated operation.

The developer has logging/debugging routines that run pretty much all the time or we can also enable more detailed looks to try and capture to/fro codes to help trouble-shoot issues.

I've included a screen clip of those routines from the drop-down menu.

The program is free to install/use. http://www.log4om.com/

Cheers - Nolan K.

(In reply to NolanK from comment #23 - comment #25)

Unfortunately, the logs are not useful here. What I meant was creating a minidump - which can be done using ProcDump utility [1] from Microsoft/Sysinternals. When you have Thunderbird running, you can launch ProcDump using a command line like

d:\procdump4.01>procdump.exe thunderbird.exe -h

and then do whatever is required to crash Thunderbird. Then ProcDump would (hopefully) emit a diagnostic in its console, like this:

d:\procdump4.01>procdump.exe thunderbird.exe -h
ProcDump v4.0 - Writes process dump files
Copyright (C) 2009-2011 Mark Russinovich
Sysinternals - www.sysinternals.com
Process: thunderbird.exe (1964)
CPU threshold: n/a
Performance counter: n/a
Commit threshold: n/a
Threshold seconds: n/a
Number of dumps: 1
Hung window check: Enabled
Exception monitor: Disabled
Terminate monitor: Disabled
Dump file: d:\procdump4.01\thunderbird.dmp
[09:02.39] Hung window detected.
Writing dump file d:\procdump4.01\thunderbird_120614_090239.dmp ...
Dump written.
Dump count reached.
d:\procdump4.01>

and tell you where the created minidump file is put, which you hopefully could then upload here.

[1] http://technet.microsoft.com/en-us/sysinternals/dd996900

Mike,

Tnx for the help and direction with ProcDump. I have it downloaded, but not yet installed.

I reverted back to 65.0b4 to test the "shut-down" to see if it would repeat. Well ... it did NOT shut down TB when I tested.

I'm guessing that whatever tweak y'all did has held through the basic code and DOES allow the MAPI to function as intended.

I experienced the same thing on both of my laptops.

I have both of them now running the most current beta release.

Keeping fingers crossed that it all holds.

Cheers - Nolan K.
Plano, TX

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: