Issue 10 in socket-sentry: messagebus error

[socket...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 10 by alekcejk: messagebus error
http://code.google.com/p/socket-sentry/issues/detail?id=10

What steps will reproduce the problem?
1. Install socketsentry
2. Restart service messagebus with 'service messagebus restart' as root

There is error message:

Unknown group "socketsentry" in message bus configuration file

What version of the product are you using? On what operating system?
socketsentry 0.9.2 built on Fedora 12, running in KDE 4.4.1.

Please provide any additional information below.
Fedora 12 RPM can be built using this SRPM
http://nucleo.fedorapeople.org/rpms/socketsentry/

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[socket...@googlecode.com]

Comment #1 on issue 10 by r...@hasselbaum.net: messagebus error
http://code.google.com/p/socket-sentry/issues/detail?id=10

It's not clear to me how this impacts yuou. 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#How_can_I_restrict_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/1ccfbb2202362586
and perhaps try that package to see if it makes a difference.

[socket...@googlecode.com]

Comment #2 on issue 10 by r...@hasselbaum.net: messagebus error
http://code.google.com/p/socket-sentry/issues/detail?id=10

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_getting_a_cryptic_error:_%22Launch_helper_exited_with_un
and

[socket...@googlecode.com]

Comment #3 on issue 10 by r...@hasselbaum.net: messagebus error
http://code.google.com/p/socket-sentry/issues/detail?id=10

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_getting_a_cryptic_error:_%22Launch_helper_exited_with_un
and

http://code.google.com/p/socket-sentry/wiki/FrequentlyAskedQuestions#How_can_I_restrict_access_to_Socket_Sentry_data?

[socket...@googlecode.com]

Comment #4 on issue 10 by alekcejk: messagebus error
http://code.google.com/p/socket-sentry/issues/detail?id=10

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

[socket...@googlecode.com]

Comment #5 on issue 10 by r...@hasselbaum.net: messagebus error
http://code.google.com/p/socket-sentry/issues/detail?id=10

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.

[socket...@googlecode.com]

Comment #6 on issue 10 by alekcejk: messagebus error
http://code.google.com/p/socket-sentry/issues/detail?id=10

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.

[socket...@googlecode.com]

Updates:
Status: WontFix

Comment #7 on issue 10 by r...@hasselbaum.net: messagebus error
http://code.google.com/p/socket-sentry/issues/detail?id=10

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

[socket...@googlecode.com]

Comment #8 on issue 10 by alekcejk: messagebus error
http://code.google.com/p/socket-sentry/issues/detail?id=10

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

[socket...@googlecode.com]

Comment #9 on issue 10 by martosurf7600: messagebus error
http://code.google.com/p/socket-sentry/issues/detail?id=10

Regarding this comment,

Comment 3 by r...@hasselbaum.net, 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_getting_a_cryptic_error:_%22Launch_helper_exited_with_un
and
http://code.google.com/p/socket-sentry/wiki/FrequentlyAskedQuestions#How_can_I_restrict_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!

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--

You received this message because you are subscribed to the Google
Groups "Socket Sentry Admin" group.
To unsubscribe from this group, send email to
socket-sentry-...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/socket-sentry-adm?hl=en