Posting in this sub-forum to follow up on what was a significant problem in TW and possibly grub, took a lot of heavy lifting from the forum gurus to repair, but since then the system has been running well . . . using the “default video module” as per “mrmazda’s” suggestion . . . rather than “nouveau” or “nvidia” . . . although there might be some issues with getting a TTY shell to show up . . . ??? But that isn’t today’s complaint . . . .
Ran a search of “at-bus-launcher” and “no results found” was the response, so I’m posting here to report that every time I try to shut down from the main menu an error of “at-bus-launcher is not responding, would you like to shut down anyway?” error dialogue opens . . . if I click yes, the machine must go into a “shutting down in one minute, but from a few seconds from now . . .” mode, because the machine pauses for awhile before then beginning to shut down . . . .
I prefer that when I click “shut down” the machine just “shuts down” . . . no error window asking me if I “really want to shut down because people are still doing stuff and would like to keep doing that, particularly mr. bus-launcher is busy” type message . . . . Any way to work around that problem??
Highly annoying to have to wait to shut down, I fully agree. What does
sudo journalctl | grep at-bus-launcher
output? If you get any hits, do
sudo journalctl -b
and search for at-bus-launcher to see the messages before and after for clues to what it belongs to or causes it.
Is this in your Mac? If not, are there AT bus devices present, maybe a floppy drive, or a CD or DVD drive on ATAPI/PATA? Do you use a PS/2 keyboard connector plugged into the correct port?
Is this a Wayland session? Xorg? Which DE do you use, Gnome? KDE? Other?
Thanks for the reply, I’m now away from that computer so I can’t run any commands just yet. Yep, on the Mac Pro, there is an optical drive, there is a plug-in usb keyboard, don’t know what PS/2 keyboard is . . . .
This is a “new” thing in TW . . . didn’t happen in Leap when I had that going, can’t remember if this started with this recent install, as there were significant issues with it . . . but possibly showed up after some updates . . . .
Should be Xorg with MATE DE . . . .
I also have MATE running in a Gecko install and this issue isn’t happening over there . . . in the other OpenSUSE system that I have installed . . . .
I tried to run it as a “sudo cat” and it returned “No such file or directory.” I opened File sytem in the GUI and searched it with “.xsession-errors” . . . nothing came back.
I don’t have any Mate installations, so have no way to test, but I suspect this is about your Mate session, not X or the base system. To see if this is the case, log into an IceWM session instead of Mate, then try shutting down.
If you haven’t already done so, try logging out of your desktop session, then choosing to shut down from the greeter/login screen. Does it make a difference?
~> sudo journalctl -b -1 | grep ailed
[sudo] password for root:
Feb 18 07:08:41 linux-f6nl systemd[1]: haveged.service: Failed with result 'exit-code'.
Feb 18 07:08:50 linux-f6nl systemd-udevd[867]: controlC0: Process '/usr/sbin/alsactl restore 0' failed with exit code 99.
Feb 18 07:08:51 linux-f6nl systemd-udevd[865]: controlC1: Process '/usr/sbin/alsactl restore 1' failed with exit code 99.
Feb 18 07:08:52 linux-f6nl nscd[1076]: 1076 stat failed for file `/etc/services'; will try again later: No such file or directory
Feb 18 07:08:57 linux-f6nl firewalld[1180]: ERROR: Failed to load service file '/usr/lib/firewalld/services/docker-swarm.xml': INVALID_PROTOCOL: esp
Feb 18 07:08:57 linux-f6nl firewalld[1180]: ERROR: Failed to load service file '/usr/lib/firewalld/services/gre.xml': INVALID_PROTOCOL: gre
Feb 18 07:08:57 linux-f6nl firewalld[1180]: ERROR: Failed to load service file '/usr/lib/firewalld/services/ipsec.xml': INVALID_PROTOCOL: ah
Feb 18 07:09:20 linux-f6nl accounts-daemon[2056]: g_dbus_interface_skeleton_get_object_path: assertion 'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
Feb 18 07:11:31 linux-f6nl at-spi-bus-laun[5941]: Failed to register client: Timeout was reached
Feb 18 09:13:06 linux-f6nl org.mate.panel.applet.MateMenuAppletFactory[23730]: MESA-LOADER: failed to open nouveau (search paths /usr/lib64/dri)
Feb 18 09:13:06 linux-f6nl org.mate.panel.applet.MateMenuAppletFactory[23730]: libGL error: failed to load driver: nouveau
Feb 18 09:18:03 linux-f6nl mate-session[5876]: WARNING: Client '/org/gnome/SessionManager/Client1' failed to reply before timeout
Several of those lines point to potentially serious trouble. Actually I shouldn’t have suggested the “| less” part, because less is what journalctl incorporates in the first place.
As always with less, while its output remains on screen you can search using / to start, then typing a string to search for, such as at-spi-bus-laun, which looks like a good match for your thread title. If interested only in this one failed line, you can get some likely helpful context this way:
“stat failed for file `/etc/services’” is a known problem that I have no idea what to do about. I have seen multiple factory mailing list threads discussing it. *bus-launcher could be more fallout because of that more general problem.
Did run that last line and it brought quite a long list, I just copied the bottom few lines . . . .
Feb 18 09:18:52 linux-fl at-spi-bus-launcher[324]: dbus-daemon[324]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=489 pid=300 comm="/usr/sbin/lightdm-gtk-greeter ")
Feb 18 09:18:52 linux-fl at-spi-bus-launcher[324]: dbus-daemon[324]: Successfully activated service 'org.a11y.atspi.Registry'
Feb 18 09:18:52 linux-fl at-spi-bus-launcher[347]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Feb 18 09:18:52 linux-fl systemd[1]: session-2.scope: Succeeded.
Feb 18 09:18:52 linux-fl systemd-logind[1193]: Removed session 2.
Feb 18 09:19:02 linux-fl systemd[1]: Stopping User Manager for UID 1000...
Feb 18 09:19:02 linux-fl systemd[5861]: Stopped target Bluetooth.
Feb 18 09:19:02 linux-fl systemd[5861]: Stopped target Main User Target.
Feb 18 09:19:02 linux-fl systemd[5861]: Stopping D-Bus User Message Bus...
Feb 18 09:19:02 linux-fl systemd[5861]: dbus.service: Succeeded.
Feb 18 09:19:02 linux-fl systemd[5861]: Stopped D-Bus User Message Bus.
Bump. What does the “at-bus-launcher” do? Error window still opens each time I try to shut TW down . . . and then puts a timer on it . . . delaying the shut down, etc.
It’s an “error” window that opens each time I try to shut down from GUI . . . don’t have this issue in any of my other linux distros . . . . But, no, no assistive technologies enabled.
These packages are all for assistive technology. If you don’t use AT, uninstall them. If you do, try reinstalling them. If it doesn’t help, report a bug.
OK, well I didn’t request the AT, just checked the preferences and the “enable AT” button is unchecked . . . . I did an update this morning and when I “logged out” I got this same error window, but when I logged back in and then did a “suspend” I didn’t get the error, so I thought the problem was “solved” . . . but, again testing for log out and shut down, brought the error back . . . .
So, if I’m wanting to remove each of the packages that are listed in the code I posted before, using Yast to locate them and let Yast do the dirty work? OR, I can run "sudo zypper rm (list of package names separated by space) and that would handle the AT package removal??? Jes checking before I start banging away in the console ubuntu style . . . .
Thanks for the code, what does the “al” represent? I think I asked you this before, but it was on another thread in a distant land . . . I’m going to run the commands starting now, but for the “refresher” . . . senioritis, etc.
If you don’t use Mate, proceed as instructed. If you do, either report a bug, and live with the problem until the bug gets fixed, or report the bug and try it this way to cover the interim until the bug is fixed: