Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

XML parsing error when opening/creating calendar items

  • 2 trả lời
  • 4 gặp vấn đề này
  • 7 lượt xem
  • Trả lời mới nhất được viết bởi avamk

more options

Major Lightning blocker problem here:

I am running Thunderbird 52.5.0 64-bit on Red Had Enterprise Linux 7.1, both are fully updated.

Starting today, when I try to create or edit a calendar/event item, the "Edit item" window shows up but the whole window is filed with just this message:

"XML Parsing Error: undefined entity Location: chrome://lightning/content/lightning-item-iframe.xul Line Number 115, Column 7: <button id="counter-proposal-btn" <="" p="">


^"

This is a major problem for me because I rely on the calendaring functions of Thunderbird and this error completely destroys it! How do I troubleshoot and fix this?? Thank you.

</button>

Major Lightning blocker problem here: I am running Thunderbird 52.5.0 64-bit on Red Had Enterprise Linux 7.1, both are fully updated. Starting today, when I try to create or edit a calendar/event item, the "Edit item" window shows up but the whole window is filed with just this message: "XML Parsing Error: undefined entity Location: chrome://lightning/content/lightning-item-iframe.xul Line Number 115, Column 7: <button id="counter-proposal-btn" ------^" This is a major problem for me because I rely on the calendaring functions of Thunderbird and this error completely destroys it! How do I troubleshoot and fix this?? Thank you.

Tất cả các câu trả lời (2)

more options

I also have this exact error (message is word-for-word) on Thunderbird 52.5.2 (64-bit), Lightning 5.4.5.2. Running Fedora 27, fully updated. I cannot find any way to create an event and the edit item window freezes with this error (need to kill process).

Noticed it 2 days ago but it could have been there longer as I hadn't used the calendar over Christmas. Unfortunately it renders the calendar entirely unusable, at least for now...