[gentoo-amd64] Amarok plugin problem

[gentoo-amd64] Amarok plugin problem

[Mark Haney]

I sometimes opn amarok to listen to podcasts when I get some time to.
However, today I'm getting these errors:


/usr/kde/3.5/lib64/kde3/libamarok_void-engine_plugin.so: cannot open
shared object file: No such file or directory

/usr/kde/3.5/lib64/kde3/libamarok_xine-engine.so: cannot open shared
object file: No such file or directory

I've run revdep-rebuild and just emerged amarok by itself and I still
get this message.  Has anyone seen this problem before?


-- 
Ita erat quando hic adveni.

Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Amarok plugin problem

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 331 bytes --]

On Wed, 20 Dec 2006 12:25:01 -0500, Mark Haney wrote:

> /usr/kde/3.5/lib64/kde3/libamarok_void-engine_plugin.so: cannot open
> shared object file: No such file or directory

The location in my box is /usr/lib64/kde3/libamarok_void-engine_plugin.so


-- 
Neil Bothwick

Having children will turn you into your parents.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] Amarok plugin problem

[Mark Haney]

Neil Bothwick wrote:
> On Wed, 20 Dec 2006 12:25:01 -0500, Mark Haney wrote:
> 
>> /usr/kde/3.5/lib64/kde3/libamarok_void-engine_plugin.so: cannot open
>> shared object file: No such file or directory
> 
> The location in my box is /usr/lib64/kde3/libamarok_void-engine_plugin.so
> 
> 
Okay, mine too, now that I've looked for it.  Question remains why is
amarok looking for it in /kde/3.5 now when nothing has changed recently
on this system?



-- 
Ita erat quando hic adveni.

Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Amarok plugin problem

[Richard Freeman]

[-- Attachment #1: Type: text/plain, Size: 950 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark Haney wrote:
> Neil Bothwick wrote:
>> On Wed, 20 Dec 2006 12:25:01 -0500, Mark Haney wrote:
>>
>>> /usr/kde/3.5/lib64/kde3/libamarok_void-engine_plugin.so: cannot open
>>> shared object file: No such file or directory
>> The location in my box is /usr/lib64/kde3/libamarok_void-engine_plugin.so
>>
>>
> Okay, mine too, now that I've looked for it.  Question remains why is
> amarok looking for it in /kde/3.5 now when nothing has changed recently
> on this system?
> 

I've been having this problem for a while now - I've been avoiding
Amarok as a result.  Not sure what the cause is, and I haven't had much
luck searching for the issue online.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFiYbfG4/rWKZmVWkRApKEAJ9UNt5ZSUCKfVvO0PO2/V0h6rwFbgCbBDLv
Mxv3YQ/INWpJQ+P4rd82Oeo=
=++hi
-----END PGP SIGNATURE-----

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3875 bytes --]

[gentoo-amd64] Re: Amarok plugin problem

[Duncan]

"Mark Haney" <mhaney@ercbroadband.org> posted
458971ED.80304@ercbroadband.org, excerpted below, on  Wed, 20 Dec 2006
12:25:01 -0500:

> I sometimes opn amarok to listen to podcasts when I get some time to.
> However, today I'm getting these errors:
> 
> 
> /usr/kde/3.5/lib64/kde3/libamarok_void-engine_plugin.so: cannot open
> shared object file: No such file or directory
> 
> /usr/kde/3.5/lib64/kde3/libamarok_xine-engine.so: cannot open shared
> object file: No such file or directory
> 
> I've run revdep-rebuild and just emerged amarok by itself and I still get
> this message.  Has anyone seen this problem before?

I've not seen the problem, but if you've remerged and still see the
problem, it's likely a problem with your config.  KDE apps normally store
their user config in ~/.kde*, I have a number of symlinks here to a
non-hidden ~/kde3.5 dir and I don't know which one is the default, but
anyway, the configs of interest will be 

~/.kde*/share/apps/amarok/ , a directory with a number of files, and
~/.kde*/share/config/amarokrc , a single config file.  With amarok closed
(make sure it's not still running in the tray), rename this dir and file
to *.bak, so amorok starts with a clean config, and see if the problem
still exists.

If the problem disappears as I suspect it will, you'll have fixed that,
but will have lost all your saved settings and scores and preferences and
all that too, since that's all in the stuff you renamed (which is why I
said rename it, not delete it).  If you wish to retain all that, shut down
amarok again and remove the new nearly default settings it probably
created, and copy back amorokrc from your *.bak copy.  Restart and see if
the problem is still gone or reappears.

If the problem has reappeared, you'll know the issue is in the amarokrc
file and can delete it again (you still have the amorokrc.bak file, which
you copied back for testing) and restore the apps/amorok dir.  If the
problem didn't reappear, you'll know it's in the apps/amorok dir and can
leave the rc file where it is and proceed by copying half the files in the
amorok dir back into place.  Testing again will determine whether it's the
half you moved in or the half you left out.

Repeating this process, you'll soon isolate the problem file.  At that
point, you can either simply do without that file, recreating all the
settings and/or info that was stored therein if desired, or do what
amounts to the same process on the file, particularly if it's a text based
config file as the rc files for instance normally are.  If the file's
divided into sections, after ensuring you have a backup copy, you can
delete some of the sections while keeping the others and test that. 
Eventually you'll narrow down the problem to a single config section and
you can begin testing the individual setting lines within that section.

When you isolate the problem to an individual line, it's easy enough to
delete that line and reconfigure whatever it controlled if necessary. 
However, often you'll not need to go to that extreme.  By the time you
isolate the file, or the config section within the file causing the
problem, it'll often be less work to simply recreate its settings from the
defaults, than it will be to isolate the problem further.

The first time you use this technique, it'll be somewhat difficult, altho
I eased that by pointing out the subdir and config file for amarok so you
don't have to isolate to them from your entire ~/ dir.  However, after
doing it a couple times, you'll find it far easier to guess where in
general the problem is, and be able to wipe out 3/4 or more of the
possibilities at several steps in the isolation process, by simply making
and testing educated guesses of where the problem is.  For instance, if
you had tried this on your own, a look at your home directory may have
allowed you to conclude that ~/.kde* was the likely place for the config,
and a look in there may have allowed you to conclude that share was the
most likely suspect, and a look in there would have likely allowed you to
conclude that something either under config or under apps was the likely
suspect, and you could look for an amorok entry under each of them to
test, thus eliminating all the REST of your home dir, and all the REST of
the kde config dir, and all the REST of the share dir, and all the REST of
the apps subdirs and all the REST of the config files, without even
testing anything yet.  Each of those eliminations saves you a step in the
test and isolate process, thereby making it that much easier.  Eventually,
you'll know about where to look in most cases before you even start, and
will often be able to guess the right file on your first test.

Of course, you can simply blow away your entire config every time
something like this comes up too, but for people like me that spend a lot
of time customizing, that quickly becomes an untenable thing to
contemplate, as a few minutes of educated guess elimination testing can
often save literally hours of recustomization.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Amarok plugin problem

[Kevin Koltzau]

On Wednesday 20 December 2006 12:25 pm, Mark Haney wrote:
> /usr/kde/3.5/lib64/kde3/libamarok_void-engine_plugin.so: cannot open
> shared object file: No such file or directory
>
> /usr/kde/3.5/lib64/kde3/libamarok_xine-engine.so: cannot open shared
> object file: No such file or directory

I had a similar problem, I found there were .la files in that directory
but no .so

rm /usr/kde/3.5/lib64/kde3/libamarok_void-engine_plugin.la
rm /usr/kde/3.5/lib64/kde3/libamarok_xine-engine.la

fixed it for me
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Amarok plugin problem

[Denis Solaro]

On Wed, 20 Dec 2006 13:54:24 -0500
Richard Freeman <rich@thefreemanclan.net> wrote:

> 
> I've been having this problem for a while now - I've been avoiding
> Amarok as a result.  Not sure what the cause is, and I haven't had much
> luck searching for the issue online.

And amarok is not your light program either. I have seen trading systems deployed in banks that used less memory and CPU time.  Audacious is neat, it's small, doesn't need a cluster of mysql databases and a Sun Enterprise server to run. 


-- 
Saliva causes cancer, but only if swallowed in small amounts over a long
period of time.
		-- George Carlin
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: Amarok plugin problem

[Harm Geerts]

On Thursday 21 December 2006 06:21, Denis Solaro wrote:
> On Wed, 20 Dec 2006 13:54:24 -0500
>
> Richard Freeman <rich@thefreemanclan.net> wrote:
> > I've been having this problem for a while now - I've been avoiding
> > Amarok as a result.  Not sure what the cause is, and I haven't had much
> > luck searching for the issue online.

Kevin Koltzau posted the solution, if you haven't seen his mail come by you 
might want to look on gmane. there have been reports about lost mail on 
gentoo's ML's (but this may have already been fixed. I'm not sure, so if 
anyone can confirm that I would be thankfull)

> And amarok is not your light program either. I have seen trading systems
> deployed in banks that used less memory and CPU time.

Yeah, but they don't play music
or provide easy access to media devices
or provide easy access to additional information about artists and albums
or search for the lyrics of the song you listen to
or integrate last.fm, which provides information about your *audioprofile*
or supports dynamic playlists which selects tracks based on your criteria

