[SOLVED?] gcdemu not launching

I screwed something up, as usual.
I wanted to try out XFCE4. Installed it, didn't like it, removed it (all using Synaptic). Also cleaned out using:

Code:

sudo apt-get remove --auto-remove xfce4
sudo apt-get purge --auto-remove xfce4

Maybe that was the mistake. GCDEmu didn't launch after that. So I removed GCDemu (Synaptic) and then reinstalled using:

Code:

sudo add-apt-repository ppa:cdemu/ppa
sudo apt-get update
sudo apt-get install gcdemu cdemu-client

Still no luck at launch. System monitor shows cdemu-daemon and gcdemu running but GCDemu doesn't launch (although I hear the beep it gives off when it launches).

Try doing:

Code:

sudo apt dist-upgrade

This command looks for any missing dependencies since last update for apps following kernel updates.

Thanks, Swarf. It upgraded some. Unfortunately, still no launch.

If you try launching from the terminal, does the terminal list any errors?

@Swarf:
Posting output, if it helps:
****************
The following packages will be upgraded:
gir1.2-nautilus-3.0 gnome-calculator libnautilus-extension1a nautilus
nautilus-data xserver-common xserver-xephyr xwayland
8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 3,100 kB of archives.
After this operation, 28.7 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 nautilus amd64 1:3.26.4-0~ubuntu18.04.5 [809 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 nautilus-data all 1:3.26.4-0~ubuntu18.04.5 [68.9 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnautilus-extension1a amd64 1:3.26.4-0~ubuntu18.04.5 [15.1 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 gir1.2-nautilus-3.0 amd64 1:3.26.4-0~ubuntu18.04.5 [5,532 B]
Get:5 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 gnome-calculator amd64 1:3.28.2-1~ubuntu18.04.3 [388 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 xserver-common all 2:1.19.6-1ubuntu4.4 [27.3 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 xserver-xephyr amd64 2:1.19.6-1ubuntu4.4 [923 kB]
Get:8 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 xwayland amd64 2:1.19.6-1ubuntu4.4 [863 kB]
Fetched 3,100 kB in 3s (1,079 kB/s)
(Reading database ... 309053 files and directories currently installed.)
Preparing to unpack .../0-nautilus_1%3a3.26.4-0~ubuntu18.04.5_amd64.deb ...
Unpacking nautilus (1:3.26.4-0~ubuntu18.04.5) over (1:3.26.4-0~ubuntu18.04.4) ...
Preparing to unpack .../1-nautilus-data_1%3a3.26.4-0~ubuntu18.04.5_all.deb ...
Unpacking nautilus-data (1:3.26.4-0~ubuntu18.04.5) over (1:3.26.4-0~ubuntu18.04.4) ...
Preparing to unpack .../2-libnautilus-extension1a_1%3a3.26.4-0~ubuntu18.04.5_amd64.deb ...
Unpacking libnautilus-extension1a:amd64 (1:3.26.4-0~ubuntu18.04.5) over (1:3.26.4-0~ubuntu18.04.4) ...
Preparing to unpack .../3-gir1.2-nautilus-3.0_1%3a3.26.4-0~ubuntu18.04.5_amd64.deb ...
Unpacking gir1.2-nautilus-3.0:amd64 (1:3.26.4-0~ubuntu18.04.5) over (1:3.26.4-0~ubuntu18.04.4) ...
Preparing to unpack .../4-gnome-calculator_1%3a3.28.2-1~ubuntu18.04.3_amd64.deb ...
Unpacking gnome-calculator (1:3.28.2-1~ubuntu18.04.3) over (1:3.28.2-1~ubuntu18.04.1) ...
Preparing to unpack .../5-xserver-common_2%3a1.19.6-1ubuntu4.4_all.deb ...
Unpacking xserver-common (2:1.19.6-1ubuntu4.4) over (2:1.19.6-1ubuntu4.3) ...
Preparing to unpack .../6-xserver-xephyr_2%3a1.19.6-1ubuntu4.4_amd64.deb ...
Unpacking xserver-xephyr (2:1.19.6-1ubuntu4.4) over (2:1.19.6-1ubuntu4.3) ...
Preparing to unpack .../7-xwayland_2%3a1.19.6-1ubuntu4.4_amd64.deb ...
Unpacking xwayland (2:1.19.6-1ubuntu4.4) over (2:1.19.6-1ubuntu4.3) ...
Setting up xserver-common (2:1.19.6-1ubuntu4.4) ...
Setting up nautilus-data (1:3.26.4-0~ubuntu18.04.5) ...
Setting up gnome-calculator (1:3.28.2-1~ubuntu18.04.3) ...
Setting up xserver-xephyr (2:1.19.6-1ubuntu4.4) ...
Setting up libnautilus-extension1a:amd64 (1:3.26.4-0~ubuntu18.04.5) ...
Setting up xwayland (2:1.19.6-1ubuntu4.4) ...
Setting up gir1.2-nautilus-3.0:amd64 (1:3.26.4-0~ubuntu18.04.5) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.2+zorin1) ...
Processing triggers for libglib2.0-0:i386 (2.58.1-2+zorin1) ...
Processing triggers for libglib2.0-0:amd64 (2.58.1-2+zorin1) ...
Processing triggers for libc-bin (2.28-0ubuntu1+zorin4) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Setting up nautilus (1:3.26.4-0~ubuntu18.04.5) ...
**************



@Aravisian:
I typed gcdemu and got output below:
*************
AppIndicator tray icon mode
(gcdemu:4851): Gtk-WARNING **: 08:39:48.889: Failed to fetch network locations: Timeout was reached
<cursor stays blinking but doesn't return back to the prompt>
***************

Decided to check on dependencies. Went to https://cdemu.sourceforge.io/about/gcdemu/ and went through requirements list. Checked on Synaptic for each of these. Also installed all recommended and suggested packages for each of the requirements. Parenthesized are my best guess on the listed Synaptic packages. Version numbers are last.
CMake 3.10.2-1ubuntu2.18.04.1
IntlTool 0.51.0-5ubuntu1
GetText 0.19.8.1-6ubuntu0.3
Python3 3.6.7-1~18.04
PyGObject (python-gobject-2-dev) 2.28.6-12ubuntu3
GLib (glib-networking) 2.56.0-1
GObject (gobject-introspection) 1.56.1-1
GIO <is it libglib2.0-0 2.58.1-2+zorin1?>
GTK3 GIR (gir1.2-gtk-3.0) 3.22.30-1ubuntu4
GdkPixbuf GIR (gir1.2-gdkpixbuf-2.0) 2.36.11-2

Then removed GCDEmu, rebooted, reinstalled GCDEmu using the terminal. Started through GUI and it works fine.

Thanks to you both.

Glad you are sorted but concerned you are using US server instead of Main Server.

Didn't notice that (and I didn't know it was a problem) until now. I changed to main server and Software Updater is now pumping through a few updates. Should I be doing any additional steps?

No that's fine.

Ok. This makes no sense. I shutdown my laptop and an hour later I booted up again. Now GCDEmu again doesn't launch. I'm lost.

I removed and purged GCDemu. Do you know if it is safe to remove the 4 packages in the screenshot, purge and reinstall?

carmar wrote:Do you know if it is safe to remove the 4 packages in the screenshot, purge and reinstall?

It is safe. Those packages are all related to the program giving you trouble and they are not entangled with shared object libraries.

Thanks.
Removing and reinstalling didn't make a difference.

Would deleting these help or its not advised?

carmar wrote:Would deleting these help or its not advised?

Those are docs for the app; deleting them will not harm you or your computer in any way as they would be replaced with the reinstallation. However, removing them MAY help ( I do not know) if they have information that is causing a conflict that needs to be replaced.
I have never used GcDemu because I have heard of its many issues over the years. So, I don't really know enough to help resolve your main issue.
But you did get really close when you uninstalled and reinstalled before. I wonder what threw that off...
When I remove an app, I usually use the 'apt-get remove --purge' command.

Thank you.

Yeah, that one is a mystery. All I did was install a couple of games and a shutdown.

I deleted the 4 cdemu files. Installed gcdemu and now it launches again. In case this goes south on me again, which of the two recommended packages here do you prefer? Gisomount or Pismotech? I tried Acetone - its nice but PlayOnLinux doesn't recognize mounted images.

Update: Rebooted to check. Yep. It does not like reboot. Same error message like the only other time it gave me an error message:
"AppIndicator tray icon mode

(gcdemu:1887): Gtk-WARNING **: 21:12:36.564: Failed to fetch network locations: Timeout was reached"

carmar wrote:Thank you.

Yeah, that one is a mystery. All I did was install a couple of games and a shutdown.

I deleted the 4 cdemu files. Installed gcdemu and now it launches again. In case this goes south on me again, which of the two recommended packages here do you prefer? Gisomount or Pismotech? I tried Acetone - its nice but PlayOnLinux doesn't recognize mounted images.

Update: Rebooted to check. Yep. It does not like reboot. Same error message like the only other time it gave me an error message:
"AppIndicator tray icon mode

(gcdemu:1887): Gtk-WARNING **: 21:12:36.564: Failed to fetch network locations: Timeout was reached"

I would aim for Gisomount- hopefully others give their input on that, too.
Could you try running

Code:

cdemu-daemon

and then posting any/all errors that shows?

This suggests that one of the start ups is not auto-startup. You might take a look in your /dev folder and check that vhba_ctl is present there.

vhba_ctl is present but 0 byte size.

Terminal output (stays running) -
Starting CDEmu daemon with following parameters:
- num devices: 1
- control device: /dev/vhba_ctl
- audio driver: null
- bus type: session
- default CDEmu debug mask: 0x0
- default libMirage debug mask: 0x0

carmar wrote:vhba_ctl is present but 0 byte size.

Can you try in terminal running it with Root permissions and see if anything changes?
And in terminal, can you try

Code:

sudo modprobe vhba

I ran

Code:

sudo gcdemu

. I heard a beep as every other time I launch it. But every other time I see cdemu-daemon and gcdemu in the System Monitor. This time, neither of them showed up. In the terminal I got the same "AppIndicator tray icon mode" message.

Code:

sudo modprobe vhba

just returned me back to the prompt.

carmar wrote:I ran

Code:

sudo gcdemu

. I heard a beep as every other time I launch it. But every other time I see cdemu-daemon and gcdemu in the System Monitor. This time, neither of them showed up. In the terminal I got the same "AppIndicator tray icon mode" message.

Code:

sudo modprobe vhba

just returned me back to the prompt.

Ok, so probably not a permissions issue.
I still wonder if your vhba_ctl is not auto-starting and it worries me why it said zero bytes.
My lack of experience with this app is the biggest bane to offering helpful suggestions at this point.

No worries. Thanks for trying. I'll try Gisomount some time.

I know I should reinstall the OS but Balena takes so loooong to make a bootable USB, that its easier for me to remove GCDEmu, wipe the files and reinstall. This is one instance where I have it running (until I reboot and then it refuses to start) but I noticed one thing in the terminal.
I keep getting a warning at various time intervals. "Gtk-Message: 19:53:16.689: GtkDialog mapped without a transient parent. This is discouraged."
Looked it up on the internet and it seems its just a warning, not an error. Thought I'd post it, for what its worth. I understand if the information is useless to resolve the matter but just documenting the best I can.

This may be a resolution. I got it to start up for 3 successive boots. I'm assuming that means it will continue to do so as long as I keep doing what I'm doing (steps 4 & 5, below).

Step:
1. If GCDEmu is not starting up, search for "cdemu" in Synaptic and uninstall all results (complete removal).
2. Do a search (including root) for "cdemu" and remove all folders and files. I had to use the following (with root access):

Code:

rm -rf /etc/apt/trusted.gpg.d/cdemu_ubuntu_ppa.gpg
rm -rf /etc/apt/sources.list.d/cdemu-ubuntu-ppa-bionic.list
rm -rf /etc/apt/sources.list.d/cdemu-ubuntu-ppa-bionic.list.save
rm -rf /var/lib/apt/lists/ppa.launchpad.net_cdemu_ppa_ubuntu_dists_bionic_InRelease
rm -rf /var/lib/apt/lists/ppa.launchpad.net_cdemu_ppa_ubuntu_dists_bionic_main_binary-i386_Packages
rm -rf /var/lib/apt/lists/ppa.launchpad.net_cdemu_ppa_ubuntu_dists_bionic_main_binary-amd64_Packages
rm -rf /var/lib/apt/lists/ppa.launchpad.net_cdemu_ppa_ubuntu_dists_bionic_main_i18n_Translation-en


3. Reinstall using:

Code:

sudo add-apt-repository ppa:cdemu/ppa
sudo apt-get update
sudo apt-get install gcdemu cdemu-client

4. When starting, only use the terminal. Thanks to Aravisian for suggesting this a while back.
5. Leave it running throughout your session and shutdown computer (if you do shutdown) without exiting either terminal or gcdemu. This also means your terminal will be tied up with it (at least mine is) the whole time it is on. I dare not use Ctrl+C but braver souls are welcome to.

Hopefully this helps anyone else if they have problems. Or at least if they're as lazy as me to reinstall the system even though all files are backed up and I could just use the "something-else" option to only replace root files.