messagebus error about socket-sentry

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It's not clear to me how this impacts you. Are you saying you can't use the 
applet
at all? Or that you get an error only when restarting D-Bus? If it's the 
latter, you
may be able to solve it by creating a "socketsentry" group on your box. See
http://code.google.com/p/socket-sentry/wiki/FrequentlyAskedQuestions#I_am_gettin
g_a_cryptic_error:_%22Launch_helper_exited_with_un
and 
http://code.google.com/p/socket-sentry/wiki/FrequentlyAskedQuestions#How_can_I_r
estrict_access_to_Socket_Sentry_data?
for more information.

Others have reported success with Fedora 12. See
http://groups.google.com/group/socket-sentry/browse_thread/thread/1ccfbb22023625
86
and perhaps try that package to see if it makes a difference.

Original comment by [email protected] on 7 Apr 2010 at 12:20

[GoogleCodeExporter]

Applet works fine in Fedora 12.
But that message should be fixed somehow.
Is creating of socketsentry group the only possible solution?

Original comment by [email protected] on 7 Apr 2010 at 12:44

[GoogleCodeExporter]

Another option is to remove the "socketsentry" group policy from the
"/etc/dbus-1/system.d/org.socketsentry.Watcher.conf" file. That may be a 
workable
solution in your case. However, it won't work for some non-Fedora distros,
particularly if they don't support the "at_console" security policy type. Those 
folks
will need to use the "socketsentry" group (or similar) in order to access the 
service
securely over D-Bus.

The out-of-the-box D-Bus configuration is intended to make Socket Sentry work 
on the
greatest number of distros and provide a default level of security without 
manual
intervention, but it may not be optimal in all cases. I look at this as a 
packaging
issue, though. So my recommendation is to either create the "socketsentry" 
group as
part of your install or remove the group policy from the D-Bus config file. 
Either
approach should prevent the message you see when restarting D-Bus.

Creating the group has some advantages on multiuser systems as explained in the 
FAQ,
so that's something to consider, as well.

Original comment by [email protected] on 7 Apr 2010 at 2:31

[GoogleCodeExporter]

No such problem with messagebus when I installed my rpm and run socketsentry on
Fedora 13 KDE LiveCD. Even without group creation or modification of
org.socketsentry.Watcher.conf.
Don't know why it happens on installed Fedora 12 on hard drive.

Original comment by [email protected] on 7 Apr 2010 at 9:36

[GoogleCodeExporter]

Perhaps the version of D-Bus shipped in Fedora 13 is more forgiving.

Original comment by [email protected] on 7 Apr 2010 at 1:23

• Changed state: WontFix

[GoogleCodeExporter]

dbus-1.2.16 in Fedora 12
dbus-1.2.22 in Fedora 13

Original comment by [email protected] on 7 Apr 2010 at 1:44

[GoogleCodeExporter]

Regarding this comment,

Comment 3  by [email protected], Apr 06, 2010

It's not clear to me how this impacts you. Are you saying you can't use the 
applet
at all? Or that you get an error only when restarting D-Bus? If it's the 
latter, you
may be able to solve it by creating a "socketsentry" group on your box. See
http://code.google.com/p/socket-sentry/wiki/FrequentlyAskedQuestions#I_am_gettin
g_a_cryptic_error:_%22Launch_helper_exited_with_un
and 
http://code.google.com/p/socket-sentry/wiki/FrequentlyAskedQuestions#How_can_I_r
estrict_access_to_Socket_Sentry_data?
for more information.

I only can say THANK YOU VERY MUCH :D
I'm using Arch and after last KDE update I found this error I was able to solve
thanks to your kind help.
Best and thanx a lot for your work!

Original comment by [email protected] on 21 Apr 2010 at 5:45