amarok - no audio plugins [solved]

Kaste · Last edited by Kaste on Wed Nov 29, 2006 8:39 am; edited 1 time in total

Forgive me if this has been answered before. I've searched the forum extensively and i can't find a solution.

I ran an update world and as we all know xmms was removed and the use flag went with it. So amarok and a few other sound related packages got rebuilt and since then amarok won't start anymore. It will always complain with that usual annoying message

Conan · Guru Joined: 02 Nov 2004 Posts: 360

1) find /usr/kde -name \*amarok\*.la -print0 | xargs -0 rm if that does not work update to kdelibs-3.5.4-r2 if that does not work, make sure you actually source /etc/profile somewhere in your .bashrc or something

Kaste · Posted: Tue Oct 24, 2006 6:27 pm Post subject:

Hmm I tried you solution but it didn't find anything. I fixed it I don't know how though, I remeber deleting the amarokrc and doing cd /var/tmp/portage/amarok and so on and then doing make uninstall from there followed by a temerge amarok. Don't ask me why emerge -C amarok && emerge amarok didn't work

I know this is messy, but what the heck, it worked. Amarok seems to get buggier and buggier on my system anyway

Kaste · Posted: Wed Oct 25, 2006 2:47 pm Post subject:

Ok scratch that. It came back. Oh how I hate it.

Kaste · Posted: Wed Nov 15, 2006 8:03 pm Post subject:

Bump

Someone help me please, I'm all out of ideas save for reinstalling which is not an option. I deleted my amarokrc a dozen times, i followed the instructions in that popup box thrice and kde got updated once in the mean time. I even did an emerge -e amarok but this pesky problem is just so incredibly persistent.

Please help me. I never liked any xmms derivative. amarok is the killer package for linux for me and i have been without it for almost 4 weeks now.

yngwin · Posted: Wed Nov 15, 2006 9:13 pm Post subject:

Have you rebuilt xine-libs?
_________________
"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF

DeadlyMuffin · Tux's lil' helper Joined: 29 Sep 2004 Posts: 104

I had the same problem, the solution for me was

chmod 744 /var/tmp/kdecache-user/ksycoca

where you replace user with your user name.

I got the answer from this thread:http://forums.gentoo.org/viewtopic-t-370929-highlight-amarok.html

Annoys me that with all the messages to migrate away from xmms and how it's going to be removed, they manage to screw up the other audio players in the process. Unacceptable.

Kaste · Posted: Fri Nov 17, 2006 12:26 am Post subject:

@DeadlyMuffin
My ksycocoa was accessible I checked that earlier.

@Yngwin

You are my personal hero. That seems to have fixed the problem for now. Thank you so much.
I'm still puzzled that it didn't get done by emerge -e amarok and I also don't understand why it didn't find the helix backend. It works again as it worked before. Is this dependant on xinelibs as well?

boris_qd · Posted: Fri Nov 17, 2006 1:13 pm Post subject:

this still doesn't fix the problem for me. neither do any of the other hints.

What's going on here? I think the devs (or someone) needs to produce a definative guide on how to fix this problem. It seems that the same error is cause by many - some still undiscovered - causes.

VsMaX · n00b Joined: 29 Aug 2006 Posts: 40 Location: Poland

Have same problem here. I dont know why that crashed.

Ok i repaired that by
chmod 744 /var/tmp/kdecache-<your_user_name>/ksyscoa

And after second run amarok as user it was working.
_________________
Amd Athlon64 X2 3800 , Radeon X1600Pro 256 , 2x512RAM KINGSTON , Sound Blaster Audigy LS

Chetnie zajme sie malymi robotkami w C++ / Pascalu za darmo oczywiscie

I offer my little expreience in C++ / pascal of course for free

Just to learn

boris_qd · Posted: Sun Nov 19, 2006 3:39 pm Post subject:

this didn't work for me.

I'm really frustrated and do hope that someone finds a solution that works for (all) users. I guess the same problem is being caused by a number of different reasons.

VsMaX · n00b Joined: 29 Aug 2006 Posts: 40 Location: Poland

damn after restart it now doesn't work.
_________________
Amd Athlon64 X2 3800 , Radeon X1600Pro 256 , 2x512RAM KINGSTON , Sound Blaster Audigy LS

Chetnie zajme sie malymi robotkami w C++ / Pascalu za darmo oczywiscie

I offer my little expreience in C++ / pascal of course for free

Just to learn

boris_qd · Posted: Tue Nov 21, 2006 10:48 pm Post subject:

