timedatectl crashes on rpi

[Triode]

With timezone set to UTC it looks like timedatectl crashes on arm6l. It does not do this on arm7 so I wonder if there is something specific about how it is built? It does not crash if the timezone is set to something other than UTC. Does anyone else see this?

$this->bbcode_second_pass_code('', '
[root@soa-rpi ~]# timedatectl
Local time: Sun 2014-12-28 19:35:19 UTC
Universal time: Sun 2014-12-28 19:35:19 UTC
RTC time: n/a
Time zone: UTC (UTC, +0000)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
*** Error in `timedatectl': free(): invalid next size (fast): 0xb749c8d8 ***
======= Backtrace: =========
/usr/lib/libc.so.6(+0x68ee4)[0xb6d3cee4]
/usr/lib/libc.so.6(+0x6ebd8)[0xb6d42bd8]
/usr/lib/libc.so.6(+0x6f59c)[0xb6d4359c]
======= Memory map: ========
b6cd4000-b6dff000 r-xp 00000000 b3:02 17720 /usr/lib/libc-2.20.so
b6dff000-b6e06000 ---p 0012b000 b3:02 17720 /usr/lib/libc-2.20.so
b6e06000-b6e08000 r--p 0012a000 b3:02 17720 /usr/lib/libc-2.20.so
b6e08000-b6e09000 rw-p 0012c000 b3:02 17720 /usr/lib/libc-2.20.so
b6e09000-b6e0c000 rw-p 00000000 00:00 0
b6e0c000-b6e21000 r-xp 00000000 b3:02 17573 /usr/lib/libpthread-2.20.so
b6e21000-b6e28000 ---p 00015000 b3:02 17573 /usr/lib/libpthread-2.20.so
b6e28000-b6e29000 r--p 00014000 b3:02 17573 /usr/lib/libpthread-2.20.so
b6e29000-b6e2a000 rw-p 00015000 b3:02 17573 /usr/lib/libpthread-2.20.so
b6e2a000-b6e2c000 rw-p 00000000 00:00 0
b6e2c000-b6e49000 r-xp 00000000 b3:02 17729 /usr/lib/libgcc_s.so.1
b6e49000-b6e50000 ---p 0001d000 b3:02 17729 /usr/lib/libgcc_s.so.1
b6e50000-b6e51000 rw-p 0001c000 b3:02 17729 /usr/lib/libgcc_s.so.1
b6e51000-b6e57000 r-xp 00000000 b3:02 17600 /usr/lib/librt-2.20.so
b6e57000-b6e5e000 ---p 00006000 b3:02 17600 /usr/lib/librt-2.20.so
b6e5e000-b6e5f000 r--p 00005000 b3:02 17600 /usr/lib/librt-2.20.so
b6e5f000-b6e60000 rw-p 00006000 b3:02 17600 /usr/lib/librt-2.20.so
b6e6e000-b6e8e000 r-xp 00000000 b3:02 17694 /usr/lib/ld-2.20.so
b6e90000-b6e94000 rw-p 00000000 00:00 0
b6e94000-b6e95000 r-xp 00000000 00:00 0 [sigpage]
b6e95000-b6e96000 r--p 0001f000 b3:02 17694 /usr/lib/ld-2.20.so
b6e96000-b6e97000 rw-p 00020000 b3:02 17694 /usr/lib/ld-2.20.so
b6e97000-b6f01000 r-xp 00000000 b3:02 18589 /usr/bin/timedatectl
b6f02000-b6f04000 r--p 0006a000 b3:02 18589 /usr/bin/timedatectl
b6f04000-b6f05000 rw-p 0006c000 b3:02 18589 /usr/bin/timedatectl
b749b000-b74bc000 rw-p 00000000 00:00 0 [heap]
beeba000-beedb000 rw-p 00000000 00:00 0 [stack]
ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]
Aborted (core dumped)
[root@soa-rpi ~]# timedatectl set-timezone GB
[root@soa-rpi ~]# timedatectl
Local time: Sun 2014-12-28 19:35:29 GMT
Universal time: Sun 2014-12-28 19:35:29 UTC
RTC time: n/a
Time zone: GB (GMT, +0000)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: no
Last DST change: DST ended at
Sun 2014-10-26 01:59:59 BST
Sun 2014-10-26 01:00:00 GMT
Next DST change: DST begins (the clock jumps one hour forward) at
Sun 2015-03-29 00:59:59 GMT
Sun 2015-03-29 02:00:00 BST
')

[zman97211]

I get the same behavior with my RPi. This is a pretty much "stock" installation of Arch a few days ago. I got tired of mentally adjusting the time and looked up how to set the timezone. First time I ran timedatectl, this was the output:

$this->bbcode_second_pass_code('', '[steve@pi ~]$ timedatectl
Local time: Fri 2015-02-27 02:47:01 UTC
Universal time: Fri 2015-02-27 02:47:01 UTC
RTC time: n/a
Time zone: UTC (UTC, +0000)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
*** Error in `timedatectl': free(): invalid next size (fast): 0xb83f08d8 ***
======= Backtrace: =========
/usr/lib/libc.so.6(+0x68eb4)[0xb6db4eb4]
/usr/lib/libc.so.6(+0x6eba8)[0xb6dbaba8]
/usr/lib/libc.so.6(+0x6f56c)[0xb6dbb56c]
======= Memory map: ========
b6d4c000-b6e77000 r-xp 00000000 b3:02 279927 /usr/lib/libc-2.20.so
b6e77000-b6e86000 ---p 0012b000 b3:02 279927 /usr/lib/libc-2.20.so
b6e86000-b6e88000 r--p 0012a000 b3:02 279927 /usr/lib/libc-2.20.so
b6e88000-b6e89000 rw-p 0012c000 b3:02 279927 /usr/lib/libc-2.20.so
b6e89000-b6e8c000 rw-p 00000000 00:00 0
b6e8c000-b6ea1000 r-xp 00000000 b3:02 279778 /usr/lib/libpthread-2.20.so
b6ea1000-b6eb0000 ---p 00015000 b3:02 279778 /usr/lib/libpthread-2.20.so
b6eb0000-b6eb1000 r--p 00014000 b3:02 279778 /usr/lib/libpthread-2.20.so
b6eb1000-b6eb2000 rw-p 00015000 b3:02 279778 /usr/lib/libpthread-2.20.so
b6eb2000-b6eb4000 rw-p 00000000 00:00 0
b6eb4000-b6ed1000 r-xp 00000000 b3:02 279936 /usr/lib/libgcc_s.so.1
b6ed1000-b6ee0000 ---p 0001d000 b3:02 279936 /usr/lib/libgcc_s.so.1
b6ee0000-b6ee1000 rw-p 0001c000 b3:02 279936 /usr/lib/libgcc_s.so.1
b6ee1000-b6ee7000 r-xp 00000000 b3:02 279804 /usr/lib/librt-2.20.so
b6ee7000-b6ef6000 ---p 00006000 b3:02 279804 /usr/lib/librt-2.20.so
b6ef6000-b6ef7000 r--p 00005000 b3:02 279804 /usr/lib/librt-2.20.so
b6ef7000-b6ef8000 rw-p 00006000 b3:02 279804 /usr/lib/librt-2.20.so
b6ef8000-b6f18000 r-xp 00000000 b3:02 279899 /usr/lib/ld-2.20.so
b6f1e000-b6f20000 rw-p 00000000 00:00 0
b6f25000-b6f27000 rw-p 00000000 00:00 0
b6f27000-b6f28000 r--p 0001f000 b3:02 279899 /usr/lib/ld-2.20.so
b6f28000-b6f29000 rw-p 00020000 b3:02 279899 /usr/lib/ld-2.20.so
b6f29000-b6f93000 r-xp 00000000 b3:02 277855 /usr/bin/timedatectl
b6f94000-b6f96000 r--p 0006a000 b3:02 277855 /usr/bin/timedatectl
b6f96000-b6f97000 rw-p 0006c000 b3:02 277855 /usr/bin/timedatectl
b83ef000-b8410000 rw-p 00000000 00:00 0 [heap]
bee68000-bee89000 rw-p 00000000 00:00 0 [stack]
beff3000-beff4000 r-xp 00000000 00:00 0 [sigpage]
ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]
Aborted (core dumped)')

[pepedog]

What happens if you set time zone first, and repeat timedatectl?
example-
$this->bbcode_second_pass_code('', 'timedatectl set-timezone Europe/London')
Not just a rpi thing btw

[blueA]

$this->bbcode_second_pass_quote('pepedog', 'W')hat happens if you set time zone first, and repeat timedatectl?