bugzilla.mozilla.org has resumed normal operation. Attachments prior to 2014 will be unavailable for a few days. This is tracked in Bug 1475801.
Please report any other irregularities here.

Control+s freezes "calendar entry" window



Lightning Only
5 years ago
3 years ago


(Reporter: L.I.A.R., Unassigned)



Lightning 2.6.2




5 years ago
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release)
Build ID: 20131028112446

Steps to reproduce:

- add/edit a calendar entry
- a "calendar entry" window opens up
- hit Control+s in this window

Actual results:

It is impossible for me to save the content and close this window with the button "Save&Close"...
Does not happen if I don't hit Control+s

Expected results:

Hitting Control+s should not freeze the window (is there any hidden key binding?)


5 years ago
Severity: normal → critical
Keywords: hang
Control + S should save the item without closing the dialog. It seems to be working for me, I'm not able to reproduce the frozen window.

Do you get any error messages in Tools -> Error Console?

Comment 2

5 years ago
The problem is happening all the time here.

The error console repeats endlessly the following message:
Timestamp: 11/13/2013 06:16:41 PM
Warning: Use of getAttributeNodeNS() is deprecated. Use getAttributeNS() instead.
Source File: resource://calendar/modules/calXMLUtils.jsm
Line: 32

Since it's repeated, I'm not sure it's related to the problem...

Comment 3

5 years ago
BTW, I'm using AwesomeWM and te following extensions:
- Lightning 2.6.2
- Messaging Menu and Unity Launcher...
- Provider for google calendar

Comment 4

3 years ago
No ill effects on Windows when using current daily build and lightning 4.4

Do you still see this?
Flags: needinfo?(sexxxenator)
Whiteboard: [closeme 2015-08-25]

Comment 5

3 years ago
Resolved per whiteboard
Last Resolved: 3 years ago
Flags: needinfo?(sexxxenator)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2015-08-25]
You need to log in before you can comment on or make changes to this bug.