Version: (using KDE KDE 3.4.92) Installed from: Ubuntu Packages OS: Linux i was able to click and play mp3 files with kde3.5beta1, but it crashes after i upgraded with kde3.5beta2 and again still with kde3.5rc1. here is a copy of the traceback. the title of the KDE crash handler says "Noatun - The KDE crash handler". the short description says, "The application Noatun (noatun) crashed and caused the signal 11 (SIGSEGV)". (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1231690048 (LWP 8308)] [KCrash handler] #4 0xb5fd9648 in __gnu_cxx::__mt_alloc<std::string>::deallocate () from /usr/lib/libsoundserver_idl.so.1 #5 0xb5b09662 in Arts::readTypeSeq<Arts::InterfaceDef> () from /usr/lib/libmcop.so.1 #6 0xb5ac1fd9 in Arts::ModuleDef::readType () from /usr/lib/libmcop.so.1 #7 0xb5ac224f in Arts::ModuleDef::ModuleDef () from /usr/lib/libmcop.so.1 #8 0xb5ac3024 in Arts::IDLFileReg::startup () from /usr/lib/libmcop.so.1 #9 0xb5a9cd2b in Arts::StartupManager::startup () from /usr/lib/libmcop.so.1 #10 0xb5acf6fe in Arts::Dispatcher::Dispatcher () from /usr/lib/libmcop.so.1 #11 0xb6786cfc in Visualization::initDispatcher () from /usr/lib/libnoatun.so.1 #12 0xb67ca2f5 in NoatunApp::NoatunApp () from /usr/lib/libnoatun.so.1 #13 0xb67e7139 in kdemain () from /usr/lib/libkdeinit_noatun.so #14 0xb7f3a920 in kdeinitmain () from /usr/lib/kde3/noatun.so #23 0xb7d0a334 in free () from /lib/tls/i686/cmov/libc.so.6 #50 0x08051400 in vtable for QCString () #52 0x08051400 in vtable for QCString () #182 0xb7dc6d80 in in6addr_any () from /lib/tls/i686/cmov/libc.so.6 #189 0xb7dd10dc in ?? () from /lib/tls/i686/cmov/libc.so.6 #190 0xb7dd2900 in __malloc_initialize_hook () from /lib/tls/i686/cmov/libc.so.6 #205 0xb7d0c391 in malloc () from /lib/tls/i686/cmov/libc.so.6
Reassigning temporarily to noatun
The bug is in your gcc. Please let your distribution know about that so they can fix it. As a workaround, export GLIBCXX_FORCE_NEW=1 before starting KDE. *** This bug has been marked as a duplicate of 111115 ***
it's caused by a patch your distribution applies to libstdc++, I think. I get it as well without that environment variable.
SVN commit 480136 by charles: temporary workaround to the arts crashing. Apparently it's caused by a libstdc++ patch (?) applied by some stupid distributions. If you run gcc 4.0 and your artsd works just fine, you could very well not use this patch, as your libstdc++ isn't patched. CCMAIL:116221@bugs.kde.org M +0 -1 configure.in.in --- branches/arts/1.5/arts/configure.in.in #480135:480136 @@ -47,7 +47,6 @@ dnl KDE_CHECK_LIBDL dnl AC_PROG_LIBTOOL KDE_CHECK_QT_DIRECT -KDE_ENABLE_HIDDEN_VISIBILITY dnl for NLS support. Call them in this order! dnl WITH_NLS is for the po files, GNU_GETTEXT for the sources
On Sunday 13 November 2005 15:10, Charles Samuels wrote: > temporary workaround to the arts crashing. your patch is obsolete, this has already been fixed by a configure check.
On Mon, 14 Nov 2005, Dirk Mueller wrote: > On Sunday 13 November 2005 15:10, Charles Samuels wrote: > > > temporary workaround to the arts crashing. > > your patch is obsolete, this has already been fixed by a configure check. .. one that does not work on debian because, for some reason, it has the push/pops... presumably the configure check isn't sophisticated enough. cs
On Monday 14 November 2005 14:31, Charles Samuels wrote: > .. one that does not work on debian because, for some reason, it has > the push/pops... presumably the configure check isn't sophisticated > enough. which version of debian are you talking about? first of all the bugreport you mention was filed against "ubuntu linux", and second I tested the configure check on debian unstable and 3rd your commit just work arounds the crash in one place (while we have STL dependencies everywhere, arts is just the first application started during login that happens to trigger it). Please revert your patch and let us figure out how to refine the configure check.
According to http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19664#c47, compiler need to be patched to make the pop/push actually work, and I think the patch have not made itself into the 4.0.2 release. Maybe that's the problem.
Dirk Mueller wrote, on Monday 2005 November 14 1:44 pm: > which version of debian are you talking about? first of all the bugreport Debian unstable. > you mention was filed against "ubuntu linux", and second I tested the > configure check on debian unstable and 3rd your commit just work arounds > the crash in one place (while we have STL dependencies everywhere, arts is > just the first application started during login that happens to trigger > it). Yes, it does need to be fixed. I don't have access to the other distros so I can't make a properly tested patch, however. > > Please revert your patch and let us figure out how to refine the configure > check. Well, I'm just fed up of arts getting blamed for everything, so please can we fix the configure test first? Maybe this will be of help: charles@arkimedes 4.0 $ grep -rn 'visibi' * cxxabi.h:49:#pragma GCC visibility push(default) cxxabi.h:535:#pragma GCC visibility pop exception:40:#pragma GCC visibility push(default) exception:122:#pragma GCC visibility pop i486-linux-gnu/bits/gthr.h:33:#pragma GCC visibility push(default) i486-linux-gnu/bits/gthr.h:122:#pragma GCC visibility pop new:44:#pragma GCC visibility push(default) new:103:#pragma GCC visibility pop typeinfo:40:#pragma GCC visibility push(default) typeinfo:159:#pragma GCC visibility pop x86_64-linux-gnu/bits/gthr.h:33:#pragma GCC visibility push(default) x86_64-linux-gnu/bits/gthr.h:122:#pragma GCC visibility pop