Triskel 5.5 crashes after login every now and then
I don't like Gnome 3 and it's fallback mode, so I started checking out all other flavors of Trisquel. After installing the Triskel packages I'm really impressed, KDE works way faster than how I remembered, especially after some finetuning. It doesn't even need a lot of RAM, 220MB after logging in is all it uses up, if stuff like Nepomuk and some other KDE software is disabled.
I do have one issue though: sometimes the desktop crashes at login and I'm back at KDM again. When logging in for the second time, everything is fine though. It doesn't even happen all the time, just now and then, so most of the time I can login without a crash.
When I look up Desktop Effects in System Settings it tells me "OpenGL compositing has crashed KWin in the past. This was most likely due to a driver bug."
I use the X4500 card from Intel, so I assume the driver isn't the problem. Where should I look for a more detailed report of the crash? Did anyone else experience something similar?
While I'm not saying it is... the drivers could be a problem. Just being free in and of itself does not mean they are less buggy. Obviously it isn't crashing because of a lack of 3d acceleration (like what might happen with nVidia/ATI graphics chipsets).
Have you tried different options like Direct rendering and vsync in the "desktop effects" section of System Settings. I had a similar problem in the past and it was solved by enabling vsync iirc.
Strange, now I tried different combinations of options and nothing helps. Now Triskel crashes every uneven login and every even login works. No matter what option is enabled under desktop effects and even if they are disabled completely.
However, when I turn the compositing on I can utilize all of the effects. When I try enabling different effects for the window-closing event KWin still crashes though, but I don't think it's abnormal, the effects must just be in a conflict with each other.
It's only the uneven logins that crash KWin, even if "Enable desktop effects at startup" is unchecked. It's strange how it is so consistant, every second time you login everything works well.
I'll look into the ubuntu forums tomorrow, maybe it's an upstream bug?
You can try the pure Triskel 5.5 with the last iso(from April 11th):
Page with other isos: http://devel.trisquel.info/makeiso/iso/old/?C=M;O=D
Works fine with Dell Inspiron, Intel Celeron 1.8Ghz, 1GB RAM.
But I prefer the simplicity of GNOME 3(with Shell), I love it. =)
This working every other time business sounds to me as if there is some logic that "since this works now, we'll enable that for the next login".
As a workaround you could perhaps write a logout script that would disable the compositing completely manually.
Besides that try reading the various logs for any additional insight.
It is a bug in Kubuntu that is marked as solved upstream by now. The current workaround is to add "TerminateServer=true" in the /etc/kde4/kdmrc in the [X-:0-Core] section.
That's how I've done it and managed to login with effects enabled three times in a row :)
Edit: got the workaround from here, Post #7. The guy suggests adding same line in [X-:*-Core] though. Not sure where the difference will be, for me adding the line inside [X-:0-Core] works.
Would you list what apart from Nepomuk you disabled to drop memory usage down to 220MB please? I'm keen to get Triskel working in netbook mode on my Acer Aspire One ZG5 AOA150.
Thanks in anticipation.
I have disabled Nepomuk and Akonadi. I'm not at home right now, will post more details soon. You have to edit certain files to prevent Akonadi being loaded at start, that's all I remember for sure.
All in all, I find KDE to be very fast on a Core2Duo e6400 with 2GB of memory and an integrated Intel card. Only thing that takes more than with other environments is logging in, but disabling the login-splash animation makes that a bit faster too.
> post more details soon. You have to edit certain files to prevent
> Akonadi being loaded at start, that's all I remember for sure.
Thanks, just knowing that meant I found this
And therefore could disable Akonadi myself.
Thanks again - Leny