Description of problem: system-config-samba-1.2.83-1.fc12.noarch Version-Release number of selected component (if applicable): system-config-samba-1.2.83-1.fc12.noarch How reproducible: always Steps to Reproduce: 1. System -> Samba - 2. root password 3. try to add samba user Actual results: [floki@flokipal ~]$ system-config-samba Traceback (most recent call last): File "/usr/share/system-config-samba/addUserWin.py", line 174, in on_add_user_ok_button_clicked elif self.samba_backend.userExists(unix_name): File "/usr/lib/python2.6/site-packages/scsamba/dbus/proxy/sambaBackend.py", line 88, in userExists return self.dbus_interface.userExists (user) File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__ **keywords) File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [floki@flokipal ~]$ rpm -q system-config-samba system-config-samba-1.2.83-1.fc12.noarch Expected results: new samba suser Additional info: It works when s-c-f is started from terminal as root [root@flokipal ~]# system-config-samba Added user floki. You have mail in /var/spool/mail/root [root@flokipal ~]#
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I could reproduce this with old SELinux policy. Please verify whether you see this problem with selinux-policy-targeted-3.6.32-59.fc12 or later.
Comment #2 >I could reproduce this with old SELinux policy. Please verify whether you see >this problem with selinux-policy-targeted-3.6.32-59.fc12 or later. These is still abrt crash after updating with yum --enablerepo=updates-testing update selinux-policy-\* policycoreutils\* when adding sambauser and abrt points to see Bug 523863 [abrt] crash detected in system-config-samba-1.2.82-1.fc12 (edit) from yum.log Dec 31 12:43:08 Updated: selinux-policy-3.6.32-63.fc12.noarch Dec 31 12:43:54 Updated: selinux-policy-targeted-3.6.32-63.fc12.noarch [floki@flokipa ~]$ rpm -q system-config-samba system-config-samba-1.2.83-1.fc12.noarch ---------------------------- from terminal floki@flokipa ~]$ system-config-samba Traceback (most recent call last): File "/usr/share/system-config-samba/addUserWin.py", line 174, in on_add_user_ok_button_clicked elif self.samba_backend.userExists(unix_name): File "/usr/lib/python2.6/site-packages/scsamba/dbus/proxy/sambaBackend.py", line 88, in userExists return self.dbus_interface.userExists (user) File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__ **keywords) File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Killed [floki@flokipa ~]$ --------------------------------------- Before updating with yum --enablerepo=updates-testing update selinux-policy-\* policycoreutils\* adding user in system-config-samba [floki@flokipa ~]$ rpm -q selinux-policy-targeted selinux-policy-targeted-3.6.32-59.fc12.noarch UUID: 08997608 architecture: x86_64 cmdline: /usr/bin/python /usr/bin/system-config-samba component: system-config-samba executable: /usr/bin/system-config-samba kernel: 2.6.31.9-174.fc12.x86_64 package: system-config-samba-1.2.83-1.fc12 release: Fedora release 12 (Constantine) uuid: 08997608 backtrace ----- Summary: TB08997608 connection.py:630:call_blocking:DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Traceback (most recent call last): File "/usr/share/system-config-samba/addUserWin.py", line 174, in on_add_user_ok_button_clicked elif self.samba_backend.userExists(unix_name): File "/usr/lib/python2.6/site-packages/scsamba/dbus/proxy/sambaBackend.py", line 88, in userExists return self.dbus_interface.userExists (user) File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__ **keywords) File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking message, timeout) DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Local variables in innermost frame: byte_arrays: False self: <dbus._dbus.SystemBus (system) at 0x2bf3ef0> args: ('floki',) utf8_strings: False bus_name: :1.69 get_args_opts: {'byte_arrays': False, 'utf8_strings': False} object_path: /org/fedoraproject/Config/Samba/Backend timeout: -1.0 signature: s dbus_interface: org.fedoraproject.Config.Samba.Backend message: <dbus.lowlevel.MethodCallMessage object at 0x296f780> method: userExists
For me this is same like in bug 533743.
(In reply to comment #4) > For me this is same like in bug 533743. Agreed. *** This bug has been marked as a duplicate of bug 533743 ***