This is old as dirt but if you are still wondering how to accomplish this it should be quite easy. Any DE that uses NetworkManager (Unity, Gnome, KDE, etc.) should be able to connect just fine, you just have to tweak the settings, as NetworkManager unfortunately does not detect them automatically.

The fact that your laptop can't see the network sounds like a different problem, especially if it's an older computer. (May not support 802.11N+, 5Gz, etc.)

Do you have a link to the commit or release notes? This is a fairly common problem and having it documented will be nice for future readers of this post.

Depending on what you are doing with your server you may just want to set selinux to permissive. It can cause a lot of headaches.

These instructions specifically mention Fedora 22. As mentioned above, the current version of fglrx doesn't support 23's newer Xorg. Even if the guide makes it work on newer kernels, you can't force the driver to support Xorg 1.18.

@Florian: I believe it should just be dconf write /org/gnome/nautilus/preferences/default-folder-viewer "'list_view'" (sans sudo) otherwise it would change the setting for the root user. I've been messing around with dconf a lot lately. -_-

If you simply want your card to work, you already have the open source ATI drivers installed as part of Fedora.

However if you are talking about the fglrx proprietary driver...

To put it simply, you can't. Looking at the AMD driver page, the proprietary fglrx driver not only doesn't officially support Fedora, but requires older versions of both X (<=1.17) and the kernel (<=3.19).

There is hope for ATI on Linux in the form of AMDGPU. Essentially, it will take away the headache that new kernel versions cause for ATI users. The official ATI driver will still be proprietary, but there will be an open source component that allows it to interact with the kernel without the pain that fglrx brought us.

Unfortunately, it supports very few cards at the moment and will not support any old cards.

I've had this problem for quite a while with 3.18 and the nVidia driver on Arch Linux also.

How to Change GDM's Sleep Timeout

NOTE: After doing some testing I'm getting rahter inconsistent results. If anyone knows more about how GDM interacts with dconf feel free to chime in. Until then, feel free to try this and report your results.

Searching around, there doesn't seem to be much documentation on how to do this. Anything you do find may refer to gconf, which Gnome has moved away from.

After tinkering with it for an half hour, I seem to have figured it out. The problem with changing settings using Gnome settings or dconf is that it will only change the settings for your user. GDM runs as the "gdm" user, so we have to change these settings for that user.

Instructions

1. Set "sleep-inactive-ac-timeout" to your preferred timeout in seconds. The example below sets the timeout to two minutes.
   sudo -u gdm dbus-launch dconf write /org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-timeout 120

2. Set "sleep-inactive-ac-type" to 'nothing' so your machine doesn't suspend (standby) after the timeout. If you prefer this behavior, omit this command. The double quoting is intentional.
   dbus-launch dconf write /org/gnome/settings-daemon/plugins/power/sleep-inactive-ac-type "'nothing'"'

3. Reboot the system to see the effect. (Make sure all your work is saved)
   sudo reboot

I was going to make a comment regarding that Firefox is using gtk2 and thus a different dialog but apparently Fedora compiles it so it actually uses the gtk3 file picker. Cool.

It appears that the gtk3 filepicker just doen't have that option. There are some real hacky ways to get firefox to use a different dialog but those are beyond my understanding.

However many sites support drag and drop uploading now, meaning you could open Nautilus, switch it to thumbnail view, and simply drag images from there to the site in question.

Upgrading Fedora can often be pretty risky, not to mention doing three upgrades in a row. You got guts.

Personally I would recommend (next time) copying your home directory to a different drive and doing a fresh install, copying back your home in it's entirety or just selectively copying back your configs (such as .mozilla for your Firefox profile).

It's quite possible that some major changes happened to config files in /etc, which dnf would avoid updating. You could also end up with random components missing from your install.

Just make sure that you reply to other answers using comments. It's gets crowded real quick if you don't. ^^

What do you mean by "mac authentication"? Does the AP use a captive portal (requires you to visit a page to login) or use WPA Enterprise (requires you to sign in with domain credentials)? It's possible that Windows has cached said credentials so you don't notice a password prompt.

While this is most likely a software issue, but feel free to share your hardware information by posting the output of lspci and lsusb.

Were you using an Ubuntu live CD? How-To Geek provides a nice article explaining how to do this in detail.

All you would have to do is mount the /home partition (or /root if you don't have a dedicated /home) of the Fedora install in the Ubuntu live enviroment and follow the above instructions. If you are getting errors when trying update your question to include them. It helps a lot!

Also, do these two installations coexist on the same machine?

Is there a specific reason for not preforming a graphical installation? Are you trying to install on a remote computer? Is the graphical environment failing to load? Does your device have an archaic video card?

OR do you want to install a text-only version of Fedora? In that case you want to grab the server version of Fedora available at https://getfedora.org/en/server/ .

Oops, wrong box. Please ignore.

If you are already booting to the desktop without problem, you don't have to do anything. Fedora comes with the Intel display drivers already installed. (Yay open source!)

Are you unable to login? Does Fedora boot to a text-only interface?

Could you perhaps post a screenshot of your current sound settings in Gnome settings? Just to make sure we are all on the same page. Gnome has a built in screenshot tool so you can just search for "Screenshot" in the activity overview.

Looks like 358.16 just hit the nVidia site (with Xorg 1.18 support!). Hopefully we'll see it in RPM Fusion soon.

Thanks for the info. I was having the exact same problem with my GTX660. I tried installing the nvidia driver in the repo at If Not True Then False, but 355.x caused Clutter to crash if I tried doing anything with a window (resize, move, etc). Pretty much every action caused my whole session to crash.

Also, I'd vote you up but this is the first time I've logged into this site. >_<
Update: Got my karma whooo.