Fedora 13 alpha test results - another one

Adam Williamson awilliam at redhat.com
Fri Mar 19 18:55:41 UTC 2010


On Fri, 2010-03-19 at 12:23 -0500, Jim Haynes wrote:
> I did system->administration->firewall  and got the error message
> 
> org.fedoraproject.slip.dbus.service.PolKit.NotAuthorizedException.org.fedoraproj
> ect.config.firewall.auth
> 
> I have selinux disabled, and the version of system-config-firewall is
> system-config-firewall-1.2.23-1.fc13.noarch

Works fine here. I get a PolicyKit 'enter root password' pop-up.

> Then I tried as root running system-config-firewall at the command line 
> and got the following
> 
> (system-config-firewall:2609): GVFS-RemoteVolumeMonitor-WARNING **: cannot 
> conne
> ct to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive 
> a rep
> ly. Possible causes include: the remote application did not send a reply, 
> the me
> ssage bus security policy blocked the reply, the reply timeout expired, or 
> the n
> etwork connection was broken.
> 
> (system-config-firewall:2609): GVFS-RemoteVolumeMonitor-WARNING **: cannot 
> conne
> ct to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive 
> a rep
> ly. Possible causes include: the remote application did not send a reply, 
> the me
> ssage bus security policy blocked the reply, the reply timeout expired, or 
> the n
> etwork connection was broken.
> 
> (system-config-firewall:2609): GVFS-RemoteVolumeMonitor-WARNING **: cannot 
> conne
> ct to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive 
> a rep
> ly. Possible causes include: the remote application did not send a reply, 
> the me
> ssage bus security policy blocked the reply, the reply timeout expired, or 
> the n
> etwork connection was broken.

Can you check if dbus is actually running? 'ps aux | grep dbus'
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net



More information about the test mailing list