amarok is not light because it's not designed with that goal in mind

and the ram usage is only a problem when it's needed for something else.
Keep in mind, most desktop systems rarely fully utilize their resources. If 
ram isn't used, it's wasted.

> Audacious is neat, 
> it's small, doesn't need a cluster of mysql databases and a Sun Enterprise
> server to run.

amarok also runs fine with sqlite, so this shouldn't be keeping anyone back.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Amarok plugin problem

[Richard Freeman]

[-- Attachment #1: Type: text/plain, Size: 576 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kevin Koltzau wrote:
> I had a similar problem, I found there were .la files in that directory
> but no .so
> 
> rm /usr/kde/3.5/lib64/kde3/libamarok_void-engine_plugin.la
> rm /usr/kde/3.5/lib64/kde3/libamarok_xine-engine.la
> 
> fixed it for me

Thanks - that did the trick!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFjEiaG4/rWKZmVWkRAqvEAJ4iXzVFt6oE41yx7yM085bSL3M36ACfVJoJ
ZSEkU3I/JA57jzbYJs37Las=
=CNV1
-----END PGP SIGNATURE-----

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3875 bytes --]

[gentoo-amd64] Seg Faults

[sean]

Ever since upgrading GCC some apps, after emerging from portage, get
segmentation faults when I try to start them.

Suggestions on what I might be able to do to cure this problem?
I am guessing that I should enter bugs?
If so, what would be the best info to enter for the bug report?

				Thanks
				Sean
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Seg Faults

[Daniel Iliev]

sean wrote:
> Ever since upgrading GCC some apps, after emerging from portage, get
> segmentation faults when I try to start them.
>
> Suggestions on what I might be able to do to cure this problem?
> I am guessing that I should enter bugs?
> If so, what would be the best info to enter for the bug report?
>
> 				Thanks
> 				Sean
>   

Hi,

Have you tried "revdep-rebuild"?
I wouldn't go so fast on reporting bugs - checking false bugs wastes
developers time. So if I were you I would try to solve the problem here
in the user list first. Try revdep-rebuild if you haven't already done this.


P.S.

FYI: It is called "thread hijacking" when someone replies to a letter on
different topic and changes the subject. This irritates many people and
especially the original poster. The normal way to open a new thread is
to write a new letter to the list. All replies are placed in the thread
which you replied to, changing the subject doesn't matter.

-- 
Best regards,
Daniel


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Seg Faults

[sean]

Daniel Iliev wrote:
> sean wrote:
>> Ever since upgrading GCC some apps, after emerging from portage, get
>> segmentation faults when I try to start them.
>>
>> Suggestions on what I might be able to do to cure this problem?
>> I am guessing that I should enter bugs?
>> If so, what would be the best info to enter for the bug report?
>>
>> 				Thanks
>> 				Sean
>>   
> 
> Hi,
> 
> Have you tried "revdep-rebuild"?
> I wouldn't go so fast on reporting bugs - checking false bugs wastes
> developers time. So if I were you I would try to solve the problem here
> in the user list first. Try revdep-rebuild if you haven't already done this.
> 

	Already tried that.

> 
> P.S.
> 
> FYI: It is called "thread hijacking" when someone replies to a letter on
> different topic and changes the subject.

	That was an accident on my part, not intentional.


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Seg Faults

[Daniel Iliev]

sean wrote:
>> Have you tried "revdep-rebuild"?
>>
>>     
> 	Already tried that.
>
>   


Did you follow the official GCC upgrade guide [1] because it demands
"emerge -e system" and "emerge -e world"?
[1] http://www.gentoo.org/doc/en/gcc-upgrading.xml


Anyway, if you think you should file a bug report there is a detailed
"how-to" at bugs.gentoo.org:

http://bugs.gentoo.org/page.cgi?id=bug-writing.html




>> FYI: It is called "thread hijacking" when someone replies to a letter on
>> different topic and changes the subject.
>>     
>
> 	That was an accident on my part, not intentional.
>   

I feel it is better to explain then to flame, so I do explain every time
it happens.



-- 
Best regards,
Daniel


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Seg Faults

[Michel Merinoff]

Daniel Iliev wrote:
> FYI: It is called "thread hijacking" when someone replies to a letter on
> different topic and changes the subject. This irritates many people and
> especially the original poster. The normal way to open a new thread is
> to write a new letter to the list. All replies are placed in the thread
> which you replied to, changing the subject doesn't matter.
>   
Maybe, this is rational to post rules say every half a month and set a
moderator to regulate all this, like in good old FIDO?
And, for example, a list of what kind of questions should appear here.
Send instant messages to your online friends http://uk.messenger.yahoo.com 

-- 
gentoo-amd64@gentoo.org mailing list