:45, schrieb Alberto Villa:
On Wednesday 30 March 2011 21:01:50 Ralf Folkerts wrote:
I did test-run Gnome again (by activating "gnome-session" and
commenting-out the startkde in my .xinitrc). And - got the same
effect I
get with KDE. It does run a while longer than KDE until it bombs ou
Hi,
the other day I updated my System which incl. the Update to KDE 4.6.1. I
did follow the Instructions in UPDATING. When I ran "startx" after the
Update I did get the KDE Destop, but then it froze (i.e. it didn't react
to any Key pressed, the mouse didn't work; ctrl-alt-f1 didn't take me to
Ralf Folkerts wrote:
[...]
> As I didn't find a/the reason for this I disabled the KDE 4 Screensaver
> and instead installed an Autostart-Entry for the XScreensaver (which
> runs 1a). I'm running on amd64 and tried both with kdm and (my "normal"
> way) to use
David Johnson wrote:
> It took me a while to notice, but I've discovered that the KDE screensaver
> isn't starting. I poked around a bit, and it will start using dbus, but
> krunner (which is in charge) never starts the saver.
>
> Anyone else see this? Any workarounds?
>
> Thanks,
>
> David
Hi D
Michael Nottebrock wrote:
Hi Michael,
On Saturday, 20. January 2007 15:27, Frerich Raabe wrote:
I have no Idea what might have caused the Problem; on my
Desktop-machine, where I upgraded from Ports, everything works nice.
Would be great if you let me (on the ML) know, if you find a soluti
Frerich Raabe wrote:
Hi Frerich,
well, I ran into the same Problem a while ago (posted here in December).
In my case I think the reason was that I stupidly upgraded KDE while I
was using it. Also tried to remove ~/.kde etc, which didn't help.
I have no Idea what might have caused the Problem;
