Bug 84094 - Crash in KAudioManagerPlay initialization
Summary: Crash in KAudioManagerPlay initialization
Status: CLOSED UNMAINTAINED
Alias: None
Product: arts
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Multimedia Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-27 18:22 UTC by Teemu Rytilahti
Modified: 2008-11-19 23:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Teemu Rytilahti 2004-06-27 18:22:59 UTC
Version:           unknown (using KDE 3.2.91 (3.3 beta1), compiled sources)
Compiler:          gcc version 3.3.4 (Debian 1:3.3.4-2)
OS:                Linux (i686) release 2.6.7

Install goes well, but when you try to start it, it'll crash. It'll crash here always, and has been crashing for a while now, including the old installation too.

I'm using currently clean installation of today's JuK and KDE as I got HD breakage and that's why I'm still reporting this. I've contacted you with several times about the problem with USE_ARTS which has something to do with thise one too. You've always said there's no problem and so on, but for me there is.

Backtrace:
----------
Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1102008192 (LWP 13374)]
[KCrash handler]
#3  0x4006d8ba in KAudioManagerPlay::KAudioManagerPlay ()
   from /home/tpr/kdecvshead/lib/libartskde.so.1
#4  0x0806ff1b in ArtsPlayer::setupArtsObjects (this=0x840cbf0)
    at artsplayer.cpp:226
#5  0x080700a9 in ArtsPlayer::setupPlayer (this=0x840cbf0)
    at artsplayer.cpp:250
#6  0x0806f5d6 in ArtsPlayer (this=0x840cbf0) at artsplayer.cpp:51
#7  0x0808ef1f in createPlayer (system=0) at playermanager.cpp:58
#8  0x08090331 in PlayerManager::setup (this=0x81cfbf8)
    at playermanager.cpp:529
#9  0x08090065 in PlayerManager::player (this=0x81cfbf8)
    at playermanager.cpp:484
#10 0x0808f164 in PlayerManager::playing (this=0x81cfbf8)
    at playermanager.cpp:99
#11 0x080b06bd in SystemTray (this=0x8443480, parent=0xbffff590, 
    name=0xbffff590 "àGE\b") at systemtray.cpp:101
#12 0x08087947 in JuK::setupSystemTray (this=0x81c8e20) at juk.cpp:173
#13 0x080867f0 in JuK (this=0x81c8e20, parent=0xbffff590, 
    name=0xbffff590 "àGE\b") at juk.cpp:61
#14 0x0808e5a8 in main (argc=-1073744496, argv=0xbffff590) at main.cpp:76

Console output:
---------------
tpr@tuli:~$ juk
juk: WARNING: KAction "pause" is not defined yet.
juk: WARNING: [void PlayerManager::setup()] Could not find all of the required actions.
kdecore (KAction): WARNING: KAction::plug(): has no KAccel object; this = 0x822d800 name = newPlaylist parentCollection = 0x81cfca0
kdecore (KAction): WARNING: KAction::plug(): has no KAccel object; this = 0x820f348 name = newSearchPlaylist parentCollection = 0x81cfca0
kdecore (KAction): WARNING: KAction::plug(): has no KAccel object; this = 0x820f9f8 name = newDirectoryPlaylist parentCollection = 0x81cfca0
kdecore (KAction): WARNING: KAction::plug(): has no KAccel object; this = 0x82182e8 name = file_save parentCollection = 0x81cfca0
juk: WARNING: KAction "outputSelect" is not defined yet.
Launched ok, pid = 13441
Launched ok, pid = 13446
Comment 1 Scott Wheeler 2004-06-27 19:01:45 UTC
This is crashing in libartskde, not in JuK code.  This is actually something completely separate from the issue that you reported previously.  Can you recompile kdelibs/arts with full debugging so that we can get a better backtrace?
Comment 2 Helio Chissini de Castro 2004-06-27 20:21:23 UTC
Exactly same i obtained at lab.
Tomorrow i'll provide a bt with full debug too..
Comment 3 Scott Wheeler 2004-06-27 20:28:12 UTC
"Exactly same i obtained at lab."

Not if it's the same one that you reported to me earlier.  That one was crashing when it tried to access the player -- not when initializing it.
Comment 4 Teemu Rytilahti 2004-06-27 23:36:38 UTC
Well, I'm already using --enable-debug=full for all my KDE stuff and even tried to reforce it without success.. Any other ideas?
Comment 5 Helio Chissini de Castro 2004-06-28 00:06:25 UTC
First debug output...

#0  0x4100bfc3 in fREe (mem=0x8433f98) at malloc.c:3045
#1  0x4100d565 in free (m=0x8433f98) at malloc.c:5535
#2  0x41c84ac1 in operator delete(void*) () from /usr/lib/libstdc++.so.6
#3  0x41c67d07 in std::string::_Rep::_M_destroy(std::allocator<char> const&) () from /usr/lib/libstdc++.so.6
#4  0x41c67f8d in std::string::~string() () from /usr/lib/libstdc++.so.6
#5  0x40709d1a in Arts::TmpGlobalComm_impl::put(std::string const&, std::string const&) (this=0x842ee58, variable=@0xbfffdd60, value=@0xbfffdd40)
    at tmpglobalcomm.cc:50
#6  0x406e0ce0 in Arts::GlobalComm::put(std::string const&, std::string const&) (this=0xbfffdd80, variable=@0xbfffdd60, value=@0xbfffdd40) at core.h:1492
#7  0x406dd42a in Dispatcher (this=0x840cc80, ioManager=0x840cd40, startServer=noServer) at dispatcher.cc:269
#8  0x400ab829 in KArtsDispatcher (this=0x840cc50, parent=0x0, name=0x0) at kartsdispatcher.cc:42
#9  0x0807294e in ArtsPlayer::setupPlayer() (this=0x840cff8) at artsplayer.cpp:248
#10 0x08071c4b in ArtsPlayer (this=0x840cff8) at artsplayer.cpp:51
#11 0x08091486 in createPlayer (system=0) at playermanager.cpp:58
#12 0x08092c77 in PlayerManager::setup() (this=0x819c4a8) at playermanager.cpp:529
#13 0x08092a01 in PlayerManager::player() const (this=0x819c4a8) at playermanager.cpp:484
#14 0x080917c9 in PlayerManager::playing() const (this=0x819c4a8) at playermanager.cpp:99
#15 0x080b50d0 in SystemTray (this=0x8423aa0, parent=0x81978b8, name=0x80d03a4 "systemTray") at systemtray.cpp:101
#16 0x08087521 in JuK::setupSystemTray() (this=0x81978b8) at juk.cpp:173
#17 0x0808610a in JuK (this=0x81978b8, parent=0x0, name=0x0) at juk.cpp:61
#18 0x0808c77d in main (argc=2, argv=0xbfffe244) at main.cpp:76
Comment 6 Teemu Rytilahti 2004-06-28 17:00:24 UTC
Well, I installed libs like akoda, libmad and something else too, and then recompiled kdemm/arts, juk and arts module and now it seems to work here. So I think that's caused by a missing lib or inproper installation. Some configure script doesn't check if everything arts needs is available?
Comment 7 Matt Rogers 2008-11-19 23:39:56 UTC
Arts is no longer developed and has been unmaintained for quite some time - more than 2 years. With phonon as the replacement for arts in KDE4, we're closing out all the arts bugs in Bugzilla since there is no chance of them being fixed.

Thanks