Why is my terminal emulator process is using d-bus?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












1















$ sudo lsof +E -a -U -p 1480
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1001/gvfs
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
Xorg 717 root 43u unix 0xffff975eacf2d400 0t0 30862 @/tmp/.X11-unix/X0 type=STREAM ->INO=28661 1480,lxtermina,3u
dbus-daem 980 t 34u unix 0xffff975eacf2fc00 0t0 30865 /run/user/1000/bus type=STREAM ->INO=28666 1480,lxtermina,9u
dbus-daem 1073 t 13u unix 0xffff975eacf2c400 0t0 28664 @/tmp/dbus-vtzJFcQ5Cy type=STREAM ->INO=28663 1480,lxtermina,5u
lxtermina 1480 t 3u unix 0xffff975eacf2c000 0t0 28661 type=STREAM ->INO=30862 717,Xorg,43u
lxtermina 1480 t 5u unix 0xffff975eacf2d000 0t0 28663 type=STREAM ->INO=28664 1073,dbus-daem,13u
lxtermina 1480 t 7u unix 0xffff975eacf2f000 0t0 28665 /run/user/1000/.lxterminal-socket- type=STREAM
lxtermina 1480 t 9u unix 0xffff975eacf2e800 0t0 28666 type=STREAM ->INO=30865 980,dbus-daem,34u


The lxterminal process communicates with Xorg process for GUI of lxterminal.



Then What is communication with dbus for? It's just a terminal emulator, why does it want to use dbus?



Thanks.










share|improve this question
























  • Do you know what dbus is?

    – Rui F Ribeiro
    Jan 6 at 9:08











  • @Rui stackoverflow.com/questions/54059022/is-d-bus-middleware-ipc

    – Tim
    Jan 6 at 12:26















1















$ sudo lsof +E -a -U -p 1480
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1001/gvfs
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
Xorg 717 root 43u unix 0xffff975eacf2d400 0t0 30862 @/tmp/.X11-unix/X0 type=STREAM ->INO=28661 1480,lxtermina,3u
dbus-daem 980 t 34u unix 0xffff975eacf2fc00 0t0 30865 /run/user/1000/bus type=STREAM ->INO=28666 1480,lxtermina,9u
dbus-daem 1073 t 13u unix 0xffff975eacf2c400 0t0 28664 @/tmp/dbus-vtzJFcQ5Cy type=STREAM ->INO=28663 1480,lxtermina,5u
lxtermina 1480 t 3u unix 0xffff975eacf2c000 0t0 28661 type=STREAM ->INO=30862 717,Xorg,43u
lxtermina 1480 t 5u unix 0xffff975eacf2d000 0t0 28663 type=STREAM ->INO=28664 1073,dbus-daem,13u
lxtermina 1480 t 7u unix 0xffff975eacf2f000 0t0 28665 /run/user/1000/.lxterminal-socket- type=STREAM
lxtermina 1480 t 9u unix 0xffff975eacf2e800 0t0 28666 type=STREAM ->INO=30865 980,dbus-daem,34u


The lxterminal process communicates with Xorg process for GUI of lxterminal.



Then What is communication with dbus for? It's just a terminal emulator, why does it want to use dbus?



Thanks.










share|improve this question
























  • Do you know what dbus is?

    – Rui F Ribeiro
    Jan 6 at 9:08











  • @Rui stackoverflow.com/questions/54059022/is-d-bus-middleware-ipc

    – Tim
    Jan 6 at 12:26













1












1








1








$ sudo lsof +E -a -U -p 1480
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1001/gvfs
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
Xorg 717 root 43u unix 0xffff975eacf2d400 0t0 30862 @/tmp/.X11-unix/X0 type=STREAM ->INO=28661 1480,lxtermina,3u
dbus-daem 980 t 34u unix 0xffff975eacf2fc00 0t0 30865 /run/user/1000/bus type=STREAM ->INO=28666 1480,lxtermina,9u
dbus-daem 1073 t 13u unix 0xffff975eacf2c400 0t0 28664 @/tmp/dbus-vtzJFcQ5Cy type=STREAM ->INO=28663 1480,lxtermina,5u
lxtermina 1480 t 3u unix 0xffff975eacf2c000 0t0 28661 type=STREAM ->INO=30862 717,Xorg,43u
lxtermina 1480 t 5u unix 0xffff975eacf2d000 0t0 28663 type=STREAM ->INO=28664 1073,dbus-daem,13u
lxtermina 1480 t 7u unix 0xffff975eacf2f000 0t0 28665 /run/user/1000/.lxterminal-socket- type=STREAM
lxtermina 1480 t 9u unix 0xffff975eacf2e800 0t0 28666 type=STREAM ->INO=30865 980,dbus-daem,34u


