I haven't tried anything really hard, but it has all gone fine for me with no unexpected problems.
The expected problems are, as usual have to install kudzu to get dialup networking to work have to remove a whole bunch of unwanted language fonts updating via yum update is froggy, but I guess that is understandable considering the number of unresolved dependency problems have to install control-center-extra package to get mouse cursor focus the way I like it.
jhhaynes at earthlink dot net
On Mon, 2010-03-15 at 15:12 -0500, Jim Haynes wrote:
I haven't tried anything really hard, but it has all gone fine for me with no unexpected problems.
The expected problems are, as usual have to install kudzu to get dialup networking to work
Could I possibly ask you to file a bug for this one and throw it on the F13Beta blocker list? I'm scared we'll keep forgetting this one and not get it fixed for final. thanks.
On Mon, 2010-03-15 at 15:12 -0500, Jim Haynes wrote:
I haven't tried anything really hard, but it has all gone fine for me with no unexpected problems.
The expected problems are, as usual have to install kudzu to get dialup networking to work
Greetings Jim, looks like a fix for the bug you filed (bug#573868) is available. Do you still see this issue if using the updated system-config-network? Feel free to add feedback to the update at http://admin.fedoraproject.org/updates/system-config-network-1.6.0-2.fc13
Thanks, James
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
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.
I'm trying to learn how to do the right thing, but when I tried to search in bugzilla.redhat system-config-firewall was not among the list of system-config things listed under Component:
OK, I submitted bug 575191
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'
On Fri, 19 Mar 2010, Adam Williamson wrote:
Can you check if dbus is actually running? 'ps aux | grep dbus'
1046 ? Ss 0:01 dbus-daemon --system 1435 ? S 0:00 /usr/bin/dbus-launch --exit-with-session 1555 ? S 0:00 dbus-launch --sh-syntax --exit-with-session 1556 ? Ss 0:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session 2015 pts/0 S+ 0:00 grep dbus
PolicyKit - things get more and more complicated - I never had to deal with it before. Just tried it on my working F12 system and it asked for the root password, but if I cancelled that then I got the same message that I get on F13A all the time.
On Fri, 2010-03-19 at 15:59 -0500, Jim Haynes wrote:
On Fri, 19 Mar 2010, Adam Williamson wrote:
Can you check if dbus is actually running? 'ps aux | grep dbus'
1046 ? Ss 0:01 dbus-daemon --system 1435 ? S 0:00 /usr/bin/dbus-launch --exit-with-session 1555 ? S 0:00 dbus-launch --sh-syntax --exit-with-session 1556 ? Ss 0:00 /bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session 2015 pts/0 S+ 0:00 grep dbus
PolicyKit - things get more and more complicated - I never had to deal with it before. Just tried it on my working F12 system and it asked for the root password, but if I cancelled that then I got the same message that I get on F13A all the time.
right, which indicates that somehow the policykit auth mechanism isn't working on your f13 setup. But like I say, it works fine here.
Is this KDE or GNOME?