ค้นหาฝ่ายสนับสนุน

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

เรียนรู้เพิ่มเติม

Bug: Year field accepts more than 4 chars in Lightning, causes crash

  • 4 การตอบกลับ
  • 0 คนมีปัญหานี้
  • 19 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย RedXIII

more options

How can I submit a defect for Thunderbird / Lightning calendar? I'm not sure about using Bugzilla myself.

I was typing a bit fast and accidently entered 4 chars for the year on a new calendar event and saved it. After that the event vanished from the calendar. I used Events and Tasks > Find events to locate it but when I clicked on it Thunderbird crashed.

How can I submit a defect for Thunderbird / Lightning calendar? I'm not sure about using Bugzilla myself. I was typing a bit fast and accidently entered 4 chars for the year on a new calendar event and saved it. After that the event vanished from the calendar. I used Events and Tasks > Find events to locate it but when I clicked on it Thunderbird crashed.

การตอบกลับทั้งหมด (4)

more options

Help > More Troubleshooting Info > scroll to Crash Reports for the Last 3 Days > View > click on Bugzilla tab > click on "Create a bug: Thunderbird"

เปลี่ยนแปลงโดย Wayne Mery เมื่อ

more options

Wayne Mery said

Help > More Troubleshooting Info > scroll to Crash Reports for the Last 3 Days > View > click on Bugzilla tab > click on "Create a bug: Thunderbird"

Thanks, that was really helpful. The only thing is that there's no calendar in the components field when creating the bug. So I selected addons as Lightning used to be a separate addon.

เปลี่ยนแปลงโดย Wayne Mery เมื่อ

more options

This problem shows that the developers of TB are not subjected to any quality assurance procedure.

more options

Wayne Mery said

Help > More Troubleshooting Info > scroll to bold textCrash Reports for the Last 3 Days > View > click on Bugzilla tab > click on "Create a bug: Thunderbird"

I managed to raise a bug in bugzilla anyway:

https://bugzilla.mozilla.org/show_bug.cgi?id=1780918#c6