public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jorge Almeida <jjalmeida@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: gnome intrusion?
Date: Mon, 14 Nov 2016 21:49:42 +0000	[thread overview]
Message-ID: <CAKpSnpKJXE8VZ8ThPKBw=UL1gCYPcnmP2gKU=tjSdVmDAk-VUw@mail.gmail.com> (raw)
In-Reply-To: <20161114213743.55a5e76a@jupiter.sol.kaishome.de>

On Mon, Nov 14, 2016 at 8:37 PM, Kai Krakow <hurikhan77@gmail.com> wrote:
> Am Mon, 14 Nov 2016 09:32:59 +0000

>> --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork
>> --print-address 3
>>   417 ?        Sl     0:00 /usr/libexec/at-spi2-registryd

>
> Try uninstalling a a11y related software, disable the accessibility use
> flag... at-spi2 launches its own dbus - it should go away if you
> disable a11y features. Opera triggers starting these through dbus, and
> they will try to bind to Gnome or KDE sessions.
>
> I have these, too, in my systems because some packages unconditionally
> pull in a11y features although I disabled all related useflags.
>
I don't know what a11y is... If you mean nls-related stuff, it is
already off, just like the accessibility USE flag. But
app-accessibility/at-spi2-atk is pulled by gtk+, unconditionally, so
there is nothing I can do about it, I guess. It is not ebuild fault
either, it's an upstream choice.
I also would love to get rid of dbus, but I suppose something
essential would break.

Thanks

Jorge


  reply	other threads:[~2016-11-14 21:50 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14  9:32 [gentoo-user] gnome intrusion? Jorge Almeida
2016-11-14 17:37 ` [gentoo-user] " Ian Zimmerman
2016-11-14 19:03   ` Jorge Almeida
2016-11-14 20:37 ` Kai Krakow
2016-11-14 21:49   ` Jorge Almeida [this message]
2016-11-14 23:51     ` Kai Krakow
2016-11-16 12:47     ` [gentoo-user] sans-dbus was: " Miroslav Rovis
2016-11-16 18:42       ` Jorge Almeida
2016-11-17  1:48         ` Rich Freeman
2016-11-17  7:56           ` [gentoo-user] " Ian Zimmerman
2016-11-17  9:08             ` Rich Freeman
2016-11-19  9:21               ` Kai Krakow
2016-11-19 19:06                 ` Ian Zimmerman
2016-11-19 19:16                   ` Rich Freeman
2016-11-19 20:47                     ` Ian Zimmerman
2016-11-19 21:07                       ` Alan McKinnon
2016-11-19 21:23                         ` Ian Zimmerman
2016-11-19 22:34                           ` Canek Peláez Valdés
2016-11-19 22:36                           ` Alan McKinnon
2016-11-20  0:36                           ` Walter Dnes
2016-11-19 21:59       ` [gentoo-user] " Tom H
2016-11-19 22:15         ` Rich Freeman
2016-11-20 18:40           ` [gentoo-user] " Kai Krakow
2016-11-14 23:38 ` [gentoo-user] " Andrew Tselischev
2016-11-14 23:52   ` Jorge Almeida
2016-11-15 17:39     ` [gentoo-user] " Ian Zimmerman
2016-11-15 19:23       ` Jorge Almeida
2016-11-15 19:32         ` Alan McKinnon
2016-11-15 19:45           ` Jorge Almeida
2016-11-16  2:10     ` [gentoo-user] " Walter Dnes
2016-11-16  7:23       ` Jorge Almeida
2016-11-16  9:08         ` Neil Bothwick
2016-11-16 11:25           ` Jorge Almeida
2016-11-16 20:51             ` [gentoo-user] " Kai Krakow
2016-11-16 21:20               ` Jorge Almeida
2016-11-17 20:42         ` [gentoo-user] " Frank Steinmetzger
2016-11-17 20:49           ` Jorge Almeida
2016-11-17 23:32             ` Frank Steinmetzger
2016-11-14 23:55   ` [gentoo-user] " Kai Krakow

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='CAKpSnpKJXE8VZ8ThPKBw=UL1gCYPcnmP2gKU=tjSdVmDAk-VUw@mail.gmail.com' \
    --to=jjalmeida@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox