Bug 210092 - The Browsers column is not selectable, meaning no music can be played
Summary: The Browsers column is not selectable, meaning no music can be played
Status: RESOLVED WORKSFORME
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.2.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-10 17:00 UTC by Patrick O'Callaghan
Modified: 2009-10-12 16:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick O'Callaghan 2009-10-10 17:00:34 UTC
Version:           2.2.0 (using 4.3.1 (KDE 4.3.1), 4.3.1-3.fc11 Fedora)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.30.8-64.fc11.x86_64

I upgraded from amarok-2.1.1-4.fc11.x86_64 (which was working) to amarok-2.2.0-2.fc11.x86_64 via yum from the Fedora updates repo and find it essentially borked in that I can't select any music. None of the options in the left-most Browsers column (Local Music, Internet, Playlists and Files) are selectable when clicked on. I even tried removing .kde/shared/apps/amarok and .kde/share/config/amarokrc to make sure I was starting afresh, but it makes no difference.

I then logged in as a different user who had not previously used Amarok and everything worked as it should.

Is there a way to get this to work without removing my .kde directory and reconfiguring my entire KDE session profile?
Comment 1 Mark Kretschmann 2009-10-10 17:20:58 UTC
This could be a packaging problem. It's unlikely that this is an Amarok bug per se.

Could you maybe ask in the Fedora forums?
Comment 2 Patrick O'Callaghan 2009-10-10 17:28:50 UTC
I did ask on the Fedora KDE list a couple of days ago (see http://lists.fedoraproject.org/pipermail/fedora-kde/2009-October/004237.html), but no-one else seems to have this problem.
Comment 3 Patrick O'Callaghan 2009-10-12 16:21:04 UTC
Following a suggestion of Rex Dieter, I changed the widget style from GTK+ to Oxygen and the problem went away.