The lxterminal process communicates with Xorg process for GUI of lxterminal.



Then What is communication with dbus for? It's just a terminal emulator, why does it want to use dbus?



Thanks.










share|improve this question
















$ sudo lsof +E -a -U -p 1480
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1001/gvfs
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
Xorg 717 root 43u unix 0xffff975eacf2d400 0t0 30862 @/tmp/.X11-unix/X0 type=STREAM ->INO=28661 1480,lxtermina,3u
dbus-daem 980 t 34u unix 0xffff975eacf2fc00 0t0 30865 /run/user/1000/bus type=STREAM ->INO=28666 1480,lxtermina,9u
dbus-daem 1073 t 13u unix 0xffff975eacf2c400 0t0 28664 @/tmp/dbus-vtzJFcQ5Cy type=STREAM ->INO=28663 1480,lxtermina,5u
lxtermina 1480 t 3u unix 0xffff975eacf2c000 0t0 28661 type=STREAM ->INO=30862 717,Xorg,43u
lxtermina 1480 t 5u unix 0xffff975eacf2d000 0t0 28663 type=STREAM ->INO=28664 1073,dbus-daem,13u
lxtermina 1480 t 7u unix 0xffff975eacf2f000 0t0 28665 /run/user/1000/.lxterminal-socket- type=STREAM
lxtermina 1480 t 9u unix 0xffff975eacf2e800 0t0 28666 type=STREAM ->INO=30865 980,dbus-daem,34u


The lxterminal process communicates with Xorg process for GUI of lxterminal.



Then What is communication with dbus for? It's just a terminal emulator, why does it want to use dbus?



Thanks.







d-bus terminal-emulator






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 6 at 9:48









炸鱼薯条德里克

431114




431114










asked Jan 6 at 4:13









TimTim

26.4k75250459




26.4k75250459












  • Do you know what dbus is?

    – Rui F Ribeiro
    Jan 6 at 9:08











  • @Rui stackoverflow.com/questions/54059022/is-d-bus-middleware-ipc

    – Tim
    Jan 6 at 12:26

















  • Do you know what dbus is?

    – Rui F Ribeiro
    Jan 6 at 9:08











  • @Rui stackoverflow.com/questions/54059022/is-d-bus-middleware-ipc

    – Tim
    Jan 6 at 12:26
















Do you know what dbus is?

– Rui F Ribeiro
Jan 6 at 9:08





Do you know what dbus is?

– Rui F Ribeiro
Jan 6 at 9:08













@Rui stackoverflow.com/questions/54059022/is-d-bus-middleware-ipc

– Tim
Jan 6 at 12:26





@Rui stackoverflow.com/questions/54059022/is-d-bus-middleware-ipc

– Tim
Jan 6 at 12:26










1 Answer
1






active

oldest

votes


















2














Note that there can be several DBus instances on your system:



  • the system bus, that has its socket at /var/run/dbus/system_bus_socket or similar directory that is only writable by root. It is started at boot time.

  • the user session bus that is started when you start a GUI desktop session and goes away when you log out.

  • the accessibility bus, which originally used CORBA but has now been switched to more lightweight DBus. It supports various accessibility features of the desktop environment.

Since the dbus-daemon process is running on your own user account



The description of lxterminal at LXDE.org says:




LXTerminal supports multiple tabs. All instances of program share the same process to reduce memory usage.




I don't personally use LXTerminal, but this is probably the main reason for its use of DBus: when you attempt to start a new lxterminal window by clicking on a desktop icon or menu, the starting lxterminal process probably uses D-Bus to see if another instance of it is already running.



If there's already one LXTerminal process running, the new one can then simply send a "open a new window/tab with these options..." DBus message to the already-running process, and exit. The already-running LXTerminal process will then open a new window or set up a new tab according to its settings and/or options passed to it.






share|improve this answer























  • Thanks. unix.stackexchange.com/a/486140/674 says lxterminal uses Unix domain sockets to ensure only one process running lxterminal. Are you sure it is D-bus instead of sockets?

    – Tim
    Jan 6 at 13:42











  • I'm not really sure, but it could use both: its own socket for situations where session D-Bus is not available, and D-Bus to allow the desktop environment to start more terminal windows/tabs in a standardized way that is not limited to LXTerminal or LXDE only. It might also do more than that with DBus. You could use dbus-monitor to see what happens on the DBus when you start the first LXTerminal instance, or use dbus-send to introspect the DBus interface provided by the LXTerminal process.

    – telcoM
    Jan 6 at 14:12











  • What does the desktop environment (LXDE or Gnome or whichever you know) use D-Bus for in general?

    – Tim
    Jan 6 at 14:22












  • Another question, is D-bus is implemented using sockets? Is /run/user/1000/.lxterminal-socket- type=STREAM the socket that lxterminal used for ensuring only one process is running lxterminal? Is the socket not the one underlying D-bus?

    – Tim
    Jan 6 at 15:37











  • LXTerminal uses its own socket for client-server work. unix.stackexchange.com/a/333578/5132 . It does not use the Desktop Bus, and in fact itself contains no D-Bus code.

    – JdeBP
    Jan 6 at 16:45










Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f492752%2fwhy-is-my-terminal-emulator-process-is-using-d-bus%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









2














Note that there can be several DBus instances on your system:



  • the system bus, that has its socket at /var/run/dbus/system_bus_socket or similar directory that is only writable by root. It is started at boot time.

  • the user session bus that is started when you start a GUI desktop session and goes away when you log out.

  • the accessibility bus, which originally used CORBA but has now been switched to more lightweight DBus. It supports various accessibility features of the desktop environment.

Since the dbus-daemon process is running on your own user account



The description of lxterminal at LXDE.org says:




LXTerminal supports multiple tabs. All instances of program share the same process to reduce memory usage.




I don't personally use LXTerminal, but this is probably the main reason for its use of DBus: when you attempt to start a new lxterminal window by clicking on a desktop icon or menu, the starting lxterminal process probably uses D-Bus to see if another instance of it is already running.



If there's already one LXTerminal process running, the new one can then simply send a "open a new window/tab with these options..." DBus message to the already-running process, and exit. The already-running LXTerminal process will then open a new window or set up a new tab according to its settings and/or options passed to it.






share|improve this answer























  • Thanks. unix.stackexchange.com/a/486140/674 says lxterminal uses Unix domain sockets to ensure only one process running lxterminal. Are you sure it is D-bus instead of sockets?

    – Tim
    Jan 6 at 13:42











  • I'm not really sure, but it could use both: its own socket for situations where session D-Bus is not available, and D-Bus to allow the desktop environment to start more terminal windows/tabs in a standardized way that is not limited to LXTerminal or LXDE only. It might also do more than that with DBus. You could use dbus-monitor to see what happens on the DBus when you start the first LXTerminal instance, or use dbus-send to introspect the DBus interface provided by the LXTerminal process.

    – telcoM
    Jan 6 at 14:12











  • What does the desktop environment (LXDE or Gnome or whichever you know) use D-Bus for in general?

    – Tim
    Jan 6 at 14:22












  • Another question, is D-bus is implemented using sockets? Is /run/user/1000/.lxterminal-socket- type=STREAM the socket that lxterminal used for ensuring only one process is running lxterminal? Is the socket not the one underlying D-bus?

    – Tim
    Jan 6 at 15:37











  • LXTerminal uses its own socket for client-server work. unix.stackexchange.com/a/333578/5132 . It does not use the Desktop Bus, and in fact itself contains no D-Bus code.

    – JdeBP
    Jan 6 at 16:45















2














Note that there can be several DBus instances on your system:



  • the system bus, that has its socket at /var/run/dbus/system_bus_socket or similar directory that is only writable by root. It is started at boot time.

  • the user session bus that is started when you start a GUI desktop session and goes away when you log out.

  • the accessibility bus, which originally used CORBA but has now been switched to more lightweight DBus. It supports various accessibility features of the desktop environment.

Since the dbus-daemon process is running on your own user account



The description of lxterminal at LXDE.org says:




LXTerminal supports multiple tabs. All instances of program share the same process to reduce memory usage.




I don't personally use LXTerminal, but this is probably the main reason for its use of DBus: when you attempt to start a new lxterminal window by clicking on a desktop icon or menu, the starting lxterminal process probably uses D-Bus to see if another instance of it is already running.



If there's already one LXTerminal process running, the new one can then simply send a "open a new window/tab with these options..." DBus message to the already-running process, and exit. The already-running LXTerminal process will then open a new window or set up a new tab according to its settings and/or options passed to it.






share|improve this answer























  • Thanks. unix.stackexchange.com/a/486140/674 says lxterminal uses Unix domain sockets to ensure only one process running lxterminal. Are you sure it is D-bus instead of sockets?

    – Tim
    Jan 6 at 13:42











  • I'm not really sure, but it could use both: its own socket for situations where session D-Bus is not available, and D-Bus to allow the desktop environment to start more terminal windows/tabs in a standardized way that is not limited to LXTerminal or LXDE only. It might also do more than that with DBus. You could use dbus-monitor to see what happens on the DBus when you start the first LXTerminal instance, or use dbus-send to introspect the DBus interface provided by the LXTerminal process.

    – telcoM
    Jan 6 at 14:12











  • What does the desktop environment (LXDE or Gnome or whichever you know) use D-Bus for in general?

    – Tim
    Jan 6 at 14:22












  • Another question, is D-bus is implemented using sockets? Is /run/user/1000/.lxterminal-socket- type=STREAM the socket that lxterminal used for ensuring only one process is running lxterminal? Is the socket not the one underlying D-bus?

    – Tim
    Jan 6 at 15:37











  • LXTerminal uses its own socket for client-server work. unix.stackexchange.com/a/333578/5132 . It does not use the Desktop Bus, and in fact itself contains no D-Bus code.

    – JdeBP
    Jan 6 at 16:45













2












2








2







Note that there can be several DBus instances on your system:



  • the system bus, that has its socket at /var/run/dbus/system_bus_socket or similar directory that is only writable by root. It is started at boot time.

  • the user session bus that is started when you start a GUI desktop session and goes away when you log out.

  • the accessibility bus, which originally used CORBA but has now been switched to more lightweight DBus. It supports various accessibility features of the desktop environment.

Since the dbus-daemon process is running on your own user account



The description of lxterminal at LXDE.org says:




LXTerminal supports multiple tabs. All instances of program share the same process to reduce memory usage.




I don't personally use LXTerminal, but this is probably the main reason for its use of DBus: when you attempt to start a new lxterminal window by clicking on a desktop icon or menu, the starting lxterminal process probably uses D-Bus to see if another instance of it is already running.



If there's already one LXTerminal process running, the new one can then simply send a "open a new window/tab with these options..." DBus message to the already-running process, and exit. The already-running LXTerminal process will then open a new window or set up a new tab according to its settings and/or options passed to it.






share|improve this answer













Note that there can be several DBus instances on your system:



  • the system bus, that has its socket at /var/run/dbus/system_bus_socket or similar directory that is only writable by root. It is started at boot time.

  • the user session bus that is started when you start a GUI desktop session and goes away when you log out.

  • the accessibility bus, which originally used CORBA but has now been switched to more lightweight DBus. It supports various accessibility features of the desktop environment.

Since the dbus-daemon process is running on your own user account



The description of lxterminal at LXDE.org says:




LXTerminal supports multiple tabs. All instances of program share the same process to reduce memory usage.




I don't personally use LXTerminal, but this is probably the main reason for its use of DBus: when you attempt to start a new lxterminal window by clicking on a desktop icon or menu, the starting lxterminal process probably uses D-Bus to see if another instance of it is already running.



If there's already one LXTerminal process running, the new one can then simply send a "open a new window/tab with these options..." DBus message to the already-running process, and exit. The already-running LXTerminal process will then open a new window or set up a new tab according to its settings and/or options passed to it.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 6 at 13:29









telcoMtelcoM

16.2k12144




16.2k12144












  • Thanks. unix.stackexchange.com/a/486140/674 says lxterminal uses Unix domain sockets to ensure only one process running lxterminal. Are you sure it is D-bus instead of sockets?

    – Tim
    Jan 6 at 13:42











  • I'm not really sure, but it could use both: its own socket for situations where session D-Bus is not available, and D-Bus to allow the desktop environment to start more terminal windows/tabs in a standardized way that is not limited to LXTerminal or LXDE only. It might also do more than that with DBus. You could use dbus-monitor to see what happens on the DBus when you start the first LXTerminal instance, or use dbus-send to introspect the DBus interface provided by the LXTerminal process.

    – telcoM
    Jan 6 at 14:12











  • What does the desktop environment (LXDE or Gnome or whichever you know) use D-Bus for in general?

    – Tim
    Jan 6 at 14:22












  • Another question, is D-bus is implemented using sockets? Is /run/user/1000/.lxterminal-socket- type=STREAM the socket that lxterminal used for ensuring only one process is running lxterminal? Is the socket not the one underlying D-bus?

    – Tim
    Jan 6 at 15:37











  • LXTerminal uses its own socket for client-server work. unix.stackexchange.com/a/333578/5132 . It does not use the Desktop Bus, and in fact itself contains no D-Bus code.

    – JdeBP
    Jan 6 at 16:45

















  • Thanks. unix.stackexchange.com/a/486140/674 says lxterminal uses Unix domain sockets to ensure only one process running lxterminal. Are you sure it is D-bus instead of sockets?

    – Tim
    Jan 6 at 13:42











  • I'm not really sure, but it could use both: its own socket for situations where session D-Bus is not available, and D-Bus to allow the desktop environment to start more terminal windows/tabs in a standardized way that is not limited to LXTerminal or LXDE only. It might also do more than that with DBus. You could use dbus-monitor to see what happens on the DBus when you start the first LXTerminal instance, or use dbus-send to introspect the DBus interface provided by the LXTerminal process.

    – telcoM
    Jan 6 at 14:12











  • What does the desktop environment (LXDE or Gnome or whichever you know) use D-Bus for in general?

    – Tim
    Jan 6 at 14:22












  • Another question, is D-bus is implemented using sockets? Is /run/user/1000/.lxterminal-socket- type=STREAM the socket that lxterminal used for ensuring only one process is running lxterminal? Is the socket not the one underlying D-bus?

    – Tim
    Jan 6 at 15:37











  • LXTerminal uses its own socket for client-server work. unix.stackexchange.com/a/333578/5132 . It does not use the Desktop Bus, and in fact itself contains no D-Bus code.

    – JdeBP
    Jan 6 at 16:45
















Thanks. unix.stackexchange.com/a/486140/674 says lxterminal uses Unix domain sockets to ensure only one process running lxterminal. Are you sure it is D-bus instead of sockets?

– Tim
Jan 6 at 13:42





Thanks. unix.stackexchange.com/a/486140/674 says lxterminal uses Unix domain sockets to ensure only one process running lxterminal. Are you sure it is D-bus instead of sockets?

– Tim
Jan 6 at 13:42













I'm not really sure, but it could use both: its own socket for situations where session D-Bus is not available, and D-Bus to allow the desktop environment to start more terminal windows/tabs in a standardized way that is not limited to LXTerminal or LXDE only. It might also do more than that with DBus. You could use dbus-monitor to see what happens on the DBus when you start the first LXTerminal instance, or use dbus-send to introspect the DBus interface provided by the LXTerminal process.

– telcoM
Jan 6 at 14:12





I'm not really sure, but it could use both: its own socket for situations where session D-Bus is not available, and D-Bus to allow the desktop environment to start more terminal windows/tabs in a standardized way that is not limited to LXTerminal or LXDE only. It might also do more than that with DBus. You could use dbus-monitor to see what happens on the DBus when you start the first LXTerminal instance, or use dbus-send to introspect the DBus interface provided by the LXTerminal process.

– telcoM
Jan 6 at 14:12













What does the desktop environment (LXDE or Gnome or whichever you know) use D-Bus for in general?

– Tim
Jan 6 at 14:22






What does the desktop environment (LXDE or Gnome or whichever you know) use D-Bus for in general?

– Tim
Jan 6 at 14:22














Another question, is D-bus is implemented using sockets? Is /run/user/1000/.lxterminal-socket- type=STREAM the socket that lxterminal used for ensuring only one process is running lxterminal? Is the socket not the one underlying D-bus?

– Tim
Jan 6 at 15:37





Another question, is D-bus is implemented using sockets? Is /run/user/1000/.lxterminal-socket- type=STREAM the socket that lxterminal used for ensuring only one process is running lxterminal? Is the socket not the one underlying D-bus?

– Tim
Jan 6 at 15:37













LXTerminal uses its own socket for client-server work. unix.stackexchange.com/a/333578/5132 . It does not use the Desktop Bus, and in fact itself contains no D-Bus code.

– JdeBP
Jan 6 at 16:45





LXTerminal uses its own socket for client-server work. unix.stackexchange.com/a/333578/5132 . It does not use the Desktop Bus, and in fact itself contains no D-Bus code.

– JdeBP
Jan 6 at 16:45

















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f492752%2fwhy-is-my-terminal-emulator-process-is-using-d-bus%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown






Popular posts from this blog

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay