Luis Ángel Fernández Fernández writes:
> On Martes, 13 de septiembre de 2011 17:00:38 Alex Schuster escribió:
>
> > > Any idea about what's going on and how can I fix it?
> >
> > No. But I'd diff the output with the .xsession-errors you get when
> > using the failsafe session. So you can separate the critical errors
> > from harmless entries that happen every time. For example, I have no
> > idea whether those dbus messages are normal in your setup, or if they
> > are the root of the problem.
>
> Ok. It seems that those dbus messages are normal since I have them in
> both modes.
One thing less to check for.
> The differences start just after those messages. These are the
> differences:
>
> X Error of failed request: BadWindow (invalid Window parameter)
> Major opcode of failed request: 138 (NV-GLX)
> Minor opcode of failed request: 4 ()
> Resource id in failed request: 0x1e00003
> Serial number of failed request: 33
> Current serial number in output stream: 33
> kwin(15671): ""fsrestore1" - conversion of "0,0,0,0" to QRect failed"
> kwin(15671): ""fsrestore2" - conversion of "0,0,0,0" to QRect failed"
> kwin(15671): ""fsrestore3" - conversion of "0,0,0,0" to QRect failed"
> kwin(15671): Shaders are not supported
> kwin(15671): Shaders are not supported
> plasma-desktop: cannot connect to X server :0
> plasma-desktop(15679): Communication problem with "plasma-desktop" ,
> it probably crashed.
I have similar kwin messages, too. But the X stuff is weird.
A shot in the dark: Can it be that compositing / desktop effects
are making trouble, and are turned off in safe mode? You could disable
them by setting Enabled to false in .kde/share/config/kwinrc, or better
use the
kwriteconfig --file kwinrc --group Compositing --key Enabled false
command to do this.
No more ideas,
Wonko
___________________________________________________
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
