ISO 18.1.5 - VirtualBox loading time - 'black screen of death'

With the latest ISO 18.1.5 I'm only getting a black screen when choosing VBoxSVGA.
Same for you guys?


Edit by @linux-aarhus
The comments emerged to a thread on insane loading when booting the ISO.

Which ISO are you testing?

VirtualBox has a bad habit of discouraging the use of VBoxSVGA with Linux guests but not working? That is new.

Did you see this topic?

host sys is on testing branch with virtualbox 6.1
Tried it only with the 18.1.5 XFCE iso so far.

It does work with VMSVGA, but as you said earlier that won't allow resizing the window from the host (which is why I want to use VBoxSVGA... It always worked in the past)

Official Xcfe 18.1.5 - manjaro-xfce-18.1.5-minimal-191229-linux54.iso


Just testing - xfce - black screen.

Switch to TTY - the system is loaded - just not X

Locate /var/log/mhwd-live.log

All virtualbox modules is detected and installed

Starting vboxservice

To be updated ....

While checking and returning - xfce has loaded - it just took some time.

And seamless (resizing) window is working

Currently installing archlinux, maybe I can contribute a fix for this upstream, especially because I know exactly what causes resizing to be broken with VMSVGA.

1 Like

Indeed. Just took like 10 minutes or so to come up. (Actually ~5 minutes)
Installing now. Let's see what happens after install.

edit Once installed it's ok. Comes up immediately.

For a Manjaro (and Arch) guest on a Win10 Host, I have used VBoxVGA with good results (meaning I get auto-resizing, but I have not tested against demanding games).

I have noted that assigning a single CPU core and 1GB RAM - which is the default for an Arch based VM - it takes forever to load.

At least two CPU cores and 2GB RAM - then it works.


Manjaro is special - because I have been playing with Arch ISO and it is quite different.

You mean with 2 cores and 2 GB RAM it comes up immediately?

I have given it 4 cores and 4 GB actually. With that it takes 5 minutes.

Not immediately - it took it long enough - when I tried - but eventually it came on while I was on a TTY - so - maybe 30-60s (minimal XFCE).

The Arch based PacBang I am playing with - now that is different - much faster.

I'll give it a try with the minimal one, but something seems to be wrong with the regular ISO.
During that 5 minutes, there is like 0 cpu usage for at least 4 minutes.

edit minimal also takes ages. maybe something with my machine then? will try an older ISO just to see.

edit 2 XFCE 18.1.4 comes up within 30 seconds...

Watching water boiling you realize how long it takes.

There is definetely something wrong - the minimal Xfce ISO has now been loading for +4 minutes without any progress - 4m45s - to load - that is wrong.

Using the same virtual machine - using PacBang 2020.01 ISO - boots to X in 25s.

(Both using kernel 5.4)

1 Like

I split this to a separate topic

1 Like

Tested KDE 18.1.5 minimal: Also affected
Gnome minimal seems to be ok though.

I just recalled a link posted earlier to a article on kernel 5.5 and problems when snapd support is enabled. We could try disabling snap support in the kernel commandline. I just have to locate the post :slight_smile:


Update 2: Building an ISO using Openbox profile exhibit same - insane - ISO loading time. (manjaro-openbox-18.1.5-unstable-minimal-200104-linux54.iso)

This ISO is build using manjaro-tools-git r2852-699d178-1 and unstable branch.

Something is definitely wrong!

Tried that. Same thing.

Now looking into the logs it seems there is an issue with the notifications service.
It fails to start twice and service_start_timeout=120000ms, so we are 4 minutes.

