Gentoo Archives: gentoo-user

From: Maxim Wexler <maxim.wexler@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: was Re: X crashes with nvidia-173 driver now X crash on eee w/intel driver
Date: Fri, 06 Nov 2009 20:59:11
Message-Id: a0811460911061259l44769a3bja86112378a2edec2@mail.gmail.com
In Reply to: [gentoo-user] Re: was Re: X crashes with nvidia-173 driver now X crash on eee w/intel driver by walt
1 I assumed you meant me to run /usr/bin/dbus-daemon --system. So I did:
2
3 Failed to start message bus: The pid file "/var/run/dbus.pid" exists,
4 if the message bus in not running , remove this file.
5
6 file duly removed and re-ran above command which did nothng visible
7 just returned the cursor to the next line. Is that the expected
8 behaviour.
9
10 BTW, overnight I upgraded to mozilla-firefox-3.5.1, and was surfing
11 away this morning when the screen went totally white -- same story.
12
13 Now my default desktop is down with non-functioning nvidia drivers and
14 the mobile is afflicted with sudden crashes. I dug up this K6-500,
15 2.6.19 with firefox-2.0. analog riva video and it's humming along
16 quite nicely :)
17
18
19
20 On 11/6/09, walt <w41ter@×××××.com> wrote:
21 > On 11/05/2009 09:06 PM, Maxim Wexler wrote:
22 >>>
23 >>> Will see how it works.
24 >>
25 >> Not very well. About an hour after emerging the 2.9.1 drivers the
26 >> screen went black and I had to reboot to get back to the desktop. I
27 >> notice it only seems to happen while scrolling a window in firefox.
28 >> I've left the unit on overnight with no problem. When I get back to
29 >> ctrl-alt-f1. there is this msg repeated down the console.
30 >>
31 >> Gdk - Warning*** XID collision trouble ahead.
32 >>
33 >> FWIW, there is this tidbit in the boot console:
34 >> [...]
35 >> * Checking battery state...
36 >> error: libhal_ctx_set_dbus_connection:
37 >> org.freedesktop.DBus.Error.FileNotFound:
38 >> Failed to connect to socket /var/run/dbus/system_bus_socket: No such
39 >> file or directory
40 >
41 > Hm. You should have that socket. Do you have a system dbus running?:
42 >
43 > 3387 ? Ss 0:00 /usr/bin/dbus-daemon --system
44 >
45 >
46 >

Replies