Chromium fails to start with white flash on screen

14.1-RELEASE-p6

I remember updating the chromium package a day or two ago, and I'm pretty sure I powered down my desktop system at least once--possibly twice--since then. I use my usual shortcut key in i3-wm to start chromium but, this morning, I only got a white flash of the screen.

All my other graphical programs (Firefox and LibreOffice) still work normally. I tried uninstalling/installing chromium but that didn't fix it. So then I tried starting it from the command line and got this:

Code:
[2705:56740697686784:1217/120738.152714:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[2705:56740697686784:1217/120738.260490:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2705:56740697686784:1217/120738.260572:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2705:56740697686784:1217/120738.260610:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2705:56740697686784:1217/120738.260627:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2705:56740697686784:1217/120738.260639:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2705:56740697686784:1217/120738.276448:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2705:56740697686784:1217/120738.319646:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2705:56740697686784:1217/120738.319779:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2705:56740697677824:1217/120738.369226:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
[2705:56740720721920:1217/120738.423313:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2705:56740697686784:1217/120738.443895:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2705:56740697686784:1217/120738.443989:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2705:56740809675776:1217/120738.636381:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[2705:56740809675776:1217/120738.636734:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[2705:56740809675776:1217/120738.636886:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[2705:56740809675776:1217/120738.636946:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[2705:56740809675776:1217/120738.637220:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[2705:56740697677824:1217/120738.666518:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
[2705:56740720723712:1217/120738.666669:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2705:56740697677824:1217/120738.759448:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
[2705:56740720721920:1217/120738.759524:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2705:56740697677824:1217/120738.766664:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
[2705:56740720723712:1217/120738.766779:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2705:56740697677824:1217/120738.774999:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
[2705:56740720721920:1217/120738.775358:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2705:56740697677824:1217/120738.785187:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type:
Bus error

I'm not sure if reinstalling dbus would be a solution but what would cause this?
 
I picked up latest quarterly update to chromium this morning, I'm running windowmaker starting I get the type of errors but it starts fine. I think the errors relate to maybe a dbus process not running; I don't think they should be fatal.

Looks like the default config directory is $HOME/.config/chromium, have you tried moving that out of the way then starting? Basically emulate "first time ever start"?
 
I looked in /var/log/messages and see a bunch of pulseaudio errors which I'm not familiar with.

mer Do you mean rename the chromium directory and restart?
 
I looked in /var/log/messages and see a bunch of pulseaudio errors which I'm not familiar with.

mer Do you mean rename the chromium directory and restart?
Yes. stop all running instances of chromium && mv $HOME/.config/chromium $HOME/.config/chromium.OLD && start chromium.

I've found it the quickest way on all browsers to check "did I muck up something in configuration"
 
mer Yes. Thanks, that worked. I just don't understand what could have happened to cause all this.
Check any plugins you may have installed. I only use Chromium for stuff related to work, firefox for pretty much everything else. But I tend to avoid a lot of plugins, I'll go through settings related to security and manually set.
I don't recall the exact versioning but from quarterly it was only the last 2 numbers (I think related to build numbers or checkin stuff) so it should have only been minor update.
Now it becomes the fun stuff of trying to import things or changing settings to find out what the problem was.
 
The first place to start is the command line.
Run chromium from there and see what is the problem. What is missing.
 
I did try to run it from the command line but it wouldn't start.

As far as dbus is concerned, I don't recall the exact reason why I don't enable that anymore--and it's been disabled for many months--other than nothing I use needs it. Then again, something is trying to, thus the errors I presume, and I should probably look into it.

All is fine now. I was able to import my passwords and bookmarks cause I back them up every day. One thing I always forget to do is keep track of which extensions I use. They're web dev related and I always forget their names.
 
Back
Top