[Mageia-dev] mkinitrd and Mageia2

Fri Jan 27 20:13:27 CET 2012

On 01/27/2012 01:38 PM, Florian Hubold wrote:
+> For reference, with a default setup KDE doesn't automatically mount 
+> removable media like GNOME does, this is the case since quite some 
+> time, IIRC it goes back to 4.0. 
+
+As I said in my initial post about automounting, a week or so ago it was 
+working, and whatever was mounting the disk looked like it was using hal 
+to do it:
+
+Jan 19 16:14:08 localhost halevt: halevt 0.1.6.2, 
+http://www.environnement.ens.fr/perso/dumas/halevt.html
+Jan 19 16:14:08 localhost halevt: No pid file used
+Jan 19 16:14:08 localhost halevt: Running: halevt-mount -u 
+/org/freedesktop/Hal/devices/volume_label_CSI_NY_S6_D4 -o flush
+
+Also, I've been burning ISOs to disk under KDE for months using brasero, 
+and if you loaded a blank disk and did an "OpenWith..." (brasero) on the 
+ISO file before KDE had recognized the blank disk, you got a brasero 
+dialog telling you to mount a blank disk for it; as soon as the blank 
+was detected and the KDE Device popup came up showing it, brasero 
+immediately switched its dialog to ready-to-burn.  Now, it just sits 
+there waiting.
+
+All of this started sometime after Jan19/Jan20, and worked fine prior to 
+that.
+
+But I tend to think you're right about KDE, as I've had 
+https://bugs.kde.org/show_bug.cgi?id=287170 opened for awhile, and that 
+would explain it.  Wine apps can't access unmounted disks, and my Wine 
+apps that use DVDs haven't worked under KDE for a long time.
+
+And then there's the issue that automount had been working in LXDE and 
+stopped working at the same time.  So, it may be that KDE has not been 
+automounting all along, but something else was whether KDE was active or 
+not.
+
+Whatever changed (and *something* did), the effect is that a lot of 
+stuff that was working no longer does, and I wanted to raise the issue 
+while whatever changed might be fresh enough in folks' minds to ring a bell.
+
+