Bug 8381 - KDE Automount borked
Summary: KDE Automount borked
Status: RESOLVED DUPLICATE of bug 8393
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 8393
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-13 15:28 CET by Frank Griffin
Modified: 2013-01-01 18:13 CET (History)
3 users (show)

See Also:
Source RPM: kde
CVE:
Status comment:


Attachments

Description Frank Griffin 2012-12-13 15:28:30 CET
In current cauldron, KDE itself is able to detect an inserted DVD (populated or blank), but in spite of Removable Media settings that say automount everything, it does not.

This has been happening for quite awhile, and is known (and ignored) upstream, but it has suddenly gotten worse.  It used to be that by going to the device notifications and choosing an action for the DVD that required KDE to mount it, e. g. Open with File Manager, you could force the mount, and then other non-KDE apps like wine or brasero could use it.  That is no longer the case.  The DVD gets mounted under /run/media/(userid), but no app can see it.

Maybe this has something to do with the change of mounting under /media to the current setup.

If instead of KDE you log into GNOME Classic, the apps work just fine, so this is not the kernel and it's not any DE-agnostic device handling.

To reproduce, insert a blank DVD, wait until KDE recognizes it, open Dolphin, right-click on an ISO file and choose Open With Brasero.  Brasero will not detect the available blank DVD.  You can eject and reload it, and Brasero still won't detect it.  I've only tried the populated case with a wine DVD app (DVDFab), but it should be reproducible by running wineconsole and finding that the inserted DVD is not available at any drive letter.
Comment 1 Pierre Jarillon 2012-12-28 18:09:37 CET
I have the same problem,  The CD or DVD is inserted, seen by KDE in the systray but I seems to have no mounting point...
The problem is true also with a USB memory key.
I have no file or directory in /run/media/

See also https://bugs.mageia.org/show_bug.cgi?id=8533
See other bugs with the keyword "mount" or core media, it is a big problem!

CC: (none) => jarillon

Comment 2 Manuel Hiebel 2012-12-28 18:13:22 CET
not related to bug 8393 ?
Comment 3 Frank Griffin 2012-12-28 18:15:34 CET
(In reply to comment #2)
> not related to bug 8393 ?

Probably.
Comment 4 Manuel Hiebel 2012-12-28 19:06:20 CET
ok personnaly I'm not sure so adding a dependency

Reporter, could you please reply to the previous question? If you don't reply within two weeks from now, I will have to close this bug as OLD. Thank you.

Keywords: (none) => NEEDINFO
Depends on: (none) => 8393

Comment 5 Manuel Hiebel 2012-12-28 19:07:08 CET
oups sorry for the second sentence, script works to much sometimes

Keywords: NEEDINFO => (none)

Comment 6 Frank Griffin 2012-12-28 19:21:46 CET
I'm no dbus expert, so I'm not sure what effect this had, or whether the wind's just blowing the right way, but I applied the workaraound mentioned in the upstream link from bug#8393 (copying all of the <limit> tags from /etc/dus-1/session.conf to system.conf) and without a reboot and without restarting KDE suddenly automount works for both burned and blank disks.
Comment 7 Barry Jackson 2012-12-28 21:07:48 CET
(In reply to comment #6)
Following on from your experiment I read the comment at the top of system.conf :

<!-- This configuration file controls the systemwide message bus.
     Add a system-local.conf and edit that rather than changing this 
     file directly. -->

So I created /etc/dbus-1/system-local.conf and copied the limits there.

It failed. 

However, moving the new file into /etc/dbus-1/system.d works OK.

CC: (none) => zen25000

Comment 8 Frank Griffin 2012-12-29 19:45:39 CET
Interesting.  I actually misread that and put them in a "system.local.conf" rather than system-local.conf.  So I guess mine was just working by accident.  

What, if anything, did you need to do to get dbus to notice the change ?
Comment 9 André DESMOTTES 2012-12-31 15:05:51 CET
hello,
I had the same problem, I followed the comment #6, without improvement, then comment #7 and it works.
KDE 64 bits on a laptop Dell Latitude D630.

CC: (none) => lebarhon

Comment 10 Manuel Hiebel 2013-01-01 18:13:25 CET
ok so it confirm it's a dup (in some way)

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

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


Note You need to log in before you can comment on or make changes to this bug.