Hi, Alan. On Sun, Jan 12, 2014 at 01:29:09PM +0200, Alan McKinnon wrote: > On 12/01/2014 12:11, Alan Mackenzie wrote: > >> That should get you a consistent system. Now run xfce. > >> > With luck, it will work as it should. > >> > If not, we can then start the real debugging > > No such luck, as yet. I still get these messages when trying to startx:
> > xfce4-session: GNOME compatibility is enabled and gnome-keyring-daemon > > is found on the system. Skipping gpg/ssh-agent startup. > > env: kdeinit4: No such file or directory > > env: qdbus: No such file or directory > > . Somehow, the remnants of a KDE program are hanging around somewhere. > > I've no idea what qdbus is, or where I've got it configured. I'm getting a bit weary with this issue. Thanks for the help, so far. I spent a lot of Sunday evening trying to locate executables/libraries which still invoke kdeinit4 and qdbus. To no avail. Next bright idea: why don't I emerge these two binaries again? This will surely help me locate the offending binaries, and even if it doesn't, might get my X working again as a workaround. > qdbus comes from qtdbus, it was pulled in by KDE way back when. I've emerged qtdbus, and the "qdbus" error message has gone. But I can't for the life of me locate the package containing kdeinit4. I've looked through /usr/portage/kde-base/, but can't identify the KDE base package I need. equery only works on already emerged packages. Which package contains kdeinit4? > $ equery belongs /usr/bin/qdbus > * Searching for /usr/bin/qdbus ... > dev-qt/qtdbus-4.8.5 (/usr/bin/qdbus) > It's being launched because you have a KDE app somewhere in your startup > scripts (or possibly kdeinit4 itself) > How do you start X? A display manager or using startx? > What are the contents of the relevant files? startx. My .xinitrc contains solely "exec startxfce4". > -- > Alan McKinnon > [email protected] -- Alan Mackenzie (Nuremberg, Germany).