Jan 04 15:51:12 manjaro tlp[1146]: Setting battery charge thresholds...done.
Jan 04 15:51:12 manjaro systemd[1]: Started TLP system startup/shutdown.
Jan 04 15:51:12 manjaro audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=tlp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 04 15:51:12 manjaro systemd[1]: Startup finished in 6.859s (kernel) + 12.811s (userspace) = 19.670s.
Jan 04 15:51:12 manjaro systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jan 04 15:51:12 manjaro audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succes>
Jan 04 15:51:31 manjaro systemd[1]: systemd-hostnamed.service: Succeeded.
Jan 04 15:51:31 manjaro audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 04 15:51:31 manjaro kernel: kauditd_printk_skb: 11 callbacks suppressed
Jan 04 15:51:31 manjaro kernel: audit: type=1131 audit(1578153091.813:59): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? t>
Jan 04 15:53:11 manjaro dbus-daemon[1118]: [session uid=1000 pid=1118] Failed to activate service 'org.freedesktop.Notifications': timed out (service_start_timeout=120000ms)
Jan 04 15:53:11 manjaro dbus-daemon[1118]: [session uid=1000 pid=1118] Activating via systemd: service name='org.freedesktop.Notifications' unit='xfce4-notifyd.service' requested by ':1.7' (uid=1000 pid=1284 comm="notify-send VB>
Jan 04 15:53:11 manjaro systemd[1098]: Starting XFCE notifications service...
Jan 04 15:53:11 manjaro xfce4-notifyd[1293]: Unable to init server: Could not connect: Connection refused
Jan 04 15:53:11 manjaro xfce4-notifyd[1293]: cannot open display:
Jan 04 15:53:11 manjaro systemd[1098]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Jan 04 15:53:11 manjaro systemd[1098]: xfce4-notifyd.service: Failed with result 'exit-code'.
Jan 04 15:53:11 manjaro systemd[1098]: Failed to start XFCE notifications service.
Jan 04 15:55:11 manjaro dbus-daemon[1118]: [session uid=1000 pid=1118] Failed to activate service 'org.freedesktop.Notifications': timed out (service_start_timeout=120000ms)
Jan 04 15:55:11 manjaro dbus-daemon[1118]: [session uid=1000 pid=1118] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.16' (uid=1000 pid=1110 comm="xfce4-session " label="unc>
Jan 04 15:55:11 manjaro systemd[1098]: Starting Virtual filesystem service...
Jan 04 15:55:11 manjaro dbus-daemon[1118]: [session uid=1000 pid=1118] Successfully activated service 'org.gtk.vfs.Daemon'
Jan 04 15:55:11 manjaro systemd[1098]: Started Virtual filesystem service.
Jan 04 15:55:11 manjaro kernel: fuse: init (API version 7.31)
Jan 04 15:55:11 manjaro kernel: *** VALIDATE fuse ***
Jan 04 15:55:11 manjaro kernel: *** VALIDATE fuse ***
Jan 04 15:55:11 manjaro systemd[1]: Mounting FUSE Control File System...
Jan 04 15:55:11 manjaro systemd[1]: Mounted FUSE Control File System.
Jan 04 15:55:11 manjaro dbus-daemon[1118]: [session uid=1000 pid=1118] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.19' (uid=1000 pid=1110 comm="xfce4-session " label="uncon>
Jan 04 15:55:11 manjaro systemd[1098]: Starting Accessibility services bus...
Jan 04 15:55:11 manjaro dbus-daemon[1118]: [session uid=1000 pid=1118] Successfully activated service 'org.a11y.Bus'
Jan 04 15:55:11 manjaro systemd[1098]: Started Accessibility services bus.
Jan 04 15:55:11 manjaro at-spi-bus-launcher[1353]: dbus-daemon[1359]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=1110 comm="xfce4-session " label="unconfined")
Jan 04 15:55:11 manjaro at-spi-bus-launcher[1353]: dbus-daemon[1359]: Successfully activated service 'org.a11y.atspi.Registry'
Jan 04 15:55:11 manjaro at-spi-bus-launcher[1353]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jan 04 15:55:11 manjaro systemd[1098]: Started GnuPG cryptographic agent and passphrase cache.

I don't think the notify daemon is at fault here - but I have no idea where else to look.

The funny thing is, that this daemon is starting properly with VMSVGA.
So actually I do suspect it is because of that. (The timing would fit also, like the additional 4 minutes...)

Might not be the root cause though...

Retesting using VMSVGA

  • the same Openbox which took minutes to load - now loads within 30s.
  • the same goes for Xfce

The available driver for VBoxSVGA don't work anymore.

And that is strange because using Arch - it works using VBoxSVGA - but not Manjaro.

So after all - it is a VBoxSVGA vs VMSVGA issue or at least related.

1 Like

same for me

Forum kindly sponsored by