Bug 317328 - Applying settings with the "Apply" button doesn't grey out the button
Summary: Applying settings with the "Apply" button doesn't grey out the button
Status: RESOLVED DUPLICATE of bug 275190
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.7-git
Platform: Other Linux
: NOR minor
Target Milestone: 2.8
Assignee: Amarok Developers
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-03-25 14:03 UTC by Myriam Schweingruber
Modified: 2013-04-13 08:47 UTC (History)
0 users

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 Myriam Schweingruber 2013-03-25 14:03:54 UTC
When applying a setting in the "Configure Amarok" dialog applies the new setting, but doesn't grey out the button. This works on KDE though.
Comment 1 Andi Clemens 2013-03-29 15:15:28 UTC
For me it doesn't seem to save the settings at all. After upgrading to 2.7.0, my collection "is gone" and I can not add any library paths. The config isn't saved. I removed the amarokrc file and the apps folder in $HOME/.kde4/share/apps/, but still amarok is dead. I can't get it to work anymore.
Comment 2 Myriam Schweingruber 2013-03-29 16:16:44 UTC
(In reply to comment #1)
> For me it doesn't seem to save the settings at all. After upgrading to
> 2.7.0, my collection "is gone" and I can not add any library paths. The
> config isn't saved. I removed the amarokrc file and the apps folder in
> $HOME/.kde4/share/apps/, but still amarok is dead. I can't get it to work
> anymore.

Which distribution do you use? There is a serious packaging problem on Arch with the switch to MariaDB, they simply forgot to recompile the Amarok packages with the new dependencies. See also bug 317370
Comment 3 Myriam Schweingruber 2013-04-11 08:18:50 UTC
Setting status correctly.
Comment 4 Myriam Schweingruber 2013-04-13 08:47:27 UTC
The problem is in kdelibs -> kdeui -> kpushbutton, the Apply button simply doesn't work

*** This bug has been marked as a duplicate of bug 275190 ***