All of lore.kernel.org
 help / color / mirror / Atom feed
From: justinmattock@gmail.com (Justin P. Mattock)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] bluetooth-applet not showing up in the panel
Date: Tue, 28 Dec 2010 12:09:33 -0800	[thread overview]
Message-ID: <4D1A43FD.6080801@gmail.com> (raw)
In-Reply-To: <4D1A391C.2030206@giz-works.com>

On 12/28/2010 11:23 AM, Chris Richards wrote:
> On 12/28/2010 10:39 AM, Dominick Grift wrote:
>>> yeah nothing is showing up in the logs i.g.
>>> /var/log/Xorg,messages,user.log, etc...(no audit daemon running), and
>>> semodule -DB has already been done)
>> strange indeed becuase if it works in permissive mode but not in
>> enforcing mode then i would suspect its selinux preventing access. In
>> that case avc denials *should* be visible. either in dmesg ,
>> /var/log/messages /var/log/xorg.log /var/log/audit/audit.log etc.
> It might be instructive to see if there are any denials when running in
> permissive mode.  I've encountered situations in the past where no
> denials would be reported when running enforcing (even with semodule
> -DB, other than the expected dontaudits, of course), yet when running in
> permissive mode, there would be denials out the wazzoo, even with apps
> that were supposedly not selinux-aware.
>
> Later,
> Chris
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy
>


yeah those avc's can be little buggers if hidden away in some file 
somewhere..I'll have a look again to make sure.. in the meantime
I am noticing in .xsession-errors in enforcing mode:


  cat .xsession-errors
/etc/gnome/gdm/Xsession: Beginning session setup...
/etc/gnome/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- 
ck-launch-session /usr/bin/startfluxbox

** (bluetooth-applet:2786): WARNING **: Could not open RFKILL control 
device, please verify your installation
GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings 
will not be saved or shared with other applications.
tint2 : nb monitor 1, nb monitor used 1, nb desktop 4
tint2 : pixmap background detection failed
Error changing to home directory /root: Permission denied
Error changing to home directory /root: Permission denied
Error changing to home directory /root: Permission denied


the: Error changing to home directory /root: Permission denied
does not occur in permissive mode so maybe this is whats hitting and 
causing the stuckage or something.. I'll need to look again at 
everything to make sure I didnt forget a build flag or something

Justin P. Mattock

  reply	other threads:[~2010-12-28 20:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-28 14:50 [refpolicy] bluetooth-applet not showing up in the panel Justin Mattock
2010-12-28 14:59 ` Dominick Grift
2010-12-28 15:34   ` Justin P. Mattock
2010-12-28 15:40     ` Dominick Grift
2010-12-28 16:35       ` Justin P. Mattock
2010-12-28 16:39         ` Dominick Grift
2010-12-28 17:02           ` Justin P. Mattock
2010-12-28 19:23           ` Chris Richards
2010-12-28 20:09             ` Justin P. Mattock [this message]
2010-12-31 10:28               ` Daniel J Walsh
2011-01-04  1:29                 ` Justin P. Mattock
2011-01-04 14:06                   ` Daniel J Walsh
2011-01-04 14:36                     ` Justin P. Mattock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D1A43FD.6080801@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=refpolicy@oss.tresys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.