View previous topic :: View next topic |
Author |
Message |
Fran Guru
Joined: 29 Feb 2004 Posts: 530 Location: Coruña (Spain)
|
Posted: Sun Jan 06, 2013 4:15 pm Post subject: gtk3 programs leave a11y daemon running after exit [SOLVED] |
|
|
I'm quite happy with my minimal system, in which I can recognize every process I see in htop because *I* launched them.
Well, not every one. Whenever I launch a gtk+-3.6 application I see 3 new processes that remain even after I exit that application:
Code: | fran 30332 0.0 0.0 258920 2800 ? Sl 16:41 0:00 /usr/libexec/at-spi-bus-launcher
fran 30335 0.0 0.0 19492 1392 ? S 16:41 0:00 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
fran 30338 0.0 0.0 120368 3208 ? Sl 16:41 0:00 /usr/libexec/at-spi2-registryd --use-gnome-session |
Huh? Are these REALLY needed for any gtk3 application? I've tried removing /usr/share/dbus-1/services/org.a11y.*, but then every gtk3 application shows
Code: | WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
CRITICAL **: atk_bridge_adaptor_cleanup: assertion `inited' failed |
which seems harmless, but annoying. No way to completely disable a11y?
Last edited by Fran on Mon Jan 07, 2013 8:25 am; edited 1 time in total |
|
Back to top |
|
|
Fran Guru
Joined: 29 Feb 2004 Posts: 530 Location: Coruña (Spain)
|
Posted: Mon Jan 07, 2013 8:25 am Post subject: |
|
|
Just found a post that lead me to a solution: setting NO_AT_BRIDGE=1 somewhere in the environment avoids gtk3 programs spawning that stupid daemon. I had to apply this patch too.
BTW, this response is quite eye-opening:
Quote: | So these seem to fall into the "people wanting to consume GTK3 outside of the GNOME schedule". We should be receptive to this, but we also shouldn't block progress in GNOME on it. |
I thought gtk was independent of gnome, and gnome was simply built on top :/. Now I understand better this rant by the spacefm developer. |
|
Back to top |
|
|
Ottre Tux's lil' helper
Joined: 23 Dec 2012 Posts: 129
|
Posted: Thu Jan 10, 2013 9:32 am Post subject: |
|
|
What does this patch do exactly? Does it supress the error message:
Code: |
CRITICAL **: atk_bridge_adaptor_cleanup: assertion 'inited' failed
|
That has been really annoying for me when I use zenity in my bash scripts. |
|
Back to top |
|
|
Fran Guru
Joined: 29 Feb 2004 Posts: 530 Location: Coruña (Spain)
|
Posted: Thu Jan 10, 2013 6:24 pm Post subject: |
|
|
Ottre wrote: |
What does this patch do exactly? Does it supress the error message:
Code: |
CRITICAL **: atk_bridge_adaptor_cleanup: assertion 'inited' failed
|
That has been really annoying for me when I use zenity in my bash scripts. |
Yep. It will be merged upstream in gtk+-3.7, I think. With that and NO_AT_BRIDGE I have a system without annoyances or retarded background daemons (i.e., no gnome crap running). |
|
Back to top |
|
|
Ottre Tux's lil' helper
Joined: 23 Dec 2012 Posts: 129
|
Posted: Thu Jan 10, 2013 6:42 pm Post subject: |
|
|
Fran wrote: |
Yep. It will be merged upstream in gtk+-3.7, I think. With that and NO_AT_BRIDGE I have a system without annoyances or retarded background daemons (i.e., no gnome crap running).
|
Good. I think the GNOME devs assume that people who don't use AT will just keep it running in the background. It's enabled by default in a lot of GNOME-based distributions. It should be the other way around IMO. |
|
Back to top |
|
|
Fran Guru
Joined: 29 Feb 2004 Posts: 530 Location: Coruña (Spain)
|
Posted: Thu Jan 10, 2013 7:06 pm Post subject: |
|
|
Spoke too soon. Sometimes I still see a process "at-spi-bus-launcher" running. Not every time I start a gtk3 program, like it happened before I set NO_AT_BRIDGE, but sporadically. Something still uses /usr/share/dbus-1/services/org.a11y.Bus.service. Is there any way to know what does this? |
|
Back to top |
|
|
heroxbd Developer
Joined: 11 Dec 2011 Posts: 31 Location: Kamioka, Hida, Japan
|
Posted: Sat Aug 24, 2013 10:22 am Post subject: It works |
|
|
Thank you very much Fran. I have NO_AT_BRIDGE=1 set in /etc/env.d/99basic. And it works like a charm with gtk+3.6.3-r2. |
|
Back to top |
|
|
|