Red Hat Bugzilla – Bug 809123
Unable to login to desktop after upgrading to NM-0.9.4-1.git20120328.fc16
Last modified: 2013-09-02 03:01:58 EDT
Description of problem:
After upgrading to NetworkManager-0.9.4-1.git20120328.fc16.x86_64, it seems I am unable to login. The gnome-shell presents the startup-failure screen.
When downgrading to NetworkManager-0.9.2-1.fc16, the problem goes away.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Manually configure a Network bridge following instructions from libvirt.org
> /etc/sysconfig/network-scripts/ifcfg-em1 has NM_CONTROLLED=no
> /etc/sysconfig/network-scripts/ifcfg-br0 also has NM_CONTROLLED=no
2. Upgrade to latest NM from 'updates-testing'
3. Login to desktop
* Gnome shell fails to start
* After upgrading NM, the desktop should start without error
* See libnm-glib backtrace in attachment#574498 [details]
Upstream fix: 8bb278944496102a4afad46b53e1e8279425aaac
(In reply to comment #1)
> Upstream fix: 8bb278944496102a4afad46b53e1e8279425aaac
I'm unable to reproduce the reported problem when testing using a provided scratch build (http://koji.fedoraproject.org/koji/taskinfo?taskID=3956993)
NetworkManager-0.9.4-2.git20120403.fc16 has been submitted as an update for Fedora 16.
NetworkManager-0.9.4-3.git20120403.fc17 has been submitted as an update for Fedora 17.
*** Bug 808152 has been marked as a duplicate of this bug. ***
*** Bug 809215 has been marked as a duplicate of this bug. ***
I was triggering it with NetworkManager enabled - as the install was done through HTTP. I hadn't done anything special to the network interface.
systemctl tells me:
NetworkManager.service loaded active running Network Manager
The /etc/sysconfig/network-scripts/ifcfg-eth0 tells me:
[root@f17 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
I had download the NetworkManager-0.9.4-3.git20120403.fc17 and I am still hitting this. rpm -qa | grep NetworkManager tells me:
[root@f17 ~]# rpm -qa | grep Network
And it here is something more strange:
root@f17 ~]# nmcli nm
RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running connected enabled enabled enabled disabled
[root@f17 ~]# su - konrad
[konrad@f17 ~]$ nmcli nm
** (process:3305): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Rejected send message, 3 matched rules; type="method_call", sender=":1.53" (uid=1000 pid=3305 comm="nmcli nm ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=443 comm="/usr/sbin/NetworkManager --no-daemon ")
Error: nmcli (0.9.4.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable.
[root@f17 ~]# rpm -qf `which nmcli`
[root@f17 ~]# ps -eff|grep Network
root 443 1 0 09:02 ? 00:00:00 /usr/sbin/NetworkManager --no-daemon
root 3313 3183 0 10:44 hvc0 00:00:00 grep --color=auto Network
[root@f17 ~]# rpm -qf `which NetworkManager`
I'd say that there can be some problem with D-Bus or PolicyKit causing the rejected messages.
But the crash of /usr/bin/gnome-shell in libnm-glib should be fixed.
Try to obtain some logs to found out what's the problem (~/.xsession-errors, /var/log/messages)
Uninstalling fprintd (and fprintd-pam) fixed it.
*** Bug 810053 has been marked as a duplicate of this bug. ***
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing NetworkManager-0.9.4-3.git20120403.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Nominating this as a Beta NTH so we can discuss whether to pull it into RC4. My best guess as to the circumstance that produces this bug is running Shell with the NetworkManager service disabled, though I couldn't reproduce it that simply when I tried in a VM.
Fedora Bugzappers volunteer triage team
Discussed at 2012-04-09 blocker review meeting. We agreed this is rejected as NTH as the trigger - disabling NM - is not something anyone's likely to do on a live image, so fixing this with an update should be good enough.
Fedora Bugzappers volunteer triage team
correction - 2012-04-06 NTH review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-04-06/f17-beta-blocker-review-5.2012-04-06-17.01.log.html
NetworkManager-0.9.4-2.git20120403.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
NetworkManager-0.9.4-5.git20120403.fc17 has been submitted as an update for Fedora 17.
NetworkManager-0.9.4.0-6.git20120403.fc17 has been submitted as an update for Fedora 17.
NetworkManager-0.9.4.0-7.git20120403.fc17 has been submitted as an update for Fedora 17.
NetworkManager-0.9.4.0-7.git20120403.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.