When I update Archlinux my Virtualbox VM is unable to start GNOME (after the update). Before installing the updates, I was notified that a few gnome packages have changed (e.g.: gnome-extras moved to extras/gnome-extras or something like that). When I confirm and proceed the VM seems to be unable to start GNOME, it tries a jew times and stops.
I know right now this isn’t much to go on, but I’m currently not at this PC and I decided to go ahead and open the thread anyway. I figured (hoped) someone might know what’s wrong or had a similar problem. In any case, tomorrow I can go ahead and post my X11 log.
Yeah I’m able to boot into console, but startx doesn’t work either. However, I’m currently trying to updating my installed packages one at a time to find the culprit. (Previously, I excluded GNOME, but apparently GNOME does not cause this issue. It might be gdm, libgdm, virtualbox-guest-modules-arch, or mesa. But I’m not sure. ) I’ll update this thread with the corresponding log files once I’ve found the culprit.
Possible culprtis (e.g. currently not-updated packages) are:
@FaunCB I might as well just try that next. When I last tried to purge gnome though pacman -Rns gnome it complained about dependencies and didn’t let me do it though. But I’ll try again.
Honestly… this kind of thing should be something to expect with arch and something you will have to deal with on occasion. It’s not necessary a gnome problem.
FYI If any none is running a AMD or ATI FirePro Professional add in GPU the amdgpu-pro driver installation package provided on the amd/ati linux Download page is antiquated in that it still requires some legacy i386 package.i386 multi-architecture support being abandon in favor of the pure x86_64 support dy most Linux distributions you might want to consider NVidia asve more of a grasp on correct implementation and coordination driver development and deployment wise in the Linux community.