Comment 7 for bug 253091

Revision history for this message
Rohan Dhruva (rohandhruva) wrote :

I am sorry, but I should have commented that time itself. This is not a bug. The problem was solved that time itself, by doing "killall -9 firefox" and then restarting firefox. Basically the problem arises due to firefox not "rebooting" itself properly. The problem should go away if you restart your computer, too - if you have the same problem as I did. As far as I am concerned, this bug should be marked closed.

Tiefflieger, can you please try the solution I've said?