abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: ksplashx Laughlin --pid component: kdebase-workspace crash_function: updateSplashImage executable: /usr/bin/ksplashx kernel: 2.6.35.2-9.fc14.x86_64 package: kdebase-workspace-4.5.0-2.fc14 rating: 4 reason: Process /usr/bin/ksplashx was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) How to reproduce: I've installed F-14 alpha, installed KDE, updated system, reboot and got this abrt report time: 1282826815 uid: 500
Created an attachment (id=441219) File: backtrace
I can reproduce by system settings-> workspace appearance -> splash screen ->test "Default" works Laughlin crashes I've installed F-14 with Gnome and later installed kdm kdebase kdebase-workspace kdelibs and their dependencies, so maybe there is some package missing, but it should not crash imho
# rpm -qa | grep laughlin gives me: laughlin-backgrounds-kde, laughlin-backgrounds-single, laughlin-backgrounds-gnome, laughlin-kde-theme
Most likely it's a bug in the Laughlin KSplash theme. KSplashX just segfaults if anything is wrong in the theme, there's little to no error checking.
Agreed, let's triage this there for now, and test what went wrong.
Well, but wouldn't laughlin-kde-theme be better? That's what contains the KSplash theme, AFAIK.
Doh, of course. sorry.
Do you use KVM? Laughlin KDE theme is just a Goddard port to use new wallpaper. Does Goddard works for you?
> KVM? yes >Goddart I don't have it installed
Ok, thanks. It's the Qt/XOrg/KVM/Cirrus bug - related to wrong background colours etc. - improper 24 bit depth handling. For me it isn't kde-45 or qt47 blocker - and it's related only to KVM with Cirrus graphics. Reassigning to Qt.
Why not assigned to -cirrus ?
*** This bug has been marked as a duplicate of bug 632814 ***
fyi, the 'orange' thing is hopefully fixed in qt-4.7.0-6 %changelog * Fri Oct 15 2010 Than Ngo <than> - 4.7.0-6 - apply patch to fix the color issue in 24bit mode (cirrus driver)
(In reply to comment #13) > fyi, the 'orange' thing is hopefully fixed in qt-4.7.0-6 > yes, it's fixed in qt-4.7.0-6