On Friday 22 July 2011 18:41:26 Sebastian Beßler wrote: > Am 22.07.2011 16:57, schrieb Alan McKinnon: > > It may look like KDE is the likely culprit based on just the > > information you provide, but I would be more inclined to look at > > browser plugins first, concentrating on those with both Firefox and > > Chromium versions from the same developer team. > > I have zero browser plugins installed. So that is not the culprit. And > why should plugins lock up X when used under KDE but not under XFCE?
Maybe because you did not enable compositing in xfce4, but use it with kde4? > The problem that X freezes with KDE4 is more likely with webbrowsers but > happend when using other programms too. But because of the fact that one > or more browsers are nearly always running it is hard to find a freeze > without a browser running. > > > There could be a cornercase bug in KDE that only shows up on your > > specific combination, or maybe there is some edge KDE app you use that > > disagrees with violently with FF. Or maybe it's the video driver that > > doesn't actually do what it tells KDE it can do (remember the > > painfully slow nVidia drivers with early KDE4?) > > I use the opensource drivers for ati-cards. So t is unlikely to be > driver related. Well, have a look at http://www.mail-archive.com/ubuntu- b...@lists.ubuntu.com/msg1483058.html for an example how the open source atidrivers can hang X with firefox. Note that compositing was enabled here (compiz). And here's another one: https://bugzilla.redhat.com/show_bug.cgi?id=436632 > I use no edge KDE apps only amarok, yakuake, kate, konsole, dolphin, > ktorrent from time to time. All of them but dolphin is still in use > under xfce4 so I think I can rule them out too. > > I know it could still be a truckload of other things, but as a fan of > Ockham's razor I still say that KDE4 is broken. kde4 works for me, firefox works for me. I use closed source nvidia drivers. So Ockham's razor tells us, the ati-drivers are broken. Now more seriously: try attaching gdb to the hanging process and get a backtrace. You are affected by some bug in some OSS. If you want to be helpful, provide the necessary info. Even if you don't understand the backtrace, others do. > Greetings > Sebastian Beßler Regards, Michael
