abrt 1.0.0 detected a crash. backtrace ----- Summary: TB08997608 connection.py:630:call_blocking:DBusException: org.fedoraproject.slip.dbus.service.PolKit.NotAuthorizedException.org.fedoraproject.config.services.manage: Traceback (most recent call last): File "/usr/bin/system-config-services", line 873, in on_serviceEnable_activate service.enable() File "/usr/lib/python2.6/site-packages/scservices/dbus/proxy/services.py", line 77, in enable return self.chkconfig_interface.enable() File "/usr/lib/python2.6/site-packages/slip/dbus/proxies.py", line 49, in __call__ return dbus.proxies._ProxyMethod.__call__(self, *args, **kwargs) 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.fedoraproject.slip.dbus.service.PolKit.NotAuthorizedException.org.fedoraproject.config.services.manage: Local variables in innermost frame: byte_arrays: False self: <dbus._dbus.SystemBus (system) at 0x999441c> args: () utf8_strings: False bus_name: :1.173 get_args_opts: {'byte_arrays': False, 'utf8_strings': False} object_path: /org/fedoraproject/Config/Services/ServiceHerders/SysVServiceHerder/Services/avahi_daemon timeout: 2147483 signature: dbus_interface: org.fedoraproject.Config.Services.ChkconfigService message: <dbus.lowlevel.MethodCallMessage object at 0x983d580> method: enable cmdline: /usr/bin/python /usr/bin/system-config-services component: system-config-services executable: /usr/bin/system-config-services kernel: 2.6.31.6-145.fc12.i686 package: system-config-services-0.99.41-1.fc12 uuid: 08997608
Created attachment 375510 [details] File: backtrace
Same problem here on x86-64.
Same for me.
same here. No root authentication was asked
(In reply to comment #4) > same here. No root authentication was asked Your problem is a different one. This bug is about e.g. handling cancelled password dialogs. Please file a bug with a detailed description what you did and what happened. Thanks.
could be, abrt pointed me to this bug report as duplicate. In my case not a cancelled password dialog, but nog dialog at all
(In reply to comment #6) > could be, abrt pointed me to this bug report as duplicate. In my case not a > cancelled password dialog, but nog dialog at all This also happened for me: no dialog at all. BTW system-config-services is now working for me since one of the last updates...
(In reply to comment #6) > could be, abrt pointed me to this bug report as duplicate. In my case not a > cancelled password dialog, but nog dialog at all Could be. Unfortunately abrt's duplicate detection bites us here -- the frontend can't distinguish between cancelled password dialogs and other problems so abrt thinks it's the same issue.
If there is no password dialog at all, do you use compiz? Here the password window always appears behind all other windows, so you can overlook the dialog easily. I searched for this bug, but couldn'd find any. Maybe you have the same problem?
I use freenx. I do not see the dialog behind other windows. The problem remains running latest updates. Other system-config-tools are hit by the problem too. I have some other crashes that are related to nx server not supporting xrandr.
I have just re-installed Fedora 12, ran a yum update, and system-config-services crashed when I tried to run it from System -> Administration. As Reinier and David said, I too did not get any password dialog box. That doesn't mean that it wasn't _trying_ to load it, but the application crashed.
(In reply to comment #11) > I have just re-installed Fedora 12, ran a yum update, and > system-config-services crashed when I tried to run it from System -> > Administration. As Reinier and David said, I too did not get any password > dialog box. That doesn't mean that it wasn't _trying_ to load it, but the > application crashed. After restarting the computer, the services application functioned properly.
*** Bug 567770 has been marked as a duplicate of this bug. ***
Comment ----- I was just testing basic functions - starting and stopping services. It did seem to work okay, but also threw this exception.
To give a more clear explanation since this one seems to be tricky: I'm on F13. Doing easy-karma, this update showed up in the list, so I went to test the app. I ran it, picked a service to try and stop (NetworkManager), hit Stop, and it prompted for root password. I realized I didn't really want to stop NM, so hit Cancel. Then I picked a different service (acpid), hit stop, entered the root password, and it stopped. Hit start, and it started. At some point in the above process, the abrt alert showed up; I can't say exactly when. s-c-s did not actually crash or behave in any unexpected way at any point. It may have been when I hit Cancel on the authentication dialog for stopping NM?
(In reply to comment #15) > At some point in the above process, the abrt alert showed up; I can't say > exactly when. s-c-s did not actually crash or behave in any unexpected way at > any point. It may have been when I hit Cancel on the authentication dialog for > stopping NM? Very likely. I'm busy with other stuff so making this more cosmetically appealing isn't right on the top of my todo list... I think this should be caught in the python-slip dbus/polkit wrappers, but would need API amendments: it should eat the exception and return a value that signifies "failure" (or alternatively throws a custom "auth failed" exception that is caught by the GUI), and should let users of the API specify what exactly shall be returned/thrown in that case. The polkit.enable_proxy decorator doesn't accept parameters right now and adding that possibility without breaking existing apps isn't exactly trivial.
system-config-services-0.99.43-1.fc12,python-slip-0.2.8-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/system-config-services-0.99.43-1.fc12,python-slip-0.2.8-1.fc12
system-config-services-0.99.43-1.fc13,python-slip-0.2.8-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/system-config-services-0.99.43-1.fc13,python-slip-0.2.8-1.fc13
Looks good. First I confirmed it was indeed after I hit Cancel that it threw the exception. Then I updated to the newer packages in comment #18 and re-tested; no abrt icon. Thanks. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Comment ----- I tried to restart xinet.d service
system-config-services-0.99.43-1.fc12, python-slip-0.2.8-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update system-config-services python-slip'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/system-config-services-0.99.43-1.fc12,python-slip-0.2.8-1.fc12
Comment ----- It happens casually: sometimes when starting a service, sometimes when trying to restart it (the service was libvirtd).
Updated as suggested in comment #18 or #21 Thank You
How to reproduce ----- 1.start s-c-s from command line as normal user 2. 3.
can people who are reporting this now please try the candidate update? as I said, it fixes the problem fine for me. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
system-config-services-0.99.43-1.fc13, python-slip-0.2.8-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
system-config-services-0.99.43-1.fc12, python-slip-0.2.8-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.