Oh wait, just rebooted, the message is still there but a few lines
below there is this:
*Starting D-BUS system messagebus . . .
which I remember seeing before but forgot to mention. I ran
dbus-daemon again as before with the same outcome.
On 11/6/09, Maxim Wexler <email@example.com> wrote:
> I assumed you meant me to run /usr/bin/dbus-daemon --system. So I did:
> Failed to start message bus: The pid file "/var/run/dbus.pid" exists,
> if the message bus in not running , remove this file.
> file duly removed and re-ran above command which did nothng visible
> just returned the cursor to the next line. Is that the expected
> BTW, overnight I upgraded to mozilla-firefox-3.5.1, and was surfing
> away this morning when the screen went totally white -- same story.
> Now my default desktop is down with non-functioning nvidia drivers and
> the mobile is afflicted with sudden crashes. I dug up this K6-500,
> 2.6.19 with firefox-2.0. analog riva video and it's humming along
> quite nicely
> On 11/6/09, walt <firstname.lastname@example.org> wrote:
>> On 11/05/2009 09:06 PM, Maxim Wexler wrote:
>>>> Will see how it works.
>>> Not very well. About an hour after emerging the 2.9.1 drivers the
>>> screen went black and I had to reboot to get back to the desktop. I
>>> notice it only seems to happen while scrolling a window in firefox.
>>> I've left the unit on overnight with no problem. When I get back to
>>> ctrl-alt-f1. there is this msg repeated down the console.
>>> Gdk - Warning*** XID collision trouble ahead.
>>> FWIW, there is this tidbit in the boot console:
>>> * Checking battery state...
>>> error: libhal_ctx_set_dbus_connection:
>>> Failed to connect to socket /var/run/dbus/system_bus_socket: No such
>>> file or directory
>> Hm. You should have that socket. Do you have a system dbus running?:
>> 3387 ? Ss 0:00 /usr/bin/dbus-daemon --system