GTK apps in KDE 4.2.3 lock the system...

[Izobalax]

This sounds like a memory problem to me. Both firefox and gimp thrash the RAM, and so the problem might not show up with other apps.

Try this: during boot, on the grub menu there is an item "memtest" or similar. Select that and let it run for 6 tests. If any errors show up, it means that you have a faulty memory chip and need to replace the bad unit.

I shall try it. Thanks.

/izo\

[montesss]

Izobalax you're not crazy and it's not your memory, so you can just forget about testing it.
I got the same issue and I can reproduce it with acute success
I am using GIMP intensively and did used it today too before I upgraded to KDE 4.2.3. After I upgraded it crashes beautifully, my screen goes blank, I get no errors in no logs. So tried to run it from console too... but screen goes blank.. can't see anything...

I have an ATI card and I use the normal drivers cause I can't use the proprietary ones (because... Jaunty... Xorg 1.6 )

[Izobalax]

Izobalax you're not crazy and it's not your memory, so you can just forget about testing it.
I got the same issue and I can reproduce it with acute success
I am using GIMP intensively and did used it today too before I upgraded to KDE 4.2.3. After I upgraded it crashes beautifully, my screen goes blank, I get no errors in no logs. So tried to run it from console too... but screen goes blank.. can't see anything...

I have an ATI card and I use the normal drivers cause I can't use the proprietary ones (because... Jaunty... Xorg 1.6 )

So I'm not going crazy.

/izo\

This sounds like a memory problem to me. Both firefox and gimp thrash the RAM, and so the problem might not show up with other apps.

Try this: during boot, on the grub menu there is an item "memtest" or similar. Select that and let it run for 6 tests. If any errors show up, it means that you have a faulty memory chip and need to replace the bad unit.

After the memtest, there is ONE bad memory address.

/izo\

[krazyd]

After the memtest, there is ONE bad memory address.

/izo\

One bad address is one too many. This is certainly the cause of your lockups, and it will continue to be a problem until you remove the bad memory module from your system!!

@montesss: this could be a completely different issue.