Device notifier does not let you automount attached storage

[Alfred]

On KDE 4.8.2 in Kubuntu 12.04 Beta 2 (all updates installed), device notifier does not let you activate automount for any attached devices. If you go to "Removable devices", you can select everything correctly, but if you click "Apply", the button stays the same (should be greyed out to indicate it saved your settings). The next time you open the same page, nothing you changed was saved.

In .xsession-errors, it shows the following message:

plasma-desktop(26049)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application

The same problem happens on an untouched Kubuntu 12.04 Beta 2 live cd in live mode.

Please tell me if you need any further logs.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: plasma-desktop 4:4.8.2a-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
Date: Mon Apr 9 11:41:14 2012
ExecutablePath: /usr/bin/plasma-desktop
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcEnviron:
 LANGUAGE=de_AT
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
SourcePackage: kde-workspace
UpgradeStatus: No upgrade log present (probably fresh install)

[Alfred (alfred-egger)]

On KDE 4.8.2 in Kubuntu 12.04 Beta 2, device notifier does not let you activate automount for attached devices. If you go to "Removable devices", you can select everything correctly, but if you click "Apply", the button stays the same (should be greyed out to indicate it saved your settings). The next time you open the same page, nothing you changed was saved.

In .xsession-errors, it shows the following message:

plasma-desktop(26049)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application

The same problem happens on an untouched Kubuntu 12.04 Beta 2 live cd.

Please tell me if you need any further logs.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Alfred (alfred-egger)]

Update: It works well in "System Settings" -> "Removable Devices", but not directly over the control panel symbol.

[Jbev-kdebugs-01 (jbev-kdebugs-01)]

Can confirm this for 4.8.80.
A similar issue also seems to exist for setting a shortcut. Although the shortcut seems to be saved, the Apply button stays active and the shortcut doesn't do anything (should it?)

[Doublejay-bee (doublejay-bee)]

I am also experiencing this problem, with KDE 4.8.4, Linux 3.2.0-27-generic-pae

[Harald Sitter (apachelogger)]

Closing in favor of upstream report. Please refer there for updates on this issue.

[Lee (lee-eden)]

I am also having problems with this. Please see my post on kubuntu forums for more details. ( http://www.kubuntuforums.net/showthread.php?61612-MTP-based-MP3-player-not-mounting-%28Sony-Walkman%29&p=320548#post320548 ). Basically I am getting "The process for the MTP protocol died unexpectedly" when I try to connect an MTP device, but would like to mount it as removable storage (which works flawlessly under gnome), which does not seem to be an option in device notifier.

[Guenter-k (guenter-k)]

Same issue here after updating from openSuse 12.1(kde 4.9) to 12.3(kde4.10). Reason is:
"An unexpected error has occoured: Not authorized operation."

[Guenter-k (guenter-k)]

Works for me now: KDE 4.10.5 "release 6"

[Nate-b (nate-b)]

Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham