Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timeout was reached (24) error on startup Ubuntu 20.04 #22
Timeout was reached (24) error on startup Ubuntu 20.04 #22
Comments
Hi, I’m having issues using cdemu after installing using cdemu PPAs.
I’ve checked and it appears I’m using the latest / correct versions of both cdemu and gcdemu —
kapper@xps:~$ cdemu --version cdemu 3.2.5 - (C) 2006-2022 Rok Mandeljc gcdemu shows version 3.2.6 using the ‘about’ context menu option.
I was able to use cdemu for maybe a day or so before this started to happen. I found Bug # 1926303 on launchpad is very similar, except that the solution there doesn’t work, as dbus-service-session is not an ubuntu package.
kapper@xps:~$ sudo apt install dbus-service-session [sudo] password for kapper: Reading package lists. Done Building dependency tree Reading state information. Done E: Unable to locate package dbus-service-session kapper@xps:~$ sudo apt search dbus-service-session Sorting. Done Full Text Search. Done Did a quick google search and I can’t find anything on dbus-service-session , only dbus-user-session , which is already installed with no pending updates.
Here’s the contents of journalctl —user-unit cdemu-daemon across two separate reboots. This is especially odd because I never configured cdemu to start on boot — but it (gcdemu) does start on boot and errors out.
-- Reboot -- Jan 19 23:18:33 xps systemd[2369]: Starting CDEmu daemon. Jan 19 23:18:33 xps cdemu-daemon[5111]: Starting CDEmu daemon with following parameters: Jan 19 23:18:33 xps cdemu-daemon[5111]: - config file: /home/kapper/.config/cdemu-daemon (exists: 0) Jan 19 23:18:33 xps cdemu-daemon[5111]: - num devices: 1 Jan 19 23:18:33 xps cdemu-daemon[5111]: - control device: /dev/vhba_ctl Jan 19 23:18:33 xps cdemu-daemon[5111]: - audio driver: null Jan 19 23:18:33 xps cdemu-daemon[5111]: - bus type: session Jan 19 23:18:33 xps cdemu-daemon[5111]: - default CDEmu debug mask: 0x0 Jan 19 23:18:33 xps cdemu-daemon[5111]: - default libMirage debug mask: 0x0 Jan 19 23:18:33 xps cdemu-daemon[5111]: cdemu0: Kernel I/O: failed to open control device /dev/vhba_ctl: > Jan 19 23:18:33 xps cdemu-daemon[5111]: cdemu: Daemon: failed to start device #0! Jan 19 23:18:33 xps cdemu-daemon[5111]: cdemu: Daemon: failed to create device! Jan 19 23:18:33 xps cdemu-daemon[5111]: Daemon initialization and start failed! Jan 19 23:18:33 xps systemd[2369]: cdemu-daemon.service: Main process exited, code=exited, status=255/EXC> Jan 19 23:18:33 xps systemd[2369]: cdemu-daemon.service: Failed with result 'exit-code'. Jan 19 23:18:33 xps systemd[2369]: Failed to start CDEmu daemon. # NOTE: I attempt to manually start gcdemu here Jan 19 23:22:50 xps systemd[2369]: Starting CDEmu daemon. Jan 19 23:22:50 xps cdemu-daemon[22667]: Starting CDEmu daemon with following parameters: Jan 19 23:22:50 xps cdemu-daemon[22667]: - config file: /home/kapper/.config/cdemu-daemon (exists: 0) Jan 19 23:22:50 xps cdemu-daemon[22667]: - num devices: 1 Jan 19 23:22:50 xps cdemu-daemon[22667]: - control device: /dev/vhba_ctl Jan 19 23:22:50 xps cdemu-daemon[22667]: - audio driver: null Jan 19 23:22:50 xps cdemu-daemon[22667]: - bus type: session Jan 19 23:22:50 xps cdemu-daemon[22667]: - default CDEmu debug mask: 0x0 Jan 19 23:22:50 xps cdemu-daemon[22667]: - default libMirage debug mask: 0x0 Jan 19 23:22:50 xps cdemu-daemon[22667]: cdemu0: Kernel I/O: failed to open control device /dev/vhba_ctl:> Jan 19 23:22:50 xps cdemu-daemon[22667]: cdemu: Daemon: failed to start device #0! Jan 19 23:22:50 xps cdemu-daemon[22667]: cdemu: Daemon: failed to create device! Jan 19 23:22:50 xps cdemu-daemon[22667]: Daemon initialization and start failed! Jan 19 23:22:50 xps systemd[2369]: cdemu-daemon.service: Main process exited, code=exited, status=255/EXC> Jan 19 23:22:50 xps systemd[2369]: cdemu-daemon.service: Failed with result 'exit-code'. Jan 19 23:22:50 xps systemd[2369]: Failed to start CDEmu daemon. -- Reboot -- Jan 20 12:16:44 xps systemd[2456]: Starting CDEmu daemon. Jan 20 12:16:44 xps cdemu-daemon[3156]: Starting CDEmu daemon with following parameters: Jan 20 12:16:44 xps cdemu-daemon[3156]: - config file: /home/kapper/.config/cdemu-daemon (exists: 0) Jan 20 12:16:44 xps cdemu-daemon[3156]: - num devices: 1 Jan 20 12:16:44 xps cdemu-daemon[3156]: - control device: /dev/vhba_ctl Jan 20 12:16:44 xps cdemu-daemon[3156]: - audio driver: null Jan 20 12:16:44 xps cdemu-daemon[3156]: - bus type: session Jan 20 12:16:44 xps cdemu-daemon[3156]: - default CDEmu debug mask: 0x0 Jan 20 12:16:44 xps cdemu-daemon[3156]: - default libMirage debug mask: 0x0 Jan 20 12:16:44 xps cdemu-daemon[3156]: cdemu0: Kernel I/O: failed to open control device /dev/vhba_ctl: > Jan 20 12:16:44 xps cdemu-daemon[3156]: cdemu: Daemon: failed to start device #0! Jan 20 12:16:44 xps cdemu-daemon[3156]: cdemu: Daemon: failed to create device! Jan 20 12:16:44 xps cdemu-daemon[3156]: Daemon initialization and start failed! Jan 20 12:16:44 xps systemd[2456]: cdemu-daemon.service: Main process exited, code=exited, status=255/EXC> Jan 20 12:16:44 xps systemd[2456]: cdemu-daemon.service: Failed with result 'exit-code'. Jan 20 12:16:44 xps systemd[2456]: Failed to start CDEmu daemon. Attempting to start gcdemu manually produces this error
Daemon autostart failed. Error: g-io-error-quark: Error calling StartServiceByName for net.sf.cdemu.CDEmuDaemon: Timeout was reached (24) Attempting to start the daemon manually produces this error
kapper@xps:~$ cdemu-daemon Starting CDEmu daemon with following parameters: - config file: (null) (exists: 0) - num devices: 1 - control device: /dev/vhba_ctl - audio driver: null - bus type: session - default CDEmu debug mask: 0x0 - default libMirage debug mask: 0x0 cdemu0: Kernel I/O: failed to open control device /dev/vhba_ctl: No such file or directory! cdemu: Daemon: failed to start device #0! cdemu: Daemon: failed to create device! Daemon initialization and start failed! Not really sure where to go from here, any help would be appreciated. Let me know if any further information is needed, I’d be happy to run some commands or tests and provide output.
kapper@xps:~$ uname -a Linux xps 5.11.0-46-generic #51~20.04.1-Ubuntu SMP Fri Jan 7 06:51:40 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux The text was updated successfully, but these errors were encountered:
gnome-terminal fails to start (timed out)
I just upgraded from Ubuntu 16.04 to 18.04. My workflow is to connect from Windows using VcXsrv to Ubuntu (ssh with X tunneling), starting a xterm on Ubuntu. Inside the xterm I am typing gnome-terminal to get a gnome-terminal. Since the upgrade this is not working anymore. I am getting
$ gnome-terminal # Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. # Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Fehler beim Aufruf von StartServiceByName für org.gnome.Terminal: Zeitüberschreitung wurde erreicht $ LANG=en_US.utf8 gnome-terminal # Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. # Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached - sudo gnome-terminal works
- gnome-terminal works when run in a xterm when locally logged in on the PC
- when I am also logged in locally on the PC then gnome-terminal in the remote session’s xterm opens a gnome-terminal on the local session on the PC (still getting the first error line about registering with accessibility bus)
- when I am also logged in over rdp (Windows network connection) then a gnome-terminal in the ssh session opens a gnome-terminal in the xrdp session
- when I login over rdp (Windows network connection), logoff there, then gnome-terminal can open a gnome-terminal
What can I do to get gnome-terminal in a remote session’s xterm to work?
3 Answers 3
Identical issue, found the solution.
Running ‘tail -f /var/log/syslog’ in a 2nd terminal when testing in the first terminal gives the following when I launch gnome-terminal after ‘sudo bash’:
Mar 23 10:11:59 X399-DESIGNARE-EX dbus-daemon[2584]: [session uid=0 pid=2582] Activating service name='org.gnome.Terminal' requested by ':1.6' (uid=0 pid=2929 comm="/usr/bin/gnome-terminal.real " label="unconfined") Mar 23 10:11:59 X399-DESIGNARE-EX gnome-terminal-[2934]: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-GAXcx1c8OL: Connection refused Mar 23 10:11:59 X399-DESIGNARE-EX dbus-daemon[2584]: [session uid=0 pid=2582] Successfully activated service 'org.gnome.Terminal' Mar 23 10:11:59 X399-DESIGNARE-EX gnome-terminal-[2934]: The owner of /home//.config/ibus/bus is not root! I get the following when running gnome-terminal as myself:
Mar 23 10:16:30 X399-DESIGNARE-EX dbus-daemon[2564]: [session uid=1000 pid=2564] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.4' (uid=1000 pid=2959 comm="/usr/bin/gnome-terminal.real " label="unconfined") Mar 23 10:16:30 X399-DESIGNARE-EX systemd[2435]: Starting GNOME Terminal Server. Mar 23 10:16:30 X399-DESIGNARE-EX systemd[2435]: gnome-terminal-server.service: Main process exited, code=exited, status=10/n/a Mar 23 10:16:30 X399-DESIGNARE-EX gnome-terminal-server[2962]: Unable to init server: Could not connect: Connection refused Mar 23 10:16:30 X399-DESIGNARE-EX gnome-terminal-server[2962]: Failed to parse arguments: Cannot open display: Mar 23 10:16:30 X399-DESIGNARE-EX systemd[2435]: gnome-terminal-server.service: Failed with result 'exit-code'. Mar 23 10:16:30 X399-DESIGNARE-EX systemd[2435]: Failed to start GNOME Terminal Server. . after a lot of digging I finally found gnome-terminal not starting, which indicated there is an issue with dbus not refreshing its environment when services get requested from non-root. The following steps work around the problem:
#!/usr/bin/env bash dbus-update-activation-environment —systemd —all gnome-terminal &
Please do NOT delete an answer that provides additional detail for the problem. What you deleted was not any violation of the posting guidelines, and provided substantial additional information for anyone trying to track down the solution. This answer does not provide that additional information and I am disinclined to go through the effort of recovering it.
This answer solves the problem.