kickers clock applet is screwed

confirmed via irc session on kubuntu-devel (2006-02-05) from me and hobbsee

Confirming this bug report

For some reason, I had to recreate /etc/timezone as well, to get the local time in the console to work. I have not changed any time related settings before this upgrade.

I would rather blame libc6 upload. tzconfig hangs forever when selecting a city and tzselect gives the following error:

/usr/bin/tzselect: line 53: /usr/share/zoneinfo/iso3166.tab: No such file or directory
/usr/bin/tzselect: time zone files are not set up correctly

i updated my dapper installation a few minutes ago.

   * Drop timezones from main libc package.
     - debian/debhelper.in/libc.install: Drop /usr/share/zoneinfo
       drop usr/bin/locale
     - debian/debhelper.in/libc.manpages: Drop locale.1 and localedef.1
     - debian/debhelper/in/libc.dirs: Add /usr/share/zoneinfo
     - debian/control.in/libc: Recommends: locales

To be precisly:

The effect we can see in KDEs kicker clock applet, doesn't show up in gnomes clock.
Strange thing is even more, on the console, the `date` output is correct.

Related issue: http://paste.ubuntu-nl.org/i8051

Timezone data is gooone.

How did you get a system without locales or awk? All Ubuntu systems should have ubuntu-minimal installed, which installs locales and mawk.

Tks,
Jeff Bailey

Jeff,

locales and timezone data is installed on my system. As well on Hobbsees. This issue happened after last glibc upload and upgrade of the system.
I checked kickers clock applet sources, and no evidence of system/exec calls to awk or grep.
Strange, that it looks for awk in /bin, whereas the default location is /usr/bin/awk or /usr/bin/mawk.

same for me, date works as aspected, but clock in kicker show only UTC time.

Stephen,

Can you check to make sure you have locales 2.3.10 installed? Before I hunt this much further, I'd like to make sure we're all on the same version.

Tks,
Jeff Bailey

I've locales 2.3.9. I'm on a PPC running Dapper Drake.
My system is uptodate

It looks like 2.3.10 just built this morning and isn't quite in the archive yet. I'll check back in a bit and try upgrading again.

When I looked at /usr/share/zoneinfo, I noticed that almost all files under this directory contains anything but correct timezone info. Most of them contain only some strange binary data.

Hi Jeff,

On Monday 06 February 2006 11:56, Jeff Bailey wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/30546
>
> Comment:
> Stephen,
>
> Can you check to make sure you have locales 2.3.10 installed? Before I
> hunt this much further, I'd like to make sure we're all on the same
> version.

no it's 2.3.9. I made an dist-upgrade now, and a new locales package is being
downloaded. Looks like there was a lack of sync between the packages. I'll
check directly after the package is installed and follow up here.

Regards,

\sh

just installed locales 2.3.10 and did "dcop kicker kicker restart" and voila, correct timezone and everything, seems like fixed then?

Fixed by upgrading to locales 2.3.10 :)

Also fixed here by upgrading to localse 2.3.10

sorry for being late, but after locales 2.3.10 was installed, everything is fine.