Many thanks to Urs and George.
> In Debian 12 the default /etc/ntpsec/ntp.conf file contains the lines
>
> # Comment this out if you have a refclock and want it to be able to
> discipline
> # the clock by itself (e.g. if the system is not connected to the network).
> tos
On 9/24/24 07:07, Greg Wooledge wrote:
hobbit:~$ man ntpd
[...]
-g, --panicgate
Allow the first adjustment to be big. This option may appear an
unlimited number of times.
This isn't mentioned in my ntpsec docs. IMO it should be the default.
Thank for the advisor
On Tue, Sep 24, 2024 at 01:27:14 -0400, gene heskett wrote:
> I personally am running ntpsec here, making this box a level 2 src, and have
> redirected most of my machines to it. Nut as a client, ntpsec fails as it
> cannot slam the correct time at bootup, apparently only adjust drift. So
> clients
On 9/23/24 13:24, Steve Keller wrote:
Dan Ritter writes:
Does it work without the -6 option?
No, the same problem. And ntpq shows that IPv6 is also used, when -6
isn't given. But, my NTP server is used by other hosts in the network
and that works fine.
Does it work if you bring back the
Steve Keller writes:
> When I call ntpdate my-ntp.my-domain manually it steps the time as
> expected. But then, ntpd doesn't sync the local clock to the NTP
> server, although it seems to consider that server's clock stable:
>
> $ ntpq -p
>remote
-the-system-clock
5.1.2. Changes to packages that set the system clock
The ntp package, which used to be the default way to set the system
clock from a Network Time Protocol (NTP) server, has been replaced by
ntpsec.
When I did a bit of research I found this comment which seems similar
to your
Steve Keller wrote:
> Dan Ritter writes:
>
> > Does it work without the -6 option?
>
> No, the same problem. And ntpq shows that IPv6 is also used, when -6
> isn't given. But, my NTP server is used by other hosts in the network
> and that works fine.
>
> > Does it work if you bring back the
Dan Ritter writes:
> Does it work without the -6 option?
No, the same problem. And ntpq shows that IPv6 is also used, when -6
isn't given. But, my NTP server is used by other hosts in the network
and that works fine.
> Does it work if you bring back the pool servers?
Yes, it does. I get man
> server -6 my-ntp.my-domain
>
> When I call ntpdate my-ntp.my-domain manually it steps the time as
> expected. But then, ntpd doesn't sync the local clock to the NTP
> server, although it seems to consider that server's clock stable:
>
> $ ntpq -p
>r
ntpdate my-ntp.my-domain manually it steps the time as
expected. But then, ntpd doesn't sync the local clock to the NTP
server, although it seems to consider that server's clock stable:
$ ntpq -p
remote refid st t when poll reach delay offset
I have a clock icon on my desktop PC which opens on reboot and then remains
on the top right of the screen all the time.
However, for some reason it has moved (not sure how this happened) and is
now in the middle of the screen under my browser windows (so not visible).
I would like to move the
Your clock appears to be fast by the precise number of seconds it took
for your post to leave your computer and reach my mail server.
Arrived: Tue, 20 Sep 2022 19:16:05 +0100 (BST)
Posted: Tue, 20 Sep 2022 20:16:05 +0200
That's the output of a tiny script that I was just tweaking, that
On 2022-09-18, Richard Schires wrote:
> The problem that I am trying to resolve is getting the
> system clock and CMOS clock to match.
Why is that a problem?
other operating systems or virtual machines active
> > on this machine? That can get tricky.
> >
> > If there is only one, then it sounds like your timezone isn't
> > matching your expectations.
> >
> > The easiest method is to configure hardware clock as UTC
&g
at can get tricky.
>
> If there is only one, then it sounds like your timezone isn't
> matching your expectations.
>
> The easiest method is to configure hardware clock as UTC
> and specify your timezone, because that avoids messing
> around with the hardware clock every t
ne isn't
matching your expectations.
The easiest method is to configure hardware clock as UTC
and specify your timezone, because that avoids messing
around with the hardware clock every time that daylight saving
changes localtime changes, and avoids invalid/duplicate
timestamps.
The docs I would
I've been searching for an answer and keep going in a circle.
> > I hope you can help or direct me to someone who can. I am new to Linux.
> > I am using an HP ML150 G2 to run a tabletop CNC mill. The software is
> > LinuxCNC on Debian. The problem that I am trying to resolve i
NC on Debian. The problem that I am trying to resolve is getting the
> system clock and CMOS clock to match.
> If I set the time in the CMOS, reboot, the system time is five hours off.
> I can get the system clock set through the date command;
> sudo date -s "D M Y H:M:S"
>
I've been searching for an answer and keep going in a circle.
I hope you can help or direct me to someone who can. I am new to Linux.
I am using an HP ML150 G2 to run a tabletop CNC mill. The software is
LinuxCNC on Debian. The problem that I am trying to resolve is getting the
system cloc
On Thu, Apr 21, 2022 at 05:21:56PM -0400, Stefan Monnier wrote:
> > (When switching between Unix and Windows, I need t adjust the CMOS clock on
> > the next boot.)
>
> Side note: You could presumably skip this by configuring your Windows
> installs to use UTC for the
On 4/21/22 14:21, Stefan Monnier wrote:
(When switching between Unix and Windows, I need t adjust the CMOS clock on
the next boot.)
Side note: You could presumably skip this by configuring your Windows
installs to use UTC for the CMOS clock. See e.g.:
https://wiki.archlinux.org/title
thanks very much to all.
i almst missed this as it didn't show uyp in my inbox.
it sounds like there exist things that say the time or can be made to.
then i can use cron to run it or at for a one-off.
i have beep turned off [and currently pulseaudio purged] but videos
play sound with no problem
* Samuel Wales [22-03/20=Su 23:03 -0700]:
> [...] i want debian to tell me the time at certain times.
Nobody has yet mentioned the festival package, which is a full
text-to-speech system. Once you have that installed, you can use
cron or at jobs to speak whatever you want at specific times.
On Sun, 20 Mar 2022, Samuel Wales wrote:
i want debian to tell me the time at certain times. for example
tonight i have to take medicine at 2:40 am.
I second the suggestions of at and cron.
If you want a one-off reminder, use at.
If you want a regular reminder use cron. Cron has a lot of f
On Sun, 20 Mar 2022 23:03:52 -0700
Samuel Wales wrote:
> i use slock and turn off monitor with ddccontrol.
I use the monitors attached to my desktop for sound. I find that when
they are shut off, either manually or by the computer's power management
software, sound ceases to work (unlike my lapt
On Mon, Mar 21, 2022 at 01:21:19PM -0300, Chris Mitchell wrote:
> Personally, I would use a custom systemd timer unit for this. Systemd
> is already running most of your system, and it offers a scheduling
> syntax that is (AFAIK) more flexible than cron's, and (IMHO) much
> easier to read. For exam
#x27;ll simply announce the
current time whenever it's triggered, thus giving you a general-purpose
talking clock.
Note that if you make the timer/service unit pair "system" units (in
/etc/systemd/system), they'll run (as root) as long as the machine is
up and running. If you mak
Samuel Wales wrote:
> i have to have all lights and monitors off at night. but i have to
> know the time so i can take medicine.
>
> i want debian to tell me the time at certain times. for example
> tonight i have to take medicine at 2:40 am.
>
> here are ideas:
>
> - tell me time when i righ
i have to have all lights and monitors off at night. but i have to
know the time so i can take medicine.
i use slock and turn off monitor with ddccontrol. this might turn off
mouse and keyboard; i wouild have to check.
i want debian to tell me the time at certain times. for example
tonight i h
On 2/11/22, Anssi Saari wrote:
> José Luis González writes:
>
>> According to
>>
>> https://wiki.debian.org/DateTime
>>
>> There should be an /etc/adjtime file to configure the timezone for the
>> hardware clock. I have no such file in my Debian 11 lap
CC'ing back to the list.
On Fri, Feb 11, 2022 at 03:34:35PM +0100, José Luis González wrote:
> Would creating an /etc/adjtime as done by the postinst script be fine?
As far as I know, yes. Try it and see. The worst that can happen is
your clock will be wrong, but that's already the case, right?
José Luis González writes:
> According to
>
> https://wiki.debian.org/DateTime
>
> There should be an /etc/adjtime file to configure the timezone for the
> hardware clock. I have no such file in my Debian 11 laptop. May I know
> if the file was removed and what was it repla
On Fri, Feb 11, 2022 at 12:54:01PM +0100, José Luis González wrote:
> According to
>
> https://wiki.debian.org/DateTime
>
> There should be an /etc/adjtime file to configure the timezone for the
> hardware clock.
That's... not how I'd describe that file, but I sup
According to
https://wiki.debian.org/DateTime
There should be an /etc/adjtime file to configure the timezone for the
hardware clock. I have no such file in my Debian 11 laptop. May I know
if the file was removed and what was it replaced with?
I just want to set the hardware clock to local time
On Mi, 01 mai 19, 11:33:23, Hans wrote:
> Hi folks,
>
> I am running into the little issue, that I can not set the clock in plasma5
> (KDE). Neither as a normal user nor as root.
>
> I want to set the clock using systemd to set the time automatically, but when
> ever I
Hi folks,
I am running into the little issue, that I can not set the clock in plasma5
(KDE). Neither as a normal user nor as root.
I want to set the clock using systemd to set the time automatically, but when
ever I want set the hook and confirmed the correct password of root, the
settting is
On Thu, Jun 07, 2018 at 11:06:12PM +0300, Abdullah Ramazanoğlu wrote:
> On Thu, 7 Jun 2018 19:32:35 +0100 Mike said:
>
> [--8<--]
>
> > In the end I used adjtimex -t 10065 -f 3058784 to speed the clock up a
> > bit and that has allowed NTP to be able to keep it und
they were failing sanity.
After a restart and resync of the NTP daemon, the same thing was
happening, after about five minutes, all of the servers would fail
sanity and get rejected.
Upon further investigation, I noticed that the system time was drifting
away from the hardware clock at a fairly alarming
hich is what I have
>>with
>>a Linux STB providing no LOCAL option and multiple OS/2's providing no UTC
>>option.
> I'm afraid I don't understand how things like old standalone boxes
> impact what makes sense going forward. You do understand that there'
t; > Unfortunately, I have other OSes on this system and they are
> > configured for the hardware clock set to local time. I need to keep
> > it that way.
>
> Um... OK. This sudden reversal is confusing to me, but if you've got
> it dual-booting between Windows and Lin
roviding no UTC
option.
I'm afraid I don't understand how things like old standalone boxes
impact what makes sense going forward. You do understand that there's no
relationship between the RTC clock and the displayed time? (That is, you
can set the RTC to UTC and still interact
Michael Stone composed on 2018-05-21 09:10 (UTC-0400):
> On Sun, May 20, 2018 at 12:15:05PM -0700, Patrick Bartek wrote:
>>Unfortunately, I have other OSes on this system and they are configured
>>for the hardware clock set to local time. I need to keep it that way.
> F
On Sun, May 20, 2018 at 12:15:05PM -0700, Patrick Bartek wrote:
Unfortunately, I have other OSes on this system and they are configured
for the hardware clock set to local time. I need to keep it that way.
For what it's worth, you'll have less long term pain if you also
configure th
figured
> for the hardware clock set to local time. I need to keep it that way.
Um... OK. This sudden reversal is confusing to me, but if you've got
it dual-booting between Windows and Linux, then setting the HW clock to
local time may be your simplest option.
In past versions of Debian,
ink.
> >
> > tzdata sets the local time zone. Mine is correctly set The
> > problem is the system "thinks" the hardware clock is set to UTC when
> > It's really set to local time. So, the time shown for my local time
> > zone is incorrect.
> >
UTC instead of Local for the hardware
>> > clock time. Honestly, I thought the clock was set to UTC. Haven't
>> > installed any other OS on this system since Wheezy 5 years ago. So,
>> > now system time on Stretch is 7 hours earlier than it should be --
>> > dif
t; option, etc., to correct this but is there an easier way?
> >
> > # dpkg-reconfigure tzdata
> >
> > should do it, I think.
>
> tzdata sets the local time zone. Mine is correctly set The
> problem is the system "thinks" the hardware clock is set
On Sat, 19 May 2018 10:37:39 +1000 Ben Finney
wrote:
> Patrick Bartek writes:
>
> > I could use hwclock --set --date= with the --localtime
> > option, etc., to correct this but is there an easier way?
>
> There is only one clock involved in this: the hardware cl
On Fri, 18 May 2018 20:59:25 -0500 David Wright
wrote:
> On Fri 18 May 2018 at 17:13:07 (-0700), Patrick Bartek wrote:
> > Okay, it's my fault: I admit it. During the Base Only, Terminal-only
> > install of Stretch, I clicked UTC instead of Local for the hardware
> &g
ata
>
> should do it, I think.
tzdata sets the local time zone. Mine is correctly set The
problem is the system "thinks" the hardware clock is set to UTC when
It's really set to local time. So, the time shown for my local time
zone is incorrect.
Anyway, thanks for your suggestion.
B
On Fri 18 May 2018 at 17:13:07 (-0700), Patrick Bartek wrote:
> Okay, it's my fault: I admit it. During the Base Only, Terminal-only
> install of Stretch, I clicked UTC instead of Local for the hardware
> clock time. Honestly, I thought the clock was set to UTC. Haven't
> ins
Patrick Bartek writes:
> I could use hwclock --set --date= with the --localtime
> option, etc., to correct this but is there an easier way?
There is only one clock involved in this: the hardware clock.
By telling the operating system that your hardware clock is set to UTC,
you have to
Okay, it's my fault: I admit it. During the Base Only, Terminal-only
install of Stretch, I clicked UTC instead of Local for the hardware
clock time. Honestly, I thought the clock was set to UTC. Haven't
installed any other OS on this system since Wheezy 5 years ago. So, now
system time
On 08/11/17 04:57, John Ratliff wrote:
On Wed, Aug 09, 2017 at 05:13:55PM -0700, David Christensen wrote:
Time Settings
Timezone PST8PDT
Appearance
Layout Digital
Tooltip format Wednesday 09 August 2017
Clock Options
Format
On 08/10/17 06:52, Charlie Kravetz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 9 Aug 2017 22:48:37 -0700
David Christensen wrote:
On 08/09/17 21:47, Charlie Kravetz wrote:
It almost sounds like the panel is too long for the monitor. The clock
is disappearing off the end
to use the Xfce panel "clock" item. Unfortunately, it
is broken:
- If I right-click on the Xfce panel and choose "Panel
Preferences...", the "Panel" dialog appears.
- Selecting Panel -> Items tab, "Clock" appears in the list of
panel items.
- If I s
On 08/11/17 03:39, Dan Ritter wrote:
On Wed, Aug 09, 2017 at 05:13:55PM -0700, David Christensen wrote:
Time Settings
Timezone PST8PDT
Appearance
Layout Digital
Tooltip format Wednesday 09 August 2017
Clock Options
Format
> On Wed, Aug 09, 2017 at 05:13:55PM -0700, David Christensen wrote:
>> Time Settings
>> Timezone PST8PDT
>> Appearance
>> Layout Digital
>> Tooltip format Wednesday 09 August 2017
>> Clock Options
>>
On Wed, Aug 09, 2017 at 05:13:55PM -0700, David Christensen wrote:
> Time Settings
> TimezonePST8PDT
> Appearance
> Layout Digital
> Tooltip format Wednesday 09 August 2017
> Clock Options
> Format 05:04:5
08-09 16:59:22 root@tinkywinky ~ # dpkg-query --show xfce4
> xfce44.12.3
>
>
> I would like to use the Xfce panel "clock" item. Unfortunately, it
> is broken:
>
> - If I right-click on the Xfce panel and choose "Panel
> Preferences...", the "Pane
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 9 Aug 2017 22:48:37 -0700
David Christensen wrote:
>On 08/09/17 21:47, Charlie Kravetz wrote:
>>
>> It almost sounds like the panel is too long for the monitor. The clock
>> is disappearing off the end of the panel.
On 08/09/17 21:47, Charlie Kravetz wrote:
It almost sounds like the panel is too long for the monitor. The clock
is disappearing off the end of the panel. Is the clock the last thing
in panel? Try moving it to the other of the panel, and see if it still
disappears.
Clock is neither the first
7-08-09 16:59:22 root@tinkywinky ~
># dpkg-query --show xfce4
>xfce4 4.12.3
>
>
>I would like to use the Xfce panel "clock" item. Unfortunately, it is
>broken:
>
>- If I right-click on the Xfce panel and choose "Panel Preferences...",
>the "
root@tinkywinky ~
# uname -a
Linux tinkywinky 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u3
(2017-08-06) x86_64 GNU/Linux
2017-08-09 16:59:22 root@tinkywinky ~
# dpkg-query --show xfce4
xfce4 4.12.3
I would like to use the Xfce panel "clock" item. Unfortunately, it is
broken:
-
Hello.
I use in preseed.cfg the following:
tasksel tasksel/first multiselect standard
tasksel tasksel/first seen false
d-i clock-setup/utc boolean false
d-i clock-setup/utc seen false
I set seen as false to view the value that was selected. Nor tasksel, nor clock-setup/utc does not set
On 06/14/2016 06:40 AM, Richard Barmann wrote:
> About once a week when I boot up I find the clock is exactly 4 hours slow. I
> am using Kubuntu 16.04. If I am asking the question in the wrong place please
> send me to the correct forum.
> Thank you.
Try changing /etc/adjtime to h
On Tuesday 14 June 2016 07:20:28 Jörg-Volker Peetz wrote:
> Richard Barmann wrote on 06/14/16 05:36:
> > About once a week when I boot up I find the clock is exactly 4 hours
> > slow. I am using Kubuntu 16.04. If I am asking the question in the wrong
> > place please send me
On 6/14/16, Jörg-Volker Peetz wrote:
> Richard Barmann wrote on 06/14/16 05:36:
>> About once a week when I boot up I find the clock is exactly 4 hours slow.
>> I am
>> using Kubuntu 16.04. If I am asking the question in the wrong place please
>> send
>> me t
Richard Barmann wrote on 06/14/16 05:36:
> About once a week when I boot up I find the clock is exactly 4 hours slow. I
> am
> using Kubuntu 16.04. If I am asking the question in the wrong place please
> send
> me to the correct forum.
> Thank you.
>
The four hours seem
Richard Barmann composed on 2016-06-13 23:36 (UTC-0400):
About once a week when I boot up I find the clock is exactly 4 hours
slow. I am using Kubuntu 16.04. If I am asking the question in the wrong
place please send me to the correct forum.
Kubuntu is not Debian, but is heavily Debian based
On Mon, Jun 13, 2016 at 11:36:59PM -0400, Richard Barmann wrote:
> About once a week when I boot up I find the clock is exactly 4 hours slow. I
> am using Kubuntu 16.04. If I am asking the question in the wrong place
> please send me to the correct forum.
> Thank you.
Kubuntu
About once a week when I boot up I find the clock is exactly 4 hours
slow. I am using Kubuntu 16.04. If I am asking the question in the wrong
place please send me to the correct forum.
Thank you.
On Mon, May 30, 2016 at 07:07:03AM +, Curt wrote:
> On 2016-05-29, Stephen Allen wrote:
> > On Fri, May 27, 2016 at 03:16:50PM +0200, Hársfalvi Gábor wrote:
> >> Hi!
> >>
> >> Is there any way to move the clock on the bar top on the screen? For
> &
On Friday 27 May 2016 14:24:31 Lisi Reisz wrote:
> On Friday 27 May 2016 14:16:50 Hársfalvi Gábor wrote:
> > Hi!
> >
> > Is there any way to move the clock on the bar top on the screen? For
> > example from center to left side.
>
> What desktop?? Or is it a wi
On 2016-05-29, Stephen Allen wrote:
> On Fri, May 27, 2016 at 03:16:50PM +0200, Hársfalvi Gábor wrote:
>> Hi!
>>
>> Is there any way to move the clock on the bar top on the screen? For example
>> from center to left side.
>>
>> Thanks.
>
> If you l
On Fri, May 27, 2016 at 03:16:50PM +0200, Hársfalvi Gábor wrote:
> Hi!
>
> Is there any way to move the clock on the bar top on the screen? For example
> from center to left side.
>
> Thanks.
If you look on extensions.gnome.org you might find an extension to do
this. I'm
Hello,
i installed Debian testing from the netinst iso onto a Lenovo W530 laptop.
When booting the machine when it is attached to its docking station with
closed display, i very often get the kernel message
ASPM: Could not configure common clock
and then the boot process hangs.
When i reboot
On Fri, 2016-05-27 at 15:16 +0200, Hársfalvi Gábor wrote:
> Hi!
>
> Is there any way to move the clock on the bar top on the screen? For
> example from center to left side.
You need to use extensions for that
https://extensions.gnome.org/extension/2/move-clock/
--
Cheers,
Sven Ar
On Friday 27 May 2016 14:24:31 Lisi Reisz wrote:
> In TDE 3.5.13.2 on Wheezy, and TDE 14.0.4 on Jessie, you click just to the
> left of the clock applet to bring up a small window which offers, among
> other things, to move the clock. You choose "move the clock" and move it
On Friday 27 May 2016 14:16:50 Hársfalvi Gábor wrote:
> Hi!
>
> Is there any way to move the clock on the bar top on the screen? For
> example from center to left side.
What desktop?? Or is it a window manager? I seem to remember that you are
running Gnome3 on Jessie, but you re
Hi!
Is there any way to move the clock on the bar top on the screen? For
example from center to left side.
Thanks.
> On 04.02.2016, at 14:04, Nigel Sollars wrote:
>
> There seems to be a good explanation here,
>
> https://lists.debian.org/debian-arm/2013/12/msg00038.html
>
>> On Wed, Feb 3, 2016 at 12:56 PM, Rick Thomas wrote:
>> Does anyone know what the error messages
>>
>> Does anybody know what is ca
;
> > [1.485042] imx-sdma 20ec000.sdma: firmware: failed to load
> imx/sdma/sdma-imx6q.bin (-2)
> > [ 1.544474] imx-gpc 20dc000.gpc: failed to get pu regulator: -517
> > [1.551844] imx-gpc 20dc000.gpc: failed to get pu regulator: -517
> > Loading, please wait...
> > [2.221380] imx-gpc 20dc000.gpc: failed to get pu regulator: -517
> > [2.257486] ERROR: could not get clock /usdhc1_pwrseq:ext_clock(0)
> >
>
>
--
“Science is a differential equation. Religion is a boundary condition.”
Alan Turing
] imx-gpc 20dc000.gpc: failed to get pu regulator: -517
> [1.551844] imx-gpc 20dc000.gpc: failed to get pu regulator: -517
> Loading, please wait...
> [2.221380] imx-gpc 20dc000.gpc: failed to get pu regulator: -517
> [2.257486] ERROR: could not get clock /usdhc1_pwrseq:ext_clock(0)
>
On 2015-07-03 15:38:02 +0200, Michael Biebl wrote:
> In short, your ntp client should ensure that the clock is synced to RTC
> (google for "ntp 11 min mode sync" if you want to know more). For that
> we enable timesyncd by default in systemd.
Thanks for the information, bu
On Friday 03 July 2015 14:38:02 Michael Biebl wrote:
> Am 03.07.2015 um 15:18 schrieb Arno Schuring:
> >> Date: Fri, 3 Jul 2015 15:07:34 +0200
> >> From: vinc...@vinc17.net
> >>
> >> When I run "hwclock --systohc" manually before the reboot, the cl
> Date: Fri, 3 Jul 2015 15:38:02 +0200
> From: bi...@debian.org
>
> Am 03.07.2015 um 15:18 schrieb Arno Schuring:
>>
>>> Date: Fri, 3 Jul 2015 15:07:34 +0200
>>> From: vinc...@vinc17.net
>>>
>>> When I run "hwclock --systohc" manual
Am 03.07.2015 um 15:18 schrieb Arno Schuring:
>
>> Date: Fri, 3 Jul 2015 15:07:34 +0200
>> From: vinc...@vinc17.net
>>
>> When I run "hwclock --systohc" manually before the reboot, the clock
>> is OK after reboot. So, this seems to be a systemd bug. I
On Friday 03 July 2015 14:18:50 Arno Schuring wrote:
> > Date: Fri, 3 Jul 2015 15:07:34 +0200
> > From: vinc...@vinc17.net
> >
> > When I run "hwclock --systohc" manually before the reboot, the clock
> > is OK after reboot. So, this seems to be a s
> Date: Fri, 3 Jul 2015 15:07:34 +0200
> From: vinc...@vinc17.net
>
> When I run "hwclock --systohc" manually before the reboot, the clock
> is OK after reboot. So, this seems to be a systemd bug. I've reported:
>
> https://bugs.debian.org/cgi-bin/bugreport
On 2015-07-01 02:24:14 +0200, Vincent Lefevre wrote:
> On 2015-06-30 18:15:18 -0400, Gary Dale wrote:
> > Is your cmos battery still providing power?
>
> The machine is new, so it should. The machine was also constantly on
> AC power.
>
> > Either that or your hardwa
On 2015-06-30 18:15:18 -0400, Gary Dale wrote:
> Is your cmos battery still providing power?
The machine is new, so it should. The machine was also constantly on
AC power.
> Either that or your hardware clock could be broken or very
> inaccurate.
If it loses 15 seconds just the time of
On 30/06/15 05:52 PM, Vincent Lefevre wrote:
I've noticed that with my new HP ZBook G2, the clock loses time after
a reboot. Below is the openntpd log without the "peer" messages ("ntp
engine ready" means that this is just after a reboot). What is the
cause? Whic
I've noticed that with my new HP ZBook G2, the clock loses time after
a reboot. Below is the openntpd log without the "peer" messages ("ntp
engine ready" means that this is just after a reboot). What is the
cause? Which part of the software is responsible to sync the R
Hi all,
Context: Wheezy x86_64 fresh install, plus all available updates,
plus systemd-sysv from wheezy-backports.
Is it possible to change the date format used by the GNOME Classic
Clock Applet? It seems nothing i do will get it change from the US
month-before-day format.
In GNOME
I have been fooling around with buici-clock on Debian Sid.
I was running it on the desktop at 100x100 with the appropriate
x and y offsets.
It was being called from the Fluxbox startup file.
I then modifed the file to enlarge the clock to 150x150 and
lowered the x and y offsets. What happens now
this message.
> One thing that I am aware of and no it can't be solved is that the
> clocks can't work correctly. The machines don't have good battery and
> the clocks are not working well, resulting in machines with wrong time
> settings and not all machines on the net
good battery and
the clocks are not working well, resulting in machines with wrong time
settings and not all machines on the network having the same clock
settings.
I have tried dpkg-reconfigure for nfs-kernel-server, nfs-common,
nautilus and tzdata in all machines with no luck.
Could it be the
Franco Martelli wrote:
> Bob Proulx ha scritto:
> > Franco Martelli wrote:
> >> I installed both ntpdate and rdate packages but automatic date
> >> and time update of KDE digital clock on the desktop doesn't
> >> work. Do I need package like kde
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 29/06/2013 20:24, Bob Proulx ha scritto:
> Franco Martelli wrote:
>> I installed both ntpdate and rdate packages but automatic date
>> and time update of KDE digital clock on the desktop doesn't
>> work. Do I need packag
1 - 100 of 933 matches
Mail list logo
