Version: (using KDE KDE 3.4.92) Installed from: Ubuntu Packages OS: Linux Steps 1. Fresh Ubuntu installation, version 5.04 from CD, +all available updates over web (System->Software Updates). 2. Installed Kubuntu. GL Screen savers didn't function on KDE. Worked on GNOME. Sounds were ok. 3. Configured Evolution, but I think not much anything else. 4. Update Ubuntu to v.5.10 over web, after replacing all words 'hoary' with 'breezy' in file sources.list. I also added a line 'deb http://www.ftp.funet.fi/pub/mirrors/ftp.kde.org/pub/kde/unstable/3.5-beta2/kubuntu/ breezy main' into the sources.list to get the KDE 3.5 beta. 5. Updated the KDE (System->Software Updates). 6. At re-start, a crash of artsd at startup (no stack dump). 7. Installed packages 'xorg-driver-fglrx', 'xorg-driver-fglrx-dev' and 'fglrx-control' with "Software Updates", as an attempt to get some life for my screen savers (Yes I know, this was not supposed to be the cure for the crash, but I did it anyway to help my ATI...) 8. At KDE startup, a crash of artsd at startup, with stackdump: -------------------------------------------------------------------------- Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (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 -1219479872 (LWP 8876)] (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) [KCrash handler] #14 0xb778933e in __gnu_cxx::__pool<true>::_M_reclaim_block () from /usr/lib/libstdc++.so.6 #15 0x080606b3 in ?? () #16 0x08074cc0 in Arts::ByteSoundProducerV2_base::_IID () #17 0x0821ebf8 in ?? () #18 0x00000008 in ?? () #19 0xb7719900 in __malloc_initialize_hook () from /lib/tls/i686/cmov/libc.so.6 #20 0x08177d5c in ?? () #21 0x00000000 in ?? () #22 0x08177d1c in ?? () #23 0x08177d04 in ?? () #24 0x08177cfc in ?? () #25 0x08177cf4 in ?? () #26 0x08177cec in ?? () #27 0x081caac8 in ?? () #28 0x081c9f20 in ?? () #29 0x080b97dc in ?? () #30 0xbfb26570 in ?? () #31 0x08119bc4 in ?? () #32 0x08119c3c in ?? () #33 0x0821b71c in ?? () #34 0x0821b71c in ?? () #35 0x081ca820 in ?? () #36 0x0821d59c in ?? () #37 0x08071d38 in ?? () #38 0x00000133 in ?? () #39 0x08177ce8 in ?? () #40 0x0806af04 in typeinfo name for Arts::TimeNotify () #41 0x08177ce8 in ?? () #42 0xbfb26588 in ?? () #43 0x08068018 in ?? () #44 0x08177ce8 in ?? () #45 0x0806af08 in typeinfo name for Arts::TimeNotify () #46 0x08177d8c in ?? () #47 0x08177d8c in ?? () #48 0x0806b03c in typeinfo name for Arts::TimeNotify () #49 0x08177d38 in ?? () #50 0xbfb265c8 in ?? () #51 0x08060ff6 in ?? () #52 0x08177ce8 in ?? () #53 0x0806af04 in typeinfo name for Arts::TimeNotify () #54 0x000000a8 in ?? () #55 0xb7825cd0 in ?? () from /usr/lib/libstdc++.so.6 #56 0x000000a8 in ?? () #57 0x0810b360 in ?? () #58 0xbfb265c8 in ?? () #59 0xb78014c5 in operator new () from /usr/lib/libstdc++.so.6 -------------------------------------------------------------------------- I found a promising bug report (Nr 109049), but there was no stack dump available, and the report it self seemed a bit old to me, so I decided to create a whole new report.
export GLIBCXX_FORCE_NEW=1 as a workaround *** This bug has been marked as a duplicate of 111115 ***