I upgraded to timezone-data-2006b recently. After upgrading (went smooth, no errors) every kde-app dealing with time would abort with SIGABRT and the following error: kcontrol: tzfile.c:344: __tzfile_read: Assertion `num_types == 1' failed. I obtained the following backtrace from KCrash: [...] [Thread debugging using libthread_db enabled] [New Thread -1237010768 (LWP 15037)] [KCrash handler] #6 0xffffe410 in __kernel_vsyscall () #7 0xb64773e0 in raise () from /lib/libc.so.6 #8 0xb6478b40 in abort () from /lib/libc.so.6 #9 0xb64708e0 in __assert_fail () from /lib/libc.so.6 #10 0xb64cd8f1 in tzset () from /lib/libc.so.6 #11 0xb64cbb1c in adjtime () from /lib/libc.so.6 #12 0xb64cc76e in tzset () from /lib/libc.so.6 #13 0xb721a885 in KTimezone::offset () from /usr/kde/3.5/lib/libkdecore.so.4 #14 0xb7276921 in KTimezones::local () from /usr/kde/3.5/lib/libkdecore.so.4 #15 0xb62d5079 in Tzone::currentZone () from /usr/kde/3.5/lib/kde3/kcm_clock.so #16 0xb62d51b8 in Tzone::load () from /usr/kde/3.5/lib/kde3/kcm_clock.so #17 0xb62d533c in Tzone::Tzone () from /usr/kde/3.5/lib/kde3/kcm_clock.so #18 0xb62d8afa in KclockModule::KclockModule () from /usr/kde/3.5/lib/kde3/kcm_clock.so #19 0xb62d9dc2 in KGenericFactory<KclockModule, QWidget>::createObject () from /usr/kde/3.5/lib/kde3/kcm_clock.so #20 0xb71e1041 in KLibFactory::create () from /usr/kde/3.5/lib/libkdecore.so.4 #21 0xb79afa12 in KCModuleLoader::load () from /usr/kde/3.5/lib/libkutils.so.1 #22 0xb79b01e9 in KCModuleLoader::loadModule () from /usr/kde/3.5/lib/libkutils.so.1 [...] I do not know if this problem is kde-specific, but after downgrading to timezone-data-2006a the problems vanished. sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1-r1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon -O2 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/share/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-march=athlon -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig candy ccache distlocks sandbox sfperms strict userpriv usersandbox" GENTOO_MIRRORS="http://mirror.switch.ch/mirror/gentoo/ http://ftp.romnet.org/gentoo/ http://pandemonium.tiscali.de/pub/gentoo/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo http://ftp.snt.utwente.nl/pub/os/linux/gentoo http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" LANG="en_US.ISO-8859-1" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 ipv6 kdeenablefinal nptl opengl pic unicode zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux userland_GNU video_cards_ati" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LC_ALL, LDFLAGS, LINGUAS
what does `ls -l /etc/localtime` show ?
mabi@terra ~ $ ls -l /etc/localtime -rw-r--r-- 1 root root 837 2006-01-01 13:27 /etc/localtime However copying over a much larger then before /usr/share/zoneinfo/Europe/Berlin solved the problem. Thanks for the pointer.
Same bug happens for me, kde panel crashed on kde startup or when started manually. Downgrading to 2005a reverts to normal behavior. Will try a new localtime with 2005b. Current link is this: localhost tdr # readlink /etc/localtime ../usr/share/zoneinfo/EST5EDT
Changing link from ESTEDT to America/New_York works.
can you guys find some non-kde app that crashes ? if not, can you find the "simplest" kde app that exhibits this problem ?
The kicker panel itself loads if i link localtime to EST5EDT and have the clock removed from the panel, and khexclock works if added, but when I add the regular clock applet back, it immediately crashes the entire panel. Here is a backtrace from a crash: (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1233733968 (LWP 28996)] [KCrash handler] #6 0xffffe410 in __kernel_vsyscall () #7 0xb6797671 in raise () from /lib/libc.so.6 #8 0xb6798e4b in abort () from /lib/libc.so.6 #9 0xb6790ba5 in __assert_fail () from /lib/libc.so.6 #10 0xb67ef764 in tzset () from /lib/libc.so.6 #11 0xb67ed9e5 in adjtime () from /lib/libc.so.6 #12 0xb67ee5be in tzset () from /lib/libc.so.6 #13 0xb76501a5 in KTimezone::offset () from /usr/kde/3.5/lib/libkdecore.so.4 #14 0xb7651083 in KTimezones::local () from /usr/kde/3.5/lib/libkdecore.so.4 #15 0xb65e03c0 in Zone::calc_TZ_offset () from /usr/kde/3.5/lib/kde3/clock_panelapplet.so #16 0xb65dd60b in ClockApplet::reconfigure () from /usr/kde/3.5/lib/kde3/clock_panelapplet.so #17 0xb65de52e in ClockApplet::ClockApplet () from /usr/kde/3.5/lib/kde3/clock_panelapplet.so #18 0xb65de72b in init () from /usr/kde/3.5/lib/kde3/clock_panelapplet.so #19 0xb7f18ed8 in PluginManager::loadApplet () from /usr/kde/3.5/lib/libkdeinit_kicker.so #20 0xb7f0a7fe in AppletContainer::AppletContainer () from /usr/kde/3.5/lib/libkdeinit_kicker.so #21 0xb7f1a4d5 in PluginManager::createAppletContainer () from /usr/kde/3.5/lib/libkdeinit_kicker.so #22 0xb7efb8e4 in ContainerArea::addApplet () from /usr/kde/3.5/lib/libkdeinit_kicker.so #23 0xb7f381fb in AddAppletDialog::addApplet () from /usr/kde/3.5/lib/libkdeinit_kicker.so #24 0xb7f383d7 in AddAppletDialog::addCurrentApplet () from /usr/kde/3.5/lib/libkdeinit_kicker.so #25 0xb7f3b297 in AddAppletDialog::qt_invoke () from /usr/kde/3.5/lib/libkdeinit_kicker.so #26 0xb6f12689 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3 #27 0xb6f12b30 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3 #28 0xb725922c in QButton::clicked () from /usr/qt/3/lib/libqt-mt.so.3 #29 0xb6fa5de6 in QButton::mouseReleaseEvent () from /usr/qt/3/lib/libqt-mt.so.3 #30 0xb6f4c2b8 in QWidget::event () from /usr/qt/3/lib/libqt-mt.so.3 #31 0xb6eb3861 in QApplication::internalNotify () from /usr/qt/3/lib/libqt-mt.so.3 #32 0xb6eb489c in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3 #33 0xb7514662 in KApplication::notify () from /usr/kde/3.5/lib/libkdecore.so.4 #34 0xb6e4fbc8 in QETWidget::translateMouseEvent () from /usr/qt/3/lib/libqt-mt.so.3 #35 0xb6e4f136 in QApplication::x11ProcessEvent () from /usr/qt/3/lib/libqt-mt.so.3 #36 0xb6e6279a in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3 #37 0xb6eca549 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3 #38 0xb6eca446 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3 #39 0xb6eb31af in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3 #40 0xb7ef4816 in kdemain () from /usr/kde/3.5/lib/libkdeinit_kicker.so #41 0xb6783f11 in __libc_start_main () from /lib/libc.so.6 #42 0x080486a1 in ?? ()
I found no other app that crashed, other than the kde clock applet. Could it be becuase kde timezone settings are set the America/New_York way and don't offer EST5EDT or similar format as an option? Is so, wouldn't this have caused a problem before?
Had the same problem with kicker not loading with EST5EDT, changed to US/Michigan and all worked fine.
Just want to add to my comment above that I didn't have any issues when I first upgraded to sys-libs/timezone-data-2006b, it wasn't until a system rebuild (I had just switched to gcc-4.1.0) that the problem was triggered.
(In reply to comment #9) > Just want to add to my comment above that I didn't have any issues when I first > upgraded to sys-libs/timezone-data-2006b, it wasn't until a system rebuild (I > had just switched to gcc-4.1.0) that the problem was triggered. > Ditto for me.
Well, kde-base/kicker-3.5.1 breaks w/ timezone-data-2006b & CST6CDT for me, but 2006a & CST6CDT is fine. Any idea what changed?
(In reply to comment #10) > (In reply to comment #9) > > Just want to add to my comment above that I didn't have any issues when I first > > upgraded to sys-libs/timezone-data-2006b, it wasn't until a system rebuild (I > > had just switched to gcc-4.1.0) that the problem was triggered. > > > > Ditto for me. > In trying to build my gcc-4.1 toolchain, I get the error shown below with any combination of LDFLAGS even at a bare minimum. My CFLAGS="-march=pentium4 -O2 -fomit-frame-pointer -pipe". !!! ERROR: sys-libs/timezonedata-data-2006b failed. Call stack: ebuild.sh, line 1565: Called dyn_compile ebuild.sh, line 974: Called src_compile Thanks, travlr
clearly unrelated to this bug report
david@MightyMax ~/Music/Paid/Cascada $ kicker & [1] 12183 david@MightyMax ~/Music/Paid/Cascada $ kicker: tzfile.c:344: __tzfile_read: Assertion `num_types == 1' failed. kicker: crashHandler called KCrash: Application 'kicker' crashing... kicker: tzfile.c:344: __tzfile_read: Assertion `num_types == 1' failed. ERROR: Communication problem with kicker, it probably crashed. this comes from glibc-2.4/time/tzfile.c in function __tzfile_read(). 340 if (__tzname[0] == NULL) 341 { 342 /* This should only happen if there are no transition rules. 343 In this case there should be only one single type. */ 344 assert (num_types == 1); 345 __tzname[0] = __tzstring (zone_names); 346 }
*** Bug 129884 has been marked as a duplicate of this bug. ***
/etc/conf.d/clock in new baselayouts record the TIMEZONE and the timezone-data package keys off of this to update /etc/localtime accordingly
