You'd think it wouldn't be related to the nvidia driver... but it definitely is.
At System76, we've frequently encountered scattered problems like this. The nvidia proprietary effects the boot sequence enough (for example, no kms) that it frequently exposes subtle problems in the overall structure of the upstart jobs, usually related to timing issues. My hunch is some upstart job actually should depend on an event that it doesn't, but without the nvidia proprietary driver installed, this job works correctly by chance because this event will usually have already happened. This might not be a network-manager problem, but that's where the symptom is occurring. My current hunch is this might be related to nvidia-persistenced being started via udev in Utopic, vs Upstart in Trusty and older. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1388130 Title: Cannot connect to WiFi with Nvidia GPU using nvidia-331, SSD Status in System76: Triaged Status in “network-manager” package in Ubuntu: Confirmed Bug description: For some strange reason, we cannot connect to WiFi on hardware with a descrete Nvidia GPU (using the nvidia-331 driver) when the system is running off a fast SSD. Swap the SSD for a platter drive, and things work fine. Likewise, on Intel GPU systems, with either an SSD or a platter drive, WiFi works fine. The failure message is: """ Connection activation failed. (1) Creation of object for path '/org/freedesktop/NetworkManager/ActiveConnection/2' failed in libnm-glib """ See the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu28 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 31 08:58:25 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.17.76.1 dev eth0 proto static 10.17.76.0/24 dev eth0 proto kernel scope link src 10.17.76.193 metric 1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH system76_5g d7cafbd5-f1ef-422d-9ed4-4b3a9095b234 802-11-wireless 0 never yes no /org/freedesktop/NetworkManager/Settings/1 Wired connection 1 c52af28c-07c5-4140-bf2c-3f0d236a05fc 802-3-ethernet 1414767492 Fri 31 Oct 2014 08:58:12 AM MDT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8 connected enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1388130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
