time-admin crashed with SIGSEGV in strcmp()

StacktraceTop:strcmp () at ../sysdeps/x86_64/strcmp.S:30
e_tz_map_get_location_by_name (
gst_time_tool_run_timezone_dialog (
IA__g_closure_invoke (closure=0x16434b0,
signal_emit_unlocked_R (node=0x162ca20,

the situation within the dialog: in the time-zone dialog the world map was mostly black with some light points, location of mouse pointer was recognized (status line updated accordinlgly), the list field was empty and just one line high, on <apply> the app crashed

I think the importance ought to be higher; you can't use some programs in the livecd without being able to set the time correctly, e.g. mythtv.

As I mentioned in the duplicate bug report (414664) I filed (in alpha4 karmic), a popup dialog appeared the first time indicating that it couldn't load the configuration because "you are not allowed to access the system configuration". It is presumably the lack of this access that leads both to the segv and to the messed up map and dialog elements. It probably should be a separate bug that this popup dialog only appears the first time you try to invoke the timezone dialog.

Ouch! Thanks for noticing this bug. Don't worry about the importance, Medium is already quite high and it won't prevent me from trying to fix it.

I've just committed a fix so that the map is shown again, it had indeed recently disappeared due to a wrong path to the image file. But the crash is not directly related to this, and I'm starting investigating it - should not be too hard given the bad GTK warnings that are shown. The popup may be another problem, we'll see. ;-)

OK, the crash was also fairly simple: the time zones list was not created, thus we were trying to access invalid zone names. I've added the list back, and that fixed the crash.

This is now committed to our development branch, but I guess you'll have to wait for 2.27.92 to be released, which will happen before September 7th. Please then confirm, and thanks for your attention!

Oh, and please report the "you are not allowed to access the system configuration" problem separately, including details. You can run 'sudo killall polkitd && sudo /usr/libexec/polkitd', then run time-admin, and attach the logs. Thanks!

I stumbled across this bug report thanks to the automated bug generation when my time-admin crashed with the same symptoms noted here. I was wondering if the problem with timezone setting is contributing the this bug where an fsck is being forced due to an inconsistency in the superblocks (superblock identified an hour in the future)... http://ubuntuforums.org/showthread.php?t=1252690

My apologies... the more relevant bug is this one: http://ubuntuforums.org/showthread.php?t=1252108&page=2

Well, if your clock shows the right time, then no chance the current bug can raise fsck issues. I don't think the time can become incorrect because of the crash, since the system settings should not be modified.

The fsck issue is likely bug 423427 which is now fixed.

This bug is still happening as of a fresh install of Karmic Alpha 6

well, my clock does NOT show the right time. it shows 20:27 whereas it's 12:27 where i am (or 10:27 utc).

To configure correctly your clock you can use :
sudo dpkg-reconfigure tzdata

TeutonJon78: yeah, nobody said the contrary. This is because version 2.27.92 has not been uploaded to Karmic yet.

Tomasz: please don't report completely different problems on an existing report. If you think you experience a bug, please report it separately. Else, you can get help in the forums.

I received an exception when I clicked on the clock in an Xubuntu 9.10 Alpha 6 instance, running in Virtualbox OSE from a Debian Sid based laptop system. Not positive that it is the same defect, but problems persist in this interface.

Since it says "Fix released", I just wanted to say that this problem still persists for me with most recent karmic and all updates on Sept. 22.

Oh, sorry missed #16. My gnome-system-tools is still 2.27.3.

Yes, got the update today, it works now with 2.28.0.