Cliff McDiarmid wrote:
No probs, its running.
?? strange.
Anyway, do people think dbus is the problem?
I still think that that error message is indicating the problem.
When the user space message bus starts up, it should set
DBUS_SESSION_BUS_ADDRESS. To see this, you are going to need to
2009/9/19 Trent Shea trent.s...@gmail.com:
Anyhow... Attached is the last xorg.conf I used.
I had evdev-2.1.3
xorg-server-1.6.1
no HAL or DBUS
hope this helps,
Trent.
Many thanks, it did. Turns out I'd failed to turn on evdev
in the 32-bit kernels on this machine, so I guess it was
On Fri, Sep 18, 2009 at 10:53 PM, William Immendorf
will.immend...@gmail.com wrote:
In my BLFS build, I've also built PAM into it. Well, that also
includes pam_console. But, when I'm done tinkering with PAM, a problem
emerges. /var/run/console/console.lock doesn't exist. It seems
pam_console
On Wednesday 16 September 2009 13:15:29 James Richard Tyrer wrote:
The problem is that you have two startkde scripts on your system and
how this should work is that the PATH should determine which one to use.
However, the KDE session desktop file: kde.desktop (which is in the
directory:
