Issue #1 new

gdm is capable of receiving system wide notices and hanging notification daemons, how to avoid?

Leho Kraav
created an issue

Here's what my gdm user is running:

$ pstree -u gdm -a
at-spi-bus-laun
  ├─dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
  └─3*[{at-spi-bus-laun}]

at-spi2-registr --use-gnome-session
  └─{at-spi2-registr}

dbus-daemon --fork --print-pid 5 --print-address 7 --session

dbus-launch --exit-with-session /usr/bin/gnome-session --autostart /usr/share/gdm/greeter/autostart

dconf-service
  └─2*[{dconf-service}]

gconfd-2

gnome-session --autostart /usr/share/gdm/greeter/autostart
  ├─gnome-settings-
  │   └─3*[{gnome-settings-}]
  ├─gnome-shell --mode=gdm
  │   └─5*[{gnome-shell}]
  └─3*[{gnome-session}]

gvfs-udisks2-vo
  └─{gvfs-udisks2-vo}

gvfsd
  └─{gvfsd}

pulseaudio --start --log-target=syslog
  ├─gconf-helper
  └─2*[{pulseaudio}]

It could be related to user switching with gdmflexiserver. Either way, gdm is apparently sitting in a session and therefore can receive these systemwide messages via dbus. This seems to hang the shell scripts sending my systemwide messages.

Can libtinynotify-systemwide perhaps apply some ignore list? I am not really sure what other conditions to look for in procenv besides the ones you already do.

Comments (2)

  1. Michał Górny repo owner

    What are you using to send the notifications? To be honest, I haven't looked into the project code for a while but I don't think it's capable of waiting for systemwide-notifications…

    Also, I don't think I understand your process list paste…

  2. Leho Kraav reporter

    I am using sw-notify-send.

    Re process list: I don't either :) first time using pstree. But basically it just shows all the processes that user "gdm" is currently running in the background. I am not entirely sure why gdm would be sitting with an active dbus session etc, other than maybe the multiple user switching thing.

  3. Log in to comment