Found the answer to this conundrum with a little help from the Ubuntu forum but this answer works in Fedora with Gnome, too. Here's my remix of their answer:

To enable or disable automount open a terminal and type dconf-editor followed by the [Enter] key.

Browse to org.gnome.desktop.media-handling. A quick way to do this is to press Ctrl+F (for Find) and then type automount.

The automount key controls whether to automatically mount media. If set to true, then Nautilus will automatically mount media such as user-visible hard disks and removable media on start-up and media insertion. You probably want this on.

There is another key org.gnome.desktop.media-handling.automount-never. By checking this, you will disable Shotwell, and everything else, from running when devices are automounted. So check this to turn Shotwell off.

I installed Fedora 16 today. First problem: System would not boot. I got "No bootable devices found. Insert media and press any key." That turned out to be, because the "old style" DOS partition table didn't have the new partition marked as bootable. Overcoming this took re-booting the Live CD, opening a terminal window, executing the command "su" to become root, then "fdisk /dev/sda" ...ignoring the message about the new GPT partition table type, and using the fdisk command "a" to set sda1 to be bootable (then "w" to write, ignore the error, and reboot). Very sloppy of Fedora to fail to do this. And why do we need a new partition table format at all?

Anyway the next bit that got me stuck was trying to mount an nfs share. The error message says you need to start the "statd" service (see several failed attempts below) but the actual name of the service is rpcbind ...go figure.

# <strong>yum install nfs-utils</strong>
<em>(needed for nfs mount to work at all)</em>
# <strong>mkdir /mnt/home</strong>
# <strong>mount 192.168.1.10:/home /mnt/home</strong>
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified

# <strong>service statd start</strong>
Redirecting to /bin/systemctl  start nfslock.service
Failed to issue method call: Unit nfslock.service failed to load: No such file or directory. See system logs and 'systemctl status nfslock.service' for details.
<em>(It tells you to 'start statd' but there is no statd to start! Ugh.)</em>

# <strong>service nfslock start</strong>
Redirecting to /bin/systemctl  start nfslock.service
Failed to issue method call: Unit nfslock.service failed to load: No such file or directory. See system logs and 'systemctl status nfslock.service' for details.

# <strong>service nfs start</strong>
Redirecting to /bin/systemctl  start nfs.service
Failed to issue method call: Unit nfs.service failed to load: No such file or directory. See system logs and 'systemctl status nfs.service' for details.

# <strong>service rpcbind start</strong>
Redirecting to /bin/systemctl  start rpcbind.service
<em>(( Success! ))</em>
# <strong>mount 192.168.1.10:/home /mnt/home</strong>
<em>(( Success! ))</em>
#

For some reason, on Fedora 15, CUPS wasn't starting on bootup. Print jobs were just being silently dropped. I tried this:

$ **lpq** lpq: Unable to connect to server.

Hmm... That's not right.

$ **sudo service cups start** Redirecting to /bin/systemctl start cups.service

Oh... they changed the administration command for some reason. I couldn't find anywhere in the menus (or the discombubulated, disorganized mess that substitutes for menus in Gnome 3) a GUI for selecting startup services. Didn't we have that back in RedHat 4? Anyway... a little digging uncovers that the simple service command, inexplicably, has been replaced by the more jargon-laden systemctl command, so the 'new' way is now:

$ **sudo systemctl start cups.service**

OK that got it going. lpq sees CUPS and print jobs actually print. Now to change it permanently:

$ <strong>sudo chkconfig --list</strong>

Note: This output shows SysV services only and does not include native
systemd services. SysV configuration data might be overridden by native
systemd configuration.

iscsi 0:off 1:off 2:off 3:on 4:on 5:on 6:off
iscsid 0:off 1:off 2:off 3:on 4:on 5:on 6:off
livesys 0:off 1:off 2:off 3:on 4:on 5:on 6:off
livesys-late 0:off 1:off 2:off 3:on 4:on 5:on 6:off
netconsole 0:off 1:off 2:off 3:off 4:off 5:off 6:off
netfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off
network 0:off 1:off 2:off 3:off 4:off 5:off 6:off
sandbox 0:off 1:off 2:off 3:off 4:off 5:on 6:off
svnserve 0:off 1:off 2:off 3:off 4:off 5:off 6:off

Another frustration. This functionality is now rolled into the systemctl command. Perhaps that's nicer, but where's the GUI interface for this? I guess I could use webmin, but gosh it seems Gnome should have one.

Here's what it reports:

$ **systemctl status cups.service** cups.service - CUPS Printing Service Loaded: loaded (/lib/systemd/system/cups.service; disabled) Active: active (running) since Thu, 20 Oct 2011 08:19:58 -0700; 7min ago Main PID: 16104 (cupsd) CGroup: name=systemd:/system/cups.service └ 16104 /usr/sbin/cupsd -f

OK, it's disabled at startup. here goes:

$ **sudo systemctl enable cups.service** ln -s '/lib/systemd/system/cups.service' '/etc/systemd/system/printer.target.wants/cups.service' ln -s '/lib/systemd/system/cups.socket' '/etc/systemd/system/sockets.target.wants/cups.socket' ln -s '/lib/systemd/system/cups.path' '/etc/systemd/system/multi-user.target.wants/cups.path' $

Ah, there we go.

Please, Fedora and Gnome -- where's the GUI administration tools for this?

I had already downloaded and installed Flash for Firefox, following these instructions but could not get it to work as a plugin on Chromium.

Success is yours when you type "about:plugins" into the location bar of Chromium and the Flash player appears.

Fortunately, it turned out to be pretty simple to just link Firefox's plugin into Chromium: As root, do this:

cd /usr/lib64/chromium-browser/plugins/
ln -s /usr/lib64/mozilla/plugins-wrapped/nswrapper_32_64.libflashplayer.so .