A connection to the bus can’t be made: booting issue [solved]

Hello and welcome back to “A Habit of Learning”! Couldn’t write for so long due to repetitive health issues then exams then an exciting chess tournament then a bit of LaTex and cookiecutter like tools and then here I am. Before I write about anything else of what all I have been going through these days, I feel there is a need of THIS blog post as I couldn’t find many solutions over the web regarding the issue.

Recently, I went through this issue while installing Ubuntu 18.04 in my relative’s laptop.

1. Machine Specs


2. Problem

* Type: Booting time issue
* Effect: Unable to boot completely
* Error Message:

(gvfsd-metadata:743): GUdev-CRITICAL **: 00:18:28:319: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
A connection to the bus can't be made

* Complete error: Image shown below [while trying Linux Mint (same issue was there in Ubuntu 16.04 and 18.04).


* Brief Explanation: Tried to boot my <GNU/Linux distro> and initial <seconds> appear to be normal booting. Then comes a black screen and nothing happen thereafter except a message shown repeatedly: “A connection to the bus can’t be made”. I waited for around <minutes> but system was unable to boot completely.

3. Cause

Can’t say what the actual reason might be. But as far as I searched over the web this could arise due to dedicated GPU your machine has (at least it was in my case).


There are 2 possible scenarios I have experienced which are as follows:

1. In booting while trying Ubuntu 18.04, Mint – Cinnamon with Live USB/CD
2. In booting after installation.

One of my friend also had the same issue while shutting down his Ubuntu 18.04. :p

4. Solutions

A couple of solutions I tried to get rid of this issue, I can’t say which may work for you πŸ™‚

One of my friend solved this issue after upgrading his OS (from Ubuntu 16.04 to 18.04).

So I tried it first. I installed Ubuntu 16.04 and then upgraded it to 18.04. But that didn’t work instead became the cause of error discussed in my next post. All solutions listed below and in successive posts (2nd) and (3rd)Β  of this series are done on Ubuntu 18.04.

4.1. Arrow Keys [Before/After Installation]

Appear to be silly, but worked for me πŸ™‚
After 5-10 seconds of normal booting, I tried to hit arrow keys up, down, left, right – repeat 2-3 times and 2-3 times pressing Enter key (More than a solution it appears to be an act of frustration, which exactly it was). And viola! My laptop booted completely after 30-70 seconds. But problem persisted in next boot. So, it is not a permanent solution but surprisingly may work as a temporary work around.

This ^^ is not be the best solution. Of course. Let’s see some other alternative that worked for some people.

4.2. Setting Nomodeset [Before/After Installation]

The reason being that


The newest kernels have moved the video mode setting into the kernel. So all the programming of the hardware specific clock rates and registers on the video card happen in the kernel rather than in the X driver when the X server starts.. This makes it possible to have high resolution nice looking splash (boot) screens and flicker free transitions from boot splash to login screen. Unfortunately, on some cards this doesn’t work properly and you end up with a black screen. Adding the nomodeset parameter instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded.

source: https://ubuntuforums.org/showthread.php?t=1613132

This solution also worked for me. To setup option nomodeset there are 2 cases:

4.2.1. While trying OS with Live USB/CD

In this case while in booting menu: Press F6 and choose “nomodeset”. And you would be able to boot properly. I did this and installed the OS with a hope that the issue will go away after complete installation. (but it didn’t)

Screenshot_2019-02-04 mostrar-opciones-arranque-ubuntu-li png (PNG Image, 465 Γ— 308 pixels)

4.2.2. While booting after installation.

As written in this link https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-already-installed-ubuntu/:

  • While booting press –> Shift (to go to grub menu)
  • While in boot menu –> Press ‘e’
  • Find the line start with `linux`
  • Replace -> “quiet splash” with “nomodeset” or add “nomodeset” before “quiet splash”
  • Press –> CTRL + X to boot

Once the booting is completed you need to setup this “nomodeset” permanently in your grub configuration using the instruction of Coldfish in this answer https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-already-installed-ubuntu/ which are:

sudo vim /etc/default/grub

and then add nomodeset to GRUB_CMDLINE_LINUX_DEFAULT:

GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"

And then save and exit :x , then simply run:

sudo update-grub

Now, reboot and you are good to go. This also worked for me. But still, πŸ™‚ nomodeset is a temporary solution which simply avoids the cause of solution. It doesn’t solve the cause in itself.

4.3. Update Distro [After Installation]

Simply run:

sudo apt update
sudo apt upgrade
sudo apt dist-upgrade
# And just to avoid any doubt
sudo apt full-upgrade

I did all 3 solutions listed above. And finally, I was not getting the error “A Connection to the bus can’t be made” in successive booting.

Next: [drm:radeon_init[radeon]] ERROR No UMS support in radeon module!
Next to Next: Failed toconnect to lvmetad: booting issue

5. Conclusion

I knew it, that “nomodeset” is just a temporary solution. So, I tried to boot again only with default options i.e “quiet splash”. And yes, I didn’t get the previous error line! (might be during the update the problem got solved)

But for me, it didn’t come with a clear win because now, I was dealing with the second issue in line. And this time the error was:

[drm:radeon_init[radeon]] ERROR No UMS support in radeon module!

With an hour of research I was able to solve this error as well. And I think the solution to this new error is the permanent solution of that previous one. Why do I think so, and what is the solution to this new error? Will soon write my next post unveiling the same.

I hope this post will help someone. And if you know any other solution regarding the same issue, please do write in the comments section below, that might also help someone else.

Thanks for reading!

3 thoughts on “A connection to the bus can’t be made: booting issue [solved]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s