I am using "~x86" for my system and did an update to the newest glibc (2.3.4.20050125) using "emerge -u glibc" only to find that my previously compiled applications became broken. Several KDE applications were in a rather bad state (screenshot of konqueror to be attached), xmms refused to start, and other applications, eg: Open Office, Star Office, KMail, konsole, plus other applications that I can't remember were also broken. Either they had problems similar to what konqueror had, or they refused to start, as xmms did. In the case of xmms, I did try rebuilding it (emerge --newuse xmms), but without any success - the error below still came out. The error that I got on the command line with xmms was: # xmms *** glibc detected *** free(): invalid pointer: 0xb6f5f84e *** Aborted As I run this machine as a productive system at work, I could not test long to find more information. I was able to resolve the problems by masking out glibc 2.3.4.20050125 and using instead the latest stable, which at the time of writing this report is 2.3.4.20040808-r1. After returning to this version, everything behaves normally again. I hope this report is useful. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 52392 [details] snapshot of konqueror window when using glibc 2.3.4.20050125 This is the snapshot of konqueror after starting it with the latest glibc (2.3.4.20050125). The menus were initially ok, then after running the mouse over them, they became corrupted. The large empty space came by itself and grew with each new tab, new web page, or when things were done in the window. The corrupted buttons were like that as soon as the page was loaded. Also, the longer the window was open, the more corrupted the tab names became, and their length grew constantly as they were being filled with garbage characters, the start of which you can see in the second tab "verkehrsverbund".
Can you pleasse update to 2.3.4.20041102 and let me know if that version gives you problems? Also, please resync and test 2.3.4.20050125-r1. I just committed an update to that version, so make sure the ChangeLog has a '05 March' entry at the top.
Sorry for taking so long to get back to this. I did an update to 2.3.4.20041102 and an initial test shows that it seems to be OK. I will run with this version for the next few hours to see if anything happens, and it it remains OK, I will try the 2.3.4.20050125-r1. Ian
I ran with 2.3.4.20041102 until this morning and it seemed mostly fine. I did notice that kmail was no longer able to do searches on the ldap server, the reason is still unknown to me. I've completed an update to 2.3.4.20050125-r1 and first impressions are that it's ok too. Kmail is still unable to do ldap searches, however that is another problem that I will have to look into when I get time. I will run with this for a few days and report back.
Not all is good - I now have occasional stability problems with some programs. For example, k3b now likes to crash when I try to write a cd iso image. I ran it in gdb and got the following: $ gdb k3b GNU gdb 6.2.1 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"...(no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/bin/k3b (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 16384 (LWP 23208)] k3b: WARNING: KGenericFactory: instance requested but no instance name or about data passed to the constructor! Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 23208)] 0x402f67a2 in K3bWriterSelectionWidget::slotRefreshWriterSpeeds () from /usr/lib/libk3bproject.so.2 (gdb) bt full #0 0x402f67a2 in K3bWriterSelectionWidget::slotRefreshWriterSpeeds () from /usr/lib/libk3bproject.so.2 No symbol table info available. #1 0x402f62d2 in K3bWriterSelectionWidget::init () from /usr/lib/libk3bproject.so.2 No symbol table info available. #2 0x402f5efb in K3bWriterSelectionWidget::K3bWriterSelectionWidget () from /usr/lib/libk3bproject.so.2 No symbol table info available. #3 0x0814eb2c in QValueListPrivate<KIO::UDSAtom>::insert () No symbol table info available. #4 0x0814d8e0 in QValueListPrivate<KIO::UDSAtom>::insert () No symbol table info available. #5 0x0809ee8c in QWidget::metaObject () No symbol table info available. #6 0x40ec1bcf in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #7 0x40ec1a14 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #8 0x40848d5b in KAction::activated () from /usr/kde/3.3/lib/libkdeui.so.4 No symbol table info available. #9 0x4084872f in KAction::slotActivated () from /usr/kde/3.3/lib/libkdeui.so.4 No symbol table info available. #10 0x40848f4f in KAction::qt_invoke () from /usr/kde/3.3/lib/libkdeui.so.4 No symbol table info available. #11 0x40ec1bcf in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #12 0x411f5f58 in QSignal::signal () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #13 0x40edbdaf in QSignal::activate () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #14 0x40fc6d34 in QPopupMenu::mouseReleaseEvent () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #15 0x40ef790a in QWidget::event () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #16 0x40e6642c in QApplication::internalNotify () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #17 0x40e658e9 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #18 0x40a916d2 in KApplication::notify () from /usr/kde/3.3/lib/libkdecore.so.4 No symbol table info available. #19 0x40df46d9 in QETWidget::translateMouseEvent () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #20 0x40df2628 in QApplication::x11ProcessEvent () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #21 0x40e0d13b in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #22 0x40e78718 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #23 0x40e785c8 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #24 0x40e66661 in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3 No symbol table info available. #25 0x0809fef6 in QPtrList<K3bPluginFactory>::deleteItem () No symbol table info available. ---Type <return> to continue, or q <return> to quit--- #26 0x4147b440 in __libc_start_main () from /lib/libc.so.6 No symbol table info available. #27 0x0807d861 in ?? () No symbol table info available. (gdb) Do I need to rebuild everything on my system to get this stable??? Ian
Do I need to rebuild... YES :-( I did an emerge --newuse k3b which resulted in a total of 4 package updates, including k3b, and then k3b was ok. It seems that with the new glibc, some packages have to be rebuilt in order for them to be stable. I'm now starting a rebuild/update of most of my system with an emerge -u world which is updating some 114 packages. I hope this solves the problems... Ian
Now for my final (hopefully) entry to this bug. After testing for a short time with the 2.3.4.20050125 glibc, the artifacts that I showed with the konqueror snapshot showed up again. My fault - this time I built without going down into a text terminal, therefore the delay with the artifacts showing up. Logging out did not improve the problem and this time the artifacts were also visible on the login screen, where I use kdm as the login manager. The kde session was a disaster with the artifacts everywhere and icons mutating, and applications crashing randomly. So, in the end I was able to solve this problem - I rebooted my system and all artifacts from all applications that I have seen seem to have vanished. This was not the case with previous attempts (as in a reboot produced something positive). The applications appear to be stable (if you say that a 1 hour test is long enough), with the exception of xmms - it still falls over with the same error. I've also built kde 3.4.0, which I'm now using, and it seems to be ok. KDE 3.3.2 is also apparently ok now, although I only very briefly logged in, not even 5 minutes, to see how it was. Even ldap searches in kmail work again. The gentoo XMMS refuses point blank to start with glibc 2.3.4.20050125 the with the same error as previously mentioned. The only solution to this was to take the original xmms source from the xmms site. Maybe this needs its own bug report??? My feeling now is that this bug could be closed. Users who update to this version of glibc (2.3.4.20050125) must reboot their systems, otherwise there will be problems. It is also clear the some packages will have to be rebuilt in order for them to be stable, as was the case with k3b. I will watch carefully what happens and if there is anything that appears glibc related, I will post here again (hopefully not). Ian
not a bug in glibc