so I did manage to fix this problem after all.

The problem occured for me after I upgraded from kde 3.5.x to 3.5.5 (don't remember what the previous version was at the moment).

I fixed the problem by deleting _every_ file in /usr/kde/3.5 that was older then 10 days.

find /usr/kde/3.5 -mtime +10 | xargs rm -rf

_pF_ · Posted: Wed Nov 22, 2006 9:01 am Post subject:

Horatio · Posted: Thu Nov 23, 2006 2:43 am Post subject:

_PF_, I don't know if that is the best or complete solution. Although, I tried boris_qd suggestion. As it was late, I was tired, and thinking of emergeing gnome with all the recent problems with kde emerges. I still had to reemerge kde-base, kdenetwork, kdelibs ... (but not arts)

boris_qd · Posted: Mon Nov 27, 2006 5:19 pm Post subject:

boris_qd · Posted: Mon Nov 27, 2006 5:23 pm Post subject:

flappadap · n00b Joined: 30 Mar 2005 Posts: 34

boris_qd · Posted: Tue Nov 28, 2006 2:49 am Post subject:

actually I tried this first but some libraries/files were still causing problems.

If it works for you - great - otherwise try my fix (with 10 days replaced by what is reasonable for you).

Conan · Guru Joined: 02 Nov 2004 Posts: 360

That is a really bad idea.

In any given 3.5.blah release of kde, there will be some packages that are not updated, simply because they have not changed. Therefore you will have some files from older kde releases in there anyways, though they are the newest availible version. Your command deletes these files along with stray files, causing possible huge problems.

boris_qd · Posted: Tue Nov 28, 2006 2:31 pm Post subject:

That sounds true.

But in practice it hasn't caused any problems. Of course before I ran the command to delete the files I looked at the list to see what would be deleted. I wish I had saved the list - but I didn't. In any case, nothing looked vital so I went ahead an deleted the files. (You should look at the file list before you delete any files)

Of course, the proof is in the pudding. The problem went away and I have no further problems.There is at least one other thread dealing with the same issue (mime type errors preventing things from working.). I posted the same solution there and it seems to be working for a number of people. I guess there could be some peculiar things about my installation that made it work without problems although I can't think of what they are.

So really bad idea? Probably not. Not the best fix - I can agree with that. Worst case I have to emerge some damaged kde packages again.

The real fix would be to have the kde upgrade process do a better job of cleaning / dealing with old kde installations.

Finally, I can't really take credit for the fix. I found it be searching bugzilla for similar problems and it was recommended by several (what seemed to me to be) kde developers. so...

swooshOnLn · Posted: Tue Nov 28, 2006 2:40 pm Post subject:

Just because it works is no reason to assume its not a bad idea. Deleting any wild card is dangerous. Especially something on the lines of "10 days sounds good". I wouldn't recommend trying the above unless you back up first. Just because you havnt encountered a problem yet doesn't mean its a fix.
_________________
"WARNING: you may LOL"

This is my font size, color, and signature. It will change to whatever I pick. How cool is that?

boris_qd · Posted: Tue Nov 28, 2006 5:04 pm Post subject:

If you read my post 10 days wasn't arbitrary - it was chosen to be from _before_ I upgraded kde.

In anycase - no other posted solution fixed my problem and this did. So in fact, it is a fix, and as far as I'm concerned - the only fix.

I would encourage people to look at the file list (and save the file list!) before they delete the files. You can always use equery to find out who owns the an emerge those packages after deleting the files.

According to bugs on bugzilla - the problem is caused by files being around in the kde path that shouldn't be there. So on some level the solutions _must_ boil down to deleting something. You could use a more fine grained search I suppose. For instance, taking a look at the files that will be deleted, finding out who owns them, and then deleting them one by one, testing the package and emerging if necessary.

In my case all the problem files were orphaned from previous installs in the 3.5 series. Meaning, the packages expected them to be elsewhere.

Also, the worst case scenario is that some packages have to be re-emerged.

Again - the real fix is to change how kde deals with previous installs when you upgrade. But it doesn't look like anyone is taking that approach seriously.

zaratustra_20 · Posted: Tue Nov 28, 2006 6:42 pm Post subject:

Sorry folks, is amarok capable of playing wma? for me, it says "no suitable demux plugin"

Kaste · Posted: Tue Nov 28, 2006 8:30 pm Post subject:

Yes absolutely. Can't really remeber what i had to do to get it to work though. :/

I think what i did was emerge gst-plugins-bad but don't pin me down for this one. I'm not really confident.