Amarok 2.2.0 broken?

Gilboa Davara gilboad at gmail.com
Sat Oct 10 20:20:52 UTC 2009


On Sat, 2009-10-10 at 12:31 -0430, Patrick O'Callaghan wrote:
> On Sat, 2009-10-10 at 18:10 +0200, Gilboa Davara wrote:
> > On Sat, 2009-10-10 at 10:34 -0430, Patrick O'Callaghan wrote:
> > > [Replying to myself here]
> > > 
> > > On Fri, 2009-10-09 at 15:06 -0430, Patrick O'Callaghan wrote:
> > > > On Fri, 2009-10-09 at 18:31 +0200, Eike Hein wrote:
> > > > > On 10/09/2009 06:17 PM, Patrick O'Callaghan wrote:
> > > > > > Am I the only one seeing this?
> > > > > 
> > > > > Hmm - working fine here, as did all the pre-releases.
> > > > > 
> > > > > Perhaps dry wiping amarokrc as well?
> > > > 
> > > > Tried that. It rescanned my collection (which it had already done
> > > > before) and still won't allow me to see it, let alone select anything.
> > > 
> > > I logged in as a different user and Amarok worked correctly. IIRC the
> > > user had not previously used Amarok.
> > > 
> > > It seems that Amarok, like many KDE apps, is iffy with earlier versions
> > > of its own config files. I'm afraid I don't consider removing my .kde
> > > directory and reconfiguring my entire KDE profile *again* to be a
> > > reasonable solution to this. 
> > > 
> > > I've reported the problem as https://bugs.kde.org/show_bug.cgi?id=210092
> > > 
> > > poc
> > 
> > No need to remove .kde, I fixed amarok by
> > removing .kde/share/apps/amarok and .kde/share/config/amarok*
> 
> As I said in earlier in the thread, and in my bug report, this didn't
> work for me.
> 
> Unfortunately the first response from the bug report was "this looks
> like a packaging problem, why don't you ask on the Fedora forums?".
> 
> poc

If indeed it's a packaging problem, I'd report it down-stream
(bugs.redhat) as well.

- Gilboa




More information about the kde mailing list