Created attachment 331259 [details] first backtrace Description of problem: Running the kde 4.2 packages currently in updates-testing, I've had a couple random plasma crashes; in neither case was I immediately interacting with plasma, and I was doing different things each time. The first time I had been copying some data off DVD using dolphin, so I was making occasional use of plasma (file copy status and recently plugged devices). I think I had just closed a dolphin window when plasma nuked. The second time, I was just browsing in firefox when plasma went *boom*. This was before picking up the latest -testing kdesettings packages; not sure if they'll have any effect. Version-Release number of selected component (if applicable): kdebase-workspace-4.2.0-4.fc10.2.x86_64 How reproducible: randomly happens so far Additional info: backtraces attached http://www.smolts.org/client/show/pub_57e5f384-77af-4d40-bbad-f7b92131c12c glibc-2.9-3.{i686,x86_64} kernel-2.6.27.12-170.2.5.fc10.x86_64
Created attachment 331260 [details] second backtrace
I recently migrated my installation to some different hardware, and experienced this crash again: - only video card and one hard drive common with the previous system--old was C2D on Intel 945GM, this is Phenom II on nv 590 SLI. Smolt's not talking to me right now so haven't updated profile yet. - this time I didn't even have evil nvidia module loaded - had picked up the updated set of packages (including kdebase-workspace-4.2.0-8.fc10.x86_64). With packages now pushed to updates and presumably ready for primetime, should I take this to mean low probability of Fedora specificity, and push this report to kde bz?
Created attachment 332177 [details] backtrace from crash on new system
Thank you for the bug report. This issue needs to be addressed by the upstream developers. Please submit a report at http://bugs.kde.org. You are requested to add the bugzilla link here for tracking purposes. Please make sure the bug isn't already in the upstream bug tracker before filing it.
Pushed report upstream: https://bugs.kde.org/show_bug.cgi?id=187368
Thanks for reporting this upstream, we'll continue tracking this upstream.