| Summary: | kded: Storage Media configuration not saved: Turning off Auto Action is not possible | ||
|---|---|---|---|
| Product: | [Unmaintained] kio | Reporter: | MartinG <gronslet> |
| Component: | media | Assignee: | Kevin Ottens <ervin> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | gokdenizk, rdieter |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Fix NotifierSettings::resetAutoAction() | ||
|
Description
MartinG
2006-08-02 17:09:46 UTC
It seems that I've got the service 'autofs' running - is this the service that takes care of "automounting" cdroms under FC5? In that case, I guess I need to configure these files:
# ll /etc/auto.*
-rwxr-xr-x 1 root root 558 jun 23 07:42 /etc/auto.smb
-rwxr-xr-x 1 root root 1292 jun 23 07:42 /etc/auto.net
-rw-r--r-- 1 root root 581 jun 23 07:42 /etc/auto.misc
-rw-r--r-- 1 root root 322 jun 23 07:42 /etc/auto.master
I tried to enable the auto.misc file in /etc/auto.master:
/misc /etc/auto.misc --timeout=60
where in the auto.misc file I've got:
cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom
but that didn't seem to help. Shutting down the autofs service didn't change anything either.
Sorry for beeing slightly off topic with this, but getting a notification on cdrom insertion is what I want to get working again...
Btw. I forgot to mention that manually mounting the cdrom manually ("mount /mnt/cdrom") works when I've put in my /etc/fstab:
/dev/scd0 /mnt/cdrom auto ro,noauto,users 0 0
Apparently this also happens in Gnome see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=201400 I have also run into this bug. Kubuntu Edgy. If it helps, I set the auto action on during the pop-up for the media, rather than through Control Center. I can confirm this bug as well (Kubuntu Edgy, running KDE 3.5.5) . If I have set the auto-action for a media device, I cannot disable that auto-action, I can only move it to another application using the Storage Media utility. My workaround at present is: 1. Create a temporary application entry called "temp" and attach it to the devices that have auto-start flags set. 2. Set this application to be the auto-start for each of these media devices. 3. Remove the "temp" application, effectively removing the auto-start flag as well. Hope this helps someone Sean Sean, Ahh, excellent workaround! Thanks. Sean Hodges wrote: [bugs.kde.org quoted mail] I confirm the problem on Mandriva 2007.1 Another way to work around it is to edit the file ~/.kde/share/config/medianotifierrc There should be a line for each defined auto-action. Remove the line you don't want and save the file. This also happens on gentoo, kde version 3.5.5 Editing ~/.kde/share/config/medianotifierrc manually is a "working" workaround. *** Bug 145975 has been marked as a duplicate of this bug. *** Confirmed on KDE 3.5.7 from svn. The attached notifiersettings.patch solves the bug. It applies against kdebase package from KDE 3.5.7. The problem is caused by NotifierSettings::resetAutoAction() which removes the mimetype entry from then "m_autoMimetypesMap" map. Consequently ::save() doesn't know the mimetype anymore and does not remove the entry from the config file. Fix: set map entry to 0L -> ::save() removes the entry from config file. Created attachment 21824 [details]
Fix NotifierSettings::resetAutoAction()
This bug is still around in kdelibs-3.5.8-19.fc8. Jan Klötzke's patch seems like an easy fix, could anyone implement it? Link to the Kubuntu bug report: https://bugs.launchpad.net/kdebase/+bug/56043 *** This bug has been confirmed by popular vote. *** This component is gone in KDE4. |