[kde-freebsd] amarok-kde4 dies at start-up

Raphael Kubo da Costa kubito at gmail.com
Thu Jul 8 16:18:58 CEST 2010


On Thursday 08 July 2010 07:06:55 Jerry wrote:
> On Thu, 8 Jul 2010 14:45:59 +1100
> 
> Dima Panov <fluffy at fluffy.khv.ru> articulated:
> > On Thursday 08 July 2010 07:57:18 Rusty Nejdl wrote:
> > >  Rusty made some high-level suggestions, but would not follow-up
> > > 
> > > explaining, how to perform them. But even if/when the suggestions are
> > > applied and work, the problem remains -- your port does not work "out
> > > of the box"...
> > > 
> > > I may have missed an email you
> > > sent out later asking for explanation so can you please resend that as
> > > I don't recall anything nor any feedback from what I sent.
> > > 
> > > I am running
> > > this port out of the box without issue so we need to find what is
> > > different in your environment. That means you need to do some lifting
> > > here to help us find what is different in your system or we will not
> > > get any further.
> > > 
> > > What happened when you removed the file? For some
> > > reason, your system was unable to read it. I don't recall seeing any
> > > information to you about that file (size, permissions, type, etc) until
> > > now.
> > 
> > I can guess. Amarok 2.3 can't use now embedded library from fresh mysql51
> > to init own internal database by innodb issue.
> > 
> > So only one way - revert to mysql50, build amarok, run it, configure it
> > (no matter - external or internal db), switch back to mysql51 and
> > rebuild amarok. It will use previously created database without any
> > problems.
> > 
> > All anger please route ro mysql developers, which broke compatibility :(
> 
> I fail to see why you are blaming the MySQL developers. For starters,
> version '50' is far from current. The Amarok developers failed to
> properly write/test their application to insure compatibility. It is
> not MySQL's job to insure compatibility with other minor utilities.

Have you guys talked to the Amarok developers (and/or filed bug reports) to 
check if this is really the cause of the issue?


More information about the kde-freebsd mailing list