12.07.2010 14:34, Raphael Kubo da Costa написав(ла):
I still think it might be good to take this upstream: you can try the
mailing list (ama...@kde.org), the forums or the IRC channel. If the
guys there say this is really a bug, you should then file a bug report
on bugs.kde.org.
As suspected, contacting the developers did not do much good... Jeff alleges below, the problem is with the FreeBSD's packaging of Amarok...

Anybody cares? Thanks,

   -mi

-------- Початкове пов?домлення --------
Тема: [Bug 244628] amarok dies on start-up -- can't create its own database
Дата: Tue, 10 Aug 2010 23:33:33 +0200 (CEST)
В?д: Jeff Mitchell <mitch...@kde.org>
В?дпов?сти: bug-cont...@bugs.kde.org
Кому: mi+...@aldan.algebra.com

https://bugs.kde.org/show_bug.cgi?id=244628


Jeff Mitchell <mitch...@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WAITINGFORINFO              |WONTFIX

--- Comment #11 from Jeff Mitchell <mitchell kde org> 2010-08-10 23:33:31 ---
Well, there's not much I can do.

We have *lots* of successful FreeBSD users, and the MySQL developer who told me that the error probably meant that the disk was full or permissions were wrong also told me that you should never, ever be seeing that error.

Given the nature of FreeBSD and how its packages are built, it's not impossible that you have broken shared libraries or some other deeper problem.

At this point I can really only suggest what I did in comment #3 -- that you contact the maintainer of the FreeBSD port and ask for his/her help.

Closing as WONTFIX, though if I could I'd really close it as CANTFIX.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You reported the bug.

_______________________________________________
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information

Reply via email to