After an update FC9 is mounting CDs again. I checked preferences, set for don't browse and don't play. This has been fixed for years, and now today it has started grabbing the media as soon as the drive is closed.
Can someone tell me what config or prefs file has been "upgraded" this time? When an application changes media and ejects the old, the system grabs the next one faster than the application.
On Tue, 2008-10-21 at 17:39 -0400, Bill Davidsen wrote:
After an update FC9 is mounting CDs again. I checked preferences, set for don't browse and don't play. This has been fixed for years, and now today it has started grabbing the media as soon as the drive is closed.
Can someone tell me what config or prefs file has been "upgraded" this time? When an application changes media and ejects the old, the system grabs the next one faster than the application.
Look at: System->Preferences->Personal->File Management->Media' and see if that helps. -- ======================================================================= If elected, Zippy pledges to each and every American a 55-year-old houseboy ... ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
Aaron Konstam wrote:
On Tue, 2008-10-21 at 17:39 -0400, Bill Davidsen wrote:
After an update FC9 is mounting CDs again. I checked preferences, set for don't browse and don't play. This has been fixed for years, and now today it has started grabbing the media as soon as the drive is closed.
Can someone tell me what config or prefs file has been "upgraded" this time? When an application changes media and ejects the old, the system grabs the next one faster than the application.
Look at: System->Preferences->Personal->File Management->Media' and see if that helps.
That's where I set don't play and don't browse as noted in the original post. I suspect hal or udev type programs, but I don't see any change I think would cause this. I really don't want the media mounted, or even the "blank CD" icon on the desktop, I want the optical devices totally ignored unless I manually mount them or burn to them.
Thanks for the thought, but those settings didn't change.
On Wed, 22 Oct 2008 13:31:19 -0400 Bill Davidsen davidsen@tmr.com wrote:
I really don't want the media mounted, or even the "blank CD" icon on the desktop, I want the optical devices totally ignored unless I manually mount them or burn to them.
Well, my way of avoiding that is to simply not run gnome or kde and not have nautilus (which seems to be the program triggering all this) active. You might try installing gconf-editor and seeing if there are any settings you can see in that to modify nautilus behavior (assuming you are using gnome - I don't know what the equivalent is for kde).
You could also investigate the /etc/hal/fdi/policy/ directory and see about installing some xml magic in there to make hal stop telling nautilus anything happened. This, for instance, is my 10-stop-hal-stop.fdi file:
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2"> <device> <match key="volume.label" string="BACKUP"> <merge key="volume.ignore" type="bool">true</merge> </match> </device> </deviceinfo>
It tells hal not to mention my USB drive with the partition labeled BACKUP, because I don't want it mounted most of the time (I just mount it during backups and keep it nice safe and unmounted at other times :-).
Bill Davidsen wrote:
After an update FC9 is mounting CDs again. I checked preferences, set for don't browse and don't play. This has been fixed for years, and now today it has started grabbing the media as soon as the drive is closed.
Can someone tell me what config or prefs file has been "upgraded" this time? When an application changes media and ejects the old, the system grabs the next one faster than the application.
Is it related to:
https://bugzilla.redhat.com/show_bug.cgi?id=451320
Mogens
Mogens Kjaer wrote:
Bill Davidsen wrote:
After an update FC9 is mounting CDs again. I checked preferences, set for don't browse and don't play. This has been fixed for years, and now today it has started grabbing the media as soon as the drive is closed.
Can someone tell me what config or prefs file has been "upgraded" this time? When an application changes media and ejects the old, the system grabs the next one faster than the application.
Is it related to:
I think only slightly, I really don't want hal or any of his friends to notice or care when optical or USB media are inserted. The best way to prevent incorrect action is to take no action at all.
Tom Horsley wrote:
On Wed, 22 Oct 2008 13:31:19 -0400 Bill Davidsen davidsen@tmr.com wrote:
I really don't want the media mounted, or even the "blank CD" icon on the desktop, I want the optical devices totally ignored unless I manually mount them or burn to them.
Well, my way of avoiding that is to simply not run gnome or kde and not have nautilus (which seems to be the program triggering all this) active. You might try installing gconf-editor and seeing if there are any settings you can see in that to modify nautilus behavior (assuming you are using gnome - I don't know what the equivalent is for kde).
You could also investigate the /etc/hal/fdi/policy/ directory and see about installing some xml magic in there to make hal stop telling nautilus anything happened. This, for instance, is my 10-stop-hal-stop.fdi file:
I think this is neat, and useful, but I kind of want ignore back a level, opening the device enough to look for a volume label is probably enough to mess up the application if it happens at the wrong time.
Thanks for the input, I do find the stanza useful, just not for solving the initial problem.
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2"> <device> <match key="volume.label" string="BACKUP"> <merge key="volume.ignore" type="bool">true</merge> </match> </device> </deviceinfo>
It tells hal not to mention my USB drive with the partition labeled BACKUP, because I don't want it mounted most of the time (I just mount it during backups and keep it nice safe and unmounted at other times :-).
On Thu, 23 Oct 2008 14:39:28 -0400 Bill Davidsen davidsen@tmr.com wrote:
I think this is neat, and useful, but I kind of want ignore back a level, opening the device enough to look for a volume label is probably enough to mess up the application if it happens at the wrong time.
Yea - volume.label is merely one of gazillions of things you can test. No doubt it would also be possible to simply ignore device /dev/sr0 as well (or something like that). Look in /bin or /usr/bin for programs names *hal* - I think there is one out there which will give you a listing of all the hal device attributes and such, and I believe any of them can be tested for in the policy files (but I am by no means any kind of expert - there is a hal mailing list out there where I got help to enable me to construct this specific case).
-
Aaron Konstam -
Bill Davidsen -
Mogens Kjaer -
Tom Horsley