| Summary: | x11-drivers/nvidia-drivers launches extra dbus session bus | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Emily Mills <emily> |
| Component: | Current packages | Assignee: | David Seifert <soap> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | ionen, poncho |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=414725 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Emily Mills
2015-04-04 19:54:35 UTC
When the nvidia-script is enabled: ps ux | grep dbus adam 4684 0.0 0.0 21820 240 ? Ss 15:06 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session adam 10314 0.0 0.0 24328 1916 ? S 15:55 0:00 /usr/bin/dbus-launch --autolaunch e7b3887680c0636a1a3b6e3f5094380a --binary-syntax --close-stderr adam 10315 0.0 0.0 21820 2260 ? Ss 15:55 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session adam 10321 0.0 0.0 21820 2820 ? S 15:55 0:00 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3 adam 10328 0.0 0.0 24328 1888 ? S 15:55 0:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/ssh-agent -- i3 adam 10329 0.1 0.0 22036 2416 ? Ss 15:55 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session adam 10366 0.0 0.0 21820 2824 ? S 15:55 0:00 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3 adam 10494 0.0 0.0 112616 2204 pts/2 S+ 15:56 0:00 grep --colour=auto dbus PID 10314 shows the bus launched by nvidia-settings. PID 10328 shows the bus launched with the window manager. I've tested the following workaround in /etc/X11/xinit/xinitrc.d/95-nvidia-settings #!/bin/sh DBUS_SESSION_BUS_ADDRESS="None" /opt/bin/nvidia-settings --load-config-only Defining DBUS_SESSION_BUS_ADDRESS prevents the dbus-launch utility from starting a new bus, as described in the following excerpt from the man page: If DBUS_SESSION_BUS_ADDRESS is not set for a process that tries to use D-Bus, by default the process will attempt to invoke dbus-launch with the --autolaunch option to start up a new session bus or find the existing bus address on the X display or in a file in ~/.dbus/session-bus/ Whenever an autolaunch occurs, the application that had to start a new bus will be in its own little world; it can effectively end up starting a whole new session if it tries to use a lot of bus services. This can be suboptimal or even totally broken, depending on the app and what it tries to do. I believe this is obsolete, nvidia-settings doesn't seem to force-start dbus (or at least, not anymore). Please open a new bug if still observing the behavior and I'll try to figure out why it's not happening for me. |
