Bug 6322

Summary:	Device notifier applet does not save automatic mounting options
Product:	Mageia	Reporter:	Alexandr Bezenkov <alexandrbezenkov>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	g.sprik
Version:	2
Target Milestone:	---
Hardware:	i586
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=300840
Whiteboard:
Source RPM:	KDE 4.8.2	CVE:
Status comment:

Description Alexandr Bezenkov 2012-06-04 12:03:46 CEST

Description of problem:
Changing "automatic mounting" options in "removable media" section of applet configuration results nothing. When you change some options "apply" button becomes active, but if you press apply nothing changes, button remains active, settings not applied. Closing applet settings does not help either.

Version-Release number of selected component (if applicable):
I think applet is integrated in kde-workspace package group. It can not be installed separately. KDE 4.8.2.

How reproducible:
Always, two installations of "Mageia 2 RC" and "Mageia 2" on different PCs.

Steps to Reproduce:
1. Install Cauldron with KDE
2. Go to "Device notifier" applet settings.
3. Try to change any auto mounting settings in "removable devices" section.

Comment 1 Gerald 2012-09-06 11:34:18 CEST

It seems that a fix is available at kde.org ?

CC: (none) => g.sprik
Version: Cauldron => 2
See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=300840
Severity: minor => normal

Comment 2 Alexandr Bezenkov 2012-09-06 18:13:36 CEST

Well, I did not find any solution at kde.org, but it seems problem is not in Mageia, but in KDE. Tested with Arch and KDE 4.9 - issue is the same. I think this bug must be moved upstream.

Comment 3 Manuel Hiebel 2012-09-06 22:22:50 CEST

so feel free to do so (or reopen the bugs mentioned here)

Comment 4 Gerald 2012-09-07 01:42:55 CEST

In Mageia 2 we can upgrade to KDE 4.8.5 now. 
That solved this problem on my system.

Comment 5 Alexandr Bezenkov 2012-09-07 16:27:00 CEST

Well I think bug can be closed, as it is not Mageia issue.

Status: NEW => RESOLVED
Resolution: (none) => INVALID