Hi, there are no third party plasmoids on my system, really only stuff from the official repository. Recompilation with debug symbols is much time consuming, but it will be an option to follow next week or so. You mentioned the third party thing. I noticed a wired thing on my two row task bar in the panel before plasma crashed. My English is not so good that I can describe this perfectly. Maybe this little graphics is a good way to tell you. On one desktop the task bar shows this. 1st row |firefox| 2nd row |firefox| Then I switched to another desktop and then back again. The taskbar shows this now. 1st row | ||firefox| 2nd row |firefox| On the first position of the the first row there appears an empty field. A few seconds later plasma crashes. It is strange. Thanks for your time! Bye, Lars Bram Schoenmakers wrote:

2009/10/6 Lars Tennstedt <oss@larstennstedt.de>:

Hi Lars,

...

Hello,

Plasma crashes several times a day on my Arch Linux installation (32 bit) with a segmentation fault and recovers immediately. The problem has been occured since the release of version 4.3.0. I did not remember such a problem using version 4.2.x. My system is up-to-date, installed software is taken only from the official repositories core, extra and community, the desktop effects are enabled and the graphics card driver is the nvidia closed source one. There is no bug report about this on bugs.archlinux.org. Does anybody have similar problems?

Bye, Lars Tennstedt

It's hard to say what could cause this. Do you have any (3rd-party?) plasmoids installed? Maybe it is caused by a misbehaving C++ Plasmoid, so try to remove them one after another and see if the crashes disappear. Obtaining a backtrace is also handy in order to locate where the problem is. But that requires you to rebuild the kdelibs and kdebase packages, which may be time consuming. Or, you could try if you see the same problem with kdemod, they offer debug packages straight from the repository.

For the record, I have no problems with Plasma on two very different machines (32bit and 64bit), both running KDEmod.

Kind regards,

Yesterday I deleted my .kde4 folder and Plasma has not crashed since then. If the problem appears again, I will rebuild kdebase with debug symbols. But it seems that my config files combined with the update from 4.2.4 to 4.3.0 caused the crashes. Bye Lars Bram Schoenmakers wrote:

2009/10/6 Lars Tennstedt <oss@larstennstedt.de>:

Hi Lars,

...

On one desktop the task bar shows this.

1st row |firefox| 2nd row |firefox|

Then I switched to another desktop and then back again. The taskbar shows this now.

1st row | ||firefox| 2nd row |firefox|

On the first position of the the first row there appears an empty field. A few seconds later plasma crashes.

I'd suggest to report this bug at http://bugs.kde.org . Please double check if it hasn't been reported before. I did a quick lookup over there but couldn't find something which looks like your problem. But, keep in mind that a crash report is useless without a backtrace, so I'd recommend to rebuild your packages with debug symbols if you do so.

Kind regards,

As for myself, I was using KDEmod before and now I'm just not in the mood to change from KDEmod to arch KDE. I don't know if there will be any issues and I wouldnt like then to happen now, as we're in the middle of the semester and I have a lot of importante stuff to do. That's my reason =P -- Guilherme M. Nogueira "Any sufficiently advanced technology is indistinguishable from magic." - Arthur C. Clarke

Hi, I deleted .kde4 in my home directory and the problem seems to be gone. I guess I will delete it again when KDE 4.4.0 will come out. Bye, Lars Nicolas Bigaouette wrote:

2009/10/6 Guilherme M. Nogueira <guilherme@nirev.org>

...

As for myself, I was using KDEmod before and now I'm just not in the mood to change from KDEmod to arch KDE. I don't know if there will be any issues and I wouldnt like then to happen now, as we're in the middle of the semester and I have a lot of importante stuff to do.

That's my reason =P

-- Guilherme M. Nogueira "Any sufficiently advanced technology is indistinguishable from magic." - Arthur C. Clarke

When plasma crashed on me (latest kde, intel drivers, kwin effects on, kms on), it is almost all the time because either:1) I don't have room left on drive hosting /home/me. It always need me some time to realize this since the error and consequence (crash) does not report the cause... 2) A badly written plasmoid

It's always a pain to be answered this, but you could try moving your ~/.kde4 and start with a new one. Or if you don't want, create a new user and login with it. If it works in the new user/config, then its the your configuration that is the problem, else its the system.