Was this a clean install or an release upgrade?
Have you always had this problem in 10.10 or has it happened recently? Can you associate the behavior to an update, change in packages or software sources?
Are you able to reproduce this with the 10.10 LiveCD?
Was this a clean install or an release upgrade?
Have you always had this problem in 10.10 or has it happened recently? Can you associate the behavior to an update, change in packages or software sources?
Are you able to reproduce this with the 10.10 LiveCD?