Closed Bug 1257190 Opened 10 years ago Closed 10 years ago

Export calendar causes complete hang

Categories

(Calendar :: Import and Export, defect)

Lightning 4.0.7
x86_64
Windows 8.1
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: silverbacknet, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0 Build ID: 20160307215824 Steps to reproduce: Lightning is actually version 4.0.7, which isn't listed in the dropdown. Thunderbird is 38.7.0. Steps to reproduce: - Start a completely clean new profile. - Enter any new Calendar appointment. - Right-click to export the Calendar. Actual results: Thunderbird hangs for at least five minutes (never left it longer). No CPU is used. Nothing shows up in the error console at all. Expected results: The Calendar export dialog should have shown up as usual.
OS: Unspecified → Windows 8.1
Hardware: Unspecified → x86_64
Works for me, i.e. no hang and file picker dialog is displayed when executing the steps from above. Tested Lightning 4.0.7 with Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 (Build-ID 20160310150025) Tested Lightning 4.9a2 with Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Thunderbird/47.0a2 (Build-ID 20160316004028) Is it possible that the file picker dialog is displayed, but maybe on different monitor or behind some other window? This might look like a hang because Thunderbird is waiting for the file picker dialog to be closed.
Flags: needinfo?(silverbacknet)
After putting the system to sleep and waking, the file picker now shows. If it was offscreen, I have no idea where it could have been, because TB was the only thing running for the test, and the second monitor was empty the whole time, except a couple tests with the console open. Next time I'll use keyboard shortcuts to see if it pops back onto the screen again. In the meantime, it's WFM now.
Flags: needinfo?(silverbacknet)
Version: Lightning 4.0.6 → Lightning 4.0.7
Resolving as WFM per comment 2. Please reopen if problem occurs again or if you are able to reproduce the problem.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.