[Bug 474102] Re: clock applet freezes for up to 2 seconds at a time

2021-03-26 Thread Alberts Muktupāvels
** Changed in: gnome-applets (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/474102 Title: clock applet freezes for up to 2 seconds at a time To

[Bug 474102] Re: clock applet freezes for up to 2 seconds at a time

2011-12-12 Thread Roberto Turturro
My system (10.04.3 32bit) is also affected. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/474102 Title: clock applet freezes for up to 2 seconds at a time To manage notifications about this bug

[Bug 474102] Re: clock applet freezes for up to 2 seconds at a time

2010-08-17 Thread markozu
On my system (10.04 32bit) the clock freezes completely too and the only way to get it working is to log out/log in. Cheers -- clock applet freezes for up to 2 seconds at a time https://bugs.launchpad.net/bugs/474102 You received this bug notification because you are a member of Ubuntu Desktop

[Bug 474102] Re: clock applet freezes for up to 2 seconds at a time

2010-06-07 Thread Chris Le Sueur
I have noticed this since at least 9.10, and it's still present in 10.04. I'm using a generic kernel, 1.8GHz Core2, and I seem to get a one-second freeze on average of once every ten seconds, but it's quite erratic, so that those delays could be quite close together. Also note that this is not a

[Bug 474102] Re: clock applet freezes for up to 2 seconds at a time

2010-05-27 Thread ettorevi
My clock applet freezes completely. Lucid x86_64. To reproduce (at least on my system): on the Indicator Applet select 'Chat'. Empaty appears, clock freezes Exit Empaty, open Pidgin if you have it installed (always from the Indicator Applet menu), clock restarts correctly -- clock applet

[Bug 474102] Re: clock applet freezes for up to 2 seconds at a time

2010-05-02 Thread menthurae
I'm having the clock skipping issue on my Ubuntu 10.04 32-bit install (EeePC 1000HE) - it appears to be fine on my 2 Ubuntu 10.04 64-bit installations (Q6600 Desktop, E8300 Desktop). I've set the time on all machines to update via NTP. Note that the time IS synchronised between all 3 machines -

[Bug 474102] Re: clock applet freezes for up to 2 seconds at a time

2010-01-27 Thread Bart Verwilst
I have it on my 32bit Karmic desktop, clocks counts per 2 seconds here :) No 64 bit machines to try on though :( -- clock applet freezes for up to 2 seconds at a time https://bugs.launchpad.net/bugs/474102 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which

[Bug 474102] Re: clock applet freezes for up to 2 seconds at a time

2010-01-06 Thread piratemurray
This affects me too with the same symptons as yoda was experiencing (time skipping for two seconds/ erratic seconds counting). I'll try the backtrace thing that Pedro mentioned. Just to confirm I'm running pretty much the same spec as yoda (Karmic x86 upgraded from Jaunty). I've got a Lucid 64 at

[Bug 474102] Re: clock applet freezes for up to 2 seconds at a time

2010-01-06 Thread piratemurray
All right the back trace didn't go as well as I'd like and this is the first time that I've tried to get one so I might be doing it incorrectly. I set up the debugging sources as described and tried to use gdb on gnome-panel with the assumption that this will provide you the required logs to use.

[Bug 474102] Re: clock applet freezes for up to 2 seconds at a time

2010-01-06 Thread piratemurray
I've stared at my clock for quite some time now. I don't observe this on my lucid 64 distribution. Is this something specific with 32 bit 64 bit distros? -- clock applet freezes for up to 2 seconds at a time https://bugs.launchpad.net/bugs/474102 You received this bug notification because you

[Bug 474102] Re: clock applet freezes for up to 2 seconds at a time

2009-12-04 Thread Pedro Villavicencio
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on