Doh! I know what that is :) I just described the symptoms :)

My dilema was not that the debug symbols appear. I program 6-7 years now or so .... my questions was if for anyone else who compiled amaroK or Juk they were also crashing due to the "aRTs Engine" or was this just my case ...

Thanks,

Andrei

Warlock_BA

Reply-to: warlock_ba@hotmail.com

"I collect my thoughts and I rise above all that despises me." - VNV Nation - Serial Killer

>From: Per Bjornsson <perbj@stanford.edu> >Reply-To: For testers of Fedora Core development releases <fedora-test-list@redhat.com> >To: For testers of Fedora Core development releases <fedora-test-list@redhat.com> >Subject: Re: aRTs Engine dying after KDE 3.4rc1 update >Date: Tue, 08 Mar 2005 13:26:02 -0800 > >On Tue, 2005-03-08 at 23:01 +0200, Botoaca Andrei wrote: > > I had this problem since KDE3.4 was out. Every tool based on the so called > > "aRTs engine" like Juk and amaroK die on start, leaving a blody trail of "no > > debug info found" in the crash manager of KDE. > > Anybody any ideea why this crash occurs, and if so, does anyone know also a > > remedy for it ? > >Perhaps if you install the arts-debuginfo package it will find some >debugging symbols, which might make it easier to figure out what's going >on? It might at least make the stack trace (which I think is what you're >seeing in the crash manager, at least that's what shows up in Gnome's >bug-buddy and it seems to be the sane thing to show) more useful to the >developers. > >Cheers, >Per > >-- >Per Bjornsson <perbj@stanford.edu> >Ph.D. Candidate, Department of Applied Physics, Stanford University > >-- >fedora-test-list mailing list >fedora-test-list@redhat.com >To unsubscribe: >http://www.redhat.com/mailman/listinfo/fedora-test-list


Express yourself instantly with MSN Messenger! MSN Messenger Download today it's FREE!