** Description changed:

  Binary package hint: gnome-panel
  
  I filed this bug using the PID of the clock-applet and ubuntu bug, but I 
think the clock-applet only shows a symptom, Here is
  a description :
  
  Expected Behaviour :
  Clock-applet displays the correct time,
  
  Observed Behaviour :
  Displayed time is drifting
  
  How to reproduce :
  
  If I get away from my computer for some times, the time displayed by the
  clock applet drifts. But the date command also show the wrong time.
  Moreover, sleep interval also get wrong. To debug this, I tested the
  following script :
  
  #!/bin/bash
  while [[ true ]]
  do
-     date >> clocktest.log
-     hwclock >> clocktest.log
-     sleep 300
+     date >> clocktest.log
+     hwclock >> clocktest.log
+     sleep 300
  done
  
  Must be run as root because of hwclock.
  Il launched it : ./clocktest.sh &
  and got away from my computer
  
  Here is the output log :
  
  1 mardi 17 août 2010, 12:42:12 (UTC+0200)
  2 mar. 17 août 2010 12:42:13 CEST -0.346882 secondes
  3 mardi 17 août 2010, 12:47:13 (UTC+0200)
  4 mar. 17 août 2010 12:57:13 CEST -0.080965 secondes
  5 mardi 17 août 2010, 12:52:13 (UTC+0200)
  6 mar. 17 août 2010 13:02:14 CEST -1.002776 secondes
  7 mardi 17 août 2010, 12:57:18 (UTC+0200)
  8 mar. 17 août 2010 13:07:18 CEST -0.063633 secondes
  9 mardi 17 août 2010, 13:02:18 (UTC+0200)
  10 mar. 17 août 2010 13:12:19 CEST -0.361501 secondes
  11 mardi 17 août 2010, 13:07:19 (UTC+0200)
  12 mar. 17 août 2010 13:17:20 CEST -0.987434 secondes
  
  Line 1 and 2 show the first time through the loop.
  Line 3 and 4 show the bug :
  while date (and sleep) thinks 5 minutes have elapsed, hwclock shows that 15 
minutes have elapsed.
  
  Line 5 to 12 shows normal behaviour, except now date is late by 10 minutes.
  Behaviour is normal because I was back at my desk using the computer.
  
- Having clock applet displaying the wrong time is one thing, but having
- the whole system time wrong (since sleep gets confused too) is a major
- bug.
+ Additional info :
+ * Hardware is an Amilo xi2550
+ * If I keep the computer busy, for example building a kernel, and I go away, 
clock works a expected,
+ and so does the screen locking mechanism.
+ * Everything was working fine with 8.04
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-panel 1:2.30.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic i686
  Architecture: i386
  Date: Wed Aug 18 09:43:59 2010
  ExecutablePath: /usr/lib/gnome-panel/clock-applet
  ProcEnviron:
-  LANG=fr_FR.utf8
-  PATH=(custom, user)
-  SHELL=/bin/bash
+  LANG=fr_FR.utf8
+  PATH=(custom, user)
+  SHELL=/bin/bash
  SourcePackage: gnome-panel
  XsessionErrors:
-  (polkit-gnome-authentication-agent-1:1990): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
-  (gnome-terminal:2235): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion 
`entry != NULL && entry->lock_count > 0' failed
-  (<unknown>:2763): Gdk-WARNING **: XID collision, trouble ahead
-  (<unknown>:2763): Gdk-WARNING **: XID collision, trouble ahead
+  (polkit-gnome-authentication-agent-1:1990): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
+  (gnome-terminal:2235): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion 
`entry != NULL && entry->lock_count > 0' failed
+  (<unknown>:2763): Gdk-WARNING **: XID collision, trouble ahead
+  (<unknown>:2763): Gdk-WARNING **: XID collision, trouble ahead

-- 
Clock drifts during inactivity
https://bugs.launchpad.net/bugs/619677
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to