Bug 1066781

Summary: NetworkManager does not allow gdm to send messages via dbus
Product: [Fedora] Fedora Reporter: Edgar Hoch <edgar.hoch>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dcbw, jklimes
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 15:18:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Output of "journalctl -e" (hostname replaced), 10 minutes none

Description Edgar Hoch 2014-02-19 05:49:28 UTC
Created attachment 864969 [details]
Output of "journalctl -e" (hostname replaced), 10 minutes

Description of problem:
On a fresh Fedora 20 installation, gdm wants to communicate with NetworkManager via dbus but gdm is not allowed to send these messages.


Version-Release number of selected component (if applicable):
gdm-3.10.0.1-1.fc20.x86_64
NetworkManager-0.9.9.0-28.git20131003.fc20.x86_64
systemd-208-14.fc20.x86_64
kernel-3.13.3-201.fc20.x86_64
dbus-1.6.12-8.fc20.x86_64
gnome-shell-3.10.3-6.fc20.x86_64


How reproducible:
Always.

Steps to Reproduce:
1. Install a fresh Fedora 20 system with gdm and NetworkManager.
   You may use the kickstart file as in bug #1051816:
   https://bugzilla.redhat.com/attachment.cgi?id=849855
2. Check the output of "journalctl -e".


Actual results:
Error messages like those listed in the attachement.

Expected results:
No error messages.

Comment 1 Edgar Hoch 2014-02-19 16:13:27 UTC
I found that the problem exists on Fedora 19 too. I have checked a Fedora 19 machine with the following packages. "journalctl -e" lists similar messages.

gdm-3.8.4-2.fc19.x86_64
NetworkManager-0.9.8.8-2.fc19.x86_64
systemd-204-18.fc19.x86_64
kernel-3.12.11-201.fc19.x86_64
dbus-1.6.12-2.fc19.x86_64
gnome-shell-3.8.4-3.fc19.x86_64

Comment 2 Jirka Klimes 2014-04-24 14:46:04 UTC
This seems to me like a problem with policies in dbus or systemd.
It may be duplicate of bug 809214.

Comment 3 Fedora End Of Life 2015-05-29 10:58:34 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-06-29 15:18:21 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.