Bug 568345 - [abrt] crash in system-config-samba-1.2.83-1.fc12
Summary: [abrt] crash in system-config-samba-1.2.83-1.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 533743
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-samba
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ae71caa4
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-25 14:32 UTC by luka
Modified: 2010-03-07 09:52 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-26 10:16:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.55 KB, text/plain)
2010-02-25 14:32 UTC, luka
no flags Details

Description luka 2010-02-25 14:32:16 UTC
abrt 1.0.7 detected a crash.

architecture: i686
cmdline: /usr/bin/python /usr/bin/system-config-samba
component: system-config-samba
executable: /usr/bin/system-config-samba
kernel: 2.6.31.12-174.2.22.fc12.i686
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 0x9c8e92c>
args: ('abrt',)
utf8_strings: False
bus_name: dbus.UTF8String(':1.160')
get_args_opts: {'byte_arrays': False, 'utf8_strings': False}
object_path: '/org/fedoraproject/Config/Samba/Backend'
timeout: -1.0
signature: u's'
dbus_interface: 'org.fedoraproject.Config.Samba.Backend'
message: <dbus.lowlevel.MethodCallMessage object at 0x9aa45d0>
method: 'userExists'

Comment 1 luka 2010-02-25 14:32:19 UTC
Created attachment 396278 [details]
File: backtrace

Comment 2 Nils Philippsen 2010-02-26 10:16:01 UTC

*** This bug has been marked as a duplicate of bug 533743 ***


Note You need to log in before you can comment on or make changes to this bug.