Session D-Bus not accessible?!?!

[poobaire]

I'm putting this here because I have no idea where else to put it, and I AM a noob.

My system had been running very slowly. I have a lot of programs VMWare, Crossover, and so on and so forth. One day, however (while not having used anything other than firefox, vlc, songbird, and smplayer, my computer froze. The screen showed a mirror image from top to bottom (not flipped 180 degrees, but mirrored) and I did a hard reboot on my Dell Inspiron e1705. When I tried to start back up it gives the KDE wallet manager without the border, only the interior of the box and doesnt allow me to do anything (this is again mirrored top-to-bottom) the mouse however is the right way up, and it is responsive to movement, only.

Here is where it gets tricky, I have gone into the recovery mode in the GRUB and it allows me to log in as root with network capabilities. I do this, then "startx", and I get the default startup screen then it opens KDE and gives a dialog saying as the title:

Session D-Bus not accessible
Cannot run with paramater '--icon'
when session D-Bus is not accessible.

I cannot click on anything. The mouse works, but only for movement. All else is unresponsive.

I have no idea what happened, it could have something to do with my trying to determine the proper video driver in mplayer, or whatever else. I did not, however add repositories that are incompatible.

Any help would be grand!!!

James

[dibl]

Re: Session D-Bus not accessible?!?!

The display issues that you describe do not correspond with any software or driver issues that I can think of -- they sound more like a graphics card or monitor failure of some sort.

If it is a hardware issue, there's nothing that you can do with the OS or software to fix it. Can you change from graphics mode to character mode via Ctrl-Alt-F1? Does the display return to normal in that mode? Your display (CRT or LCD) might have a problem with graphics mode -- something might have broken.

I'd guess the D-bus session messages might not be related to the goofy display issues. The root user should not/cannot run the X server -- it looks like you tried it -- that might cause the D-bus error. Try booting Recovery Mode again, and this time try (at the root # prompt)

/etc/init.d/kdm start

and see if it puts up the broken graphics display after you log in.