KDE 4.1.3, OpenSUSE 11.0 RPMs I want to use Compiz instead Kwin, because Compiz is really faster at this moment. When I switch from Kwin to Compiz in Systemsettings/Default Applications, simple-ccs-kde got a SIGSEGV Here is a .kcrash output: Приложение: Simple CCSM (simple-ccsm-kde), сигнал SIGSEGV [?1034h[Thread debugging using libthread_db enabled] [New Thread 0xb64c6a40 (LWP 4132)] [KCrash handler] #6 0xb6b55407 in ccsFindSetting () from /usr/lib/libcompizconfig.so.0 #7 0x0805011e in Dialog::setting (this=0xbfc6daf0, plugin=0x0, name=0x805b6f4 "open_effects") at /usr/src/debug/simple-ccsm-kde-1.0/dialog.cpp:744 #8 0x0805222d in Dialog::setupAnimationCombo (this=0xbfc6daf0, option=0x805b6f4 "open_effects", label=0x80e1488, combo=0x80e04e0) at /usr/src/debug/simple-ccsm-kde-1.0/dialog.cpp:511 #9 0x080525fa in Dialog::setupAnimation (this=0xbfc6daf0) at /usr/src/debug/simple-ccsm-kde-1.0/dialog.cpp:190 #10 0x08053d32 in Dialog::loadFromProfile (this=0xbfc6daf0) at /usr/src/debug/simple-ccsm-kde-1.0/dialog.cpp:110 #11 0x08054024 in Dialog::loadCCS (this=0xbfc6daf0) at /usr/src/debug/simple-ccsm-kde-1.0/dialog.cpp:103 #12 0x080544b0 in Dialog (this=0xbfc6daf0) at /usr/src/debug/simple-ccsm-kde-1.0/dialog.cpp:63 #13 0x0804fd4c in main (argc=3, argv=0xbfc6dd44) at /usr/src/debug/simple-ccsm-kde-1.0/main.cpp:38 #0 0xffffe430 in __kernel_vsyscall () I try to run simple-ccsm-kde from Konsole - got a crash again. Konsole output simple-ccsm-kde(6717): Communication problem with "simple-ccsm-kde" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " KCrash: Application 'simple-ccsm-kde' crashing...
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.