unable to define time zone
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-system-tools (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-system-tools
Hi.
The time-admin keeps crashing and also I am unable to define time zone.
I believe that this is causing also problems with my disks. During boot the system says that the superblock has been last time modified in the future. It is always 2 hours in the future. The Czech republic is GMT +2 so it is a time zone related problem. If I fix the disk with fsck and reboot system, the problem is inmediately back. I had to disable integrity checks during boot otherwise I would not be able to even boot. It would boot to read only state.
Please let me know if anything else is needed from me.
With regards,
Petr Hojzak.
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 11 09:29:30 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/time-admin
NonfreeKernelMo
Package: gnome-system-tools 2.27.3-0ubuntu1
ProcCmdline: time-admin
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x7fa5b45dcd92 <strcmp+2>: cmp (%rsi),%al
PC (0x7fa5b45dcd92) ok
source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-system-tools
StacktraceTop:
strcmp () from /lib/libc.so.6
?? ()
?? ()
g_closure_invoke ()
?? () from /usr/lib/
Title: time-admin crashed with SIGSEGV in strcmp()
Uname: Linux 2.6.31-10-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #406211, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.