I have just recently set up a system running KDE 3.5 on Sid. Most parts of it worked fine, but a few days ago I found (after aptitude update) that Kopete had been updated. Since that was a package I needed and it had not yet been able to install, I did "aptitude upgrade". The only thing it effected (that I couldn't fix quickly) is Amarok. Now whenever I run Amarok, I get the following output:
amaroK: [Loader] Starting amarokapp.. amaroK: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp. amaroK: [Loader] amarokapp probably crashed! There is a case like this in the archives of this list and a response suggests changing the output in amarokrc to gstreamer or xine-engine, which I've tried. I've found other similar problem reports and the only other solution I've seen is to delete amarokrc completely. I backed it up elsewhere and deleted it. This time the spash screen came up (I had disabled it), and promptly closed, giving me the same message. I don't know C or C++ (I presume it's in one of those), and I've never used a debugger, so I don't see how it thinks I'm using anything like gdb. So why does it think I'm using gdb and what can I do to get Amarok to work? Thanks! Hal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
