Bug 814471
Summary: | [abrt] system-config-samba-1.2.96-1.fc17: connection.py:630:call_blocking:DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | netroby <hufeng1987> | ||||
Component: | system-config-samba | Assignee: | Nils Philippsen <nphilipp> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 17 | CC: | ChugunovYar, donjackson_star, flokip, frank.schletz, jlmeram89, karolis, lovyagin, mbastani_66, mdmpsyd, nphilipp, quentin, rmomota, romanb, rosskitchen, savpether, shnurapet, tom | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | abrt_hash:fc15740ebe882d75044bfb92a6c67ac56df9f5f8 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2013-08-01 05:47:00 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
netroby
2012-04-19 22:36:56 UTC
I just started the application Package: system-config-samba-1.2.96-1.fc16 OS Release: Fedora release 16 (Verne) Opened Samba config Package: system-config-samba-1.2.96-1.fc16 OS Release: Fedora release 16 (Verne) Tried to launch samba config for the first time. Package: system-config-samba-1.2.96-1.fc16 OS Release: Fedora release 16 (Verne) try to start samba-config to check why i can't see shared dirs Package: system-config-samba-1.2.96-1.fc16 OS Release: Fedora release 16 (Verne) Please try this: start the backend mechanism manually (as root), then start the frontend (as a normal user). - as root: "/usr/share/system-config-samba/system-config-samba-mechanism.py" - as normal user: "system-config-samba" Please report back if this works, or if there are any error messages. Thanks. When the two are started separately at least I don't encounter any errors. When the mechanism script is ran as a normal user I complains about not being allowed to own samba service. The bug seems to occur only when system-config-samba is ran as a normal user (In reply to comment #6) > When the two are started separately at least I don't encounter any errors. > When the mechanism script is ran as a normal user I complains about not being > allowed to own samba service. This is expected and normal -- system-config-samba and other similar configuration tools are separated into an unprivileged graphical frontend which runs as the user and a privileged backend ("mechanism" in dbus-lingo) which runs as root and is allowed to (in this case) configure samba, restart the service and so forth. Usually it goes like this: you start the frontend, it connects to the system bus, asks for the backend and the dbus daemon starts the privileged backend -- which should be the same thing if you start the mechanism manually as root... Do you have SELinux enabled/enforcing? Do you get any AVC/audit error messages? Created attachment 583927 [details]
AVC deniel
When set to enforce - there's no indication of a denial however when set to permissive I receive the message in the attachment.
running `setsebool -P authlogin_nsswitch_use_ldap 1` fixes the problem
Package system-config-samba crashes when I start it. I have to downgrade python and python-libs for fix this. I hope you fix this soon and you will understand my description of problem. Package: system-config-samba-1.2.97-1.fc16 OS Release: Fedora release 16 (Verne) Just oppened system-config-samba. It no longer works. Package: system-config-samba-1.2.97-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) After installing samba, and a reboot, I wanted to start samba, then this message occures Package: system-config-samba-1.2.97-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Attempted to run system-config-samba. After several seconds of waiting, before it displayed any form, it terminated. Package: system-config-samba-1.2.97-1.fc16 OS Release: Fedora release 16 (Verne) Just tried to start system-config-samba. Package: system-config-samba-1.2.96-1.fc16 OS Release: Fedora release 16 (Verne) (In reply to comment #9) > Package system-config-samba crashes when I start it. I have to downgrade python > and python-libs for fix this. With which version of python/python-libs do you see the problem and with which not? Don't know. Just installed and tried running for first time. Package: system-config-samba-1.2.97-1.fc16 OS Release: Fedora release 16 (Verne) my samba server doesn't start it shows error in system config Package: system-config-samba-1.2.96-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Starting system-config-samba form menu fallbackmode. Works if started as root. Package: system-config-samba-1.2.97-1.fc16 OS Release: Fedora release 16 (Verne) All works fine after latest actualisation, but SELinux send alert when I start system-config-samba: SELinux is preventing /usr/bin/python2.7 from execute access on the plik /bin/systemd. Komputer NB-Piotr Źródłowe pakiety RPM python-2.7.3-1.fc16.x86_64 Docelowe pakiety RPM systemd-37-19.fc16.x86_64 Pakiet RPM polityki selinux-policy-3.10.0-86.fc16.noarch SELinux jest włączony True This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |