Bug 391840 - System time jumps 2 hours ahead at every boot
Summary: System time jumps 2 hours ahead at every boot
Status: RESOLVED DUPLICATE of bug 384254
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Beta 3
Hardware: Other Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Dr. Werner Fink
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-18 12:35 UTC by Stephan Binner
Modified: 2008-05-19 10:27 UTC (History)
1 user (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Binner 2008-05-18 12:35:43 UTC
Did an upgrade of a 10.3 installation to 11.0 Beta 3 (bug 391785 has the log files) and now at every boot the system time jumps ahead two hours despite YaST being set to hardware clock==localtime.

# chkconfig boot.setclock
boot.setclock  off

Coolo spotted in above log files:

2008-05-17 12:59:11 aaa_base-11.0-67.i586.rpm installed ok
Additional rpm output:
warning: /etc/mime.types saved as /etc/mime.types.rpmsave
insserv: script boot.setclock: service boot.clock already provided!
Comment 2 Hans-Peter Holler 2008-05-18 16:56:59 UTC
stbinner: SuSE/Novell employees should be able to search before filing a new bug.
werner: is it impossible to resolve this?
all: beside of this: great work.

*** This bug has been marked as a duplicate of bug 384254 ***
Comment 3 Stephan Kulow 2008-05-18 19:15:22 UTC
this is not a duplicate. 384254 is about zypper dup / rpm updates - this is a regular update
Comment 4 Dr. Werner Fink 2008-05-19 10:27:09 UTC
It is a side effect of both bug #386354 *and* bug #384254 ... first
bug leads to an error cause insserv to exit on this error.

To repair the system install the newset insserv and run

        insserv boot.setclock boot.getclock

as this is required due to the errors described in bug #384254 which
has caused insserv to fail.

*** This bug has been marked as a duplicate of bug 384254 ***