Version: (using Devel) Installed from: Compiled sources Compiz Fusion works fine on my laptop with kde 4.2.95-1 when started with FusionIcon, but I cannot configure the control center setting of: Personal -> Default Applications -> Window Manager -> Use a different window manager: Compiz custom (create wrapper script..... or Compiz The error message says the window manager failed to start reverting to kwin... Now compiz runs just fine on kde 4.3 (4.2.95-1) when started with FusionIcon, so it isn't a hardware/xorg issue. What needs to be fixed so that the Default Application can be set to compiz? Unless the default application can be set to compiz on kde start, the pager application (among others) is broken until plasma desktop crashes and restarts, then pager works, but won't unless compiz is the default WM) Further, there seems to be some regression between kde 4.2.91 and 4.2.95 concerning konqueror and the use of this bug page (https://bugs.kde.org/wizard.cgi). None of the drop-down menus like the KDE Version and Distribution Method can be opened when compiz is running unless you put the cursor over the drop-down, scroll the items with the mouse-wheel and then click with button-1. I don't recall this happening with 4.2.91. Let me know if I can provide any additional information. Thanks.
Which application crashed? Compiz? Thanks
I don't exactly know which app crashed. I think it is more of a case of compiz never getting started. (although compiz maybe crashing when the start attempt occurs) The situation is this: When you attempt to set the default WM with: Personal -> Default Applications -> Window Manager -> Use a different window manager -> compiz it looks like kde control center attempts to launch compiz at the moment the selection is made from the dropdown that allows you to choose "Compiz" or "Compiz custom (create wrapper script....." as soon as you make the selection, something crashes and generates the error dialog that says something to the effect of ".. window manager failed to start reverting to kwin... So I don't exactly know what is crashing, but something certainly is and this crash prevents you from ever being able to select Compiz as the default WM. Like I said above, I using compiz right now without any problems. I just start it with FusionIcon and it works fine. Of course when kde4 restores the previous session, compiz is started, but kpager is broken until plasma-desktop is restarted. Setting compiz as the default WM will evidently fix this, but this bug prevents being able to test it. Let me know if you need more info. Thanks!
That error message is from Compiz not being able to start compositing properly(or having another kind of error) and therefore it reverts to the default window manager on KDE: "KWin".
If I try changing the window manager to compiz (0.7.8) I get a crash message with this backtrace: Application: KDE Window Decorator (kde4-window-decorator), signal: Segmentation fault [KCrash Handler] #5 0x00007fdc02eaa8de in KDecorationUnstable::compositingActive (this=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.3.0/kwin/lib/kdecoration.cpp:398 #6 0x00007fdbedab95c8 in Oxygen::OxygenClient::updateWindowShape (this=0x7fd610) at /usr/src/debug/kdebase-workspace-4.3.0/kwin/clients/oxygen/oxygenclient.cpp:474 #7 0x00007fdc02eaf5df in KCommonDecoration::eventFilter (this=0x7fd610, o=0x80f040, e=0x7fff5d010c90) at /usr/src/debug/kdebase-workspace-4.3.0/kwin/lib/kcommondecoration.cpp:860 #8 0x00007fdc03677a87 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<value optimized out>, receiver=0x80f040, event=0x7fff5d010c90) at kernel/qcoreapplication.cpp:726 #9 0x00007fdc044ce2dc in QApplicationPrivate::notify_helper (this=0x65c240, receiver=0x80f040, e=0x7fff5d010c90) at kernel/qapplication.cpp:4052 #10 0x00007fdc044d55de in QApplication::notify (this=0x65c180, receiver=0x80f040, e=0x7fff5d010c90) at kernel/qapplication.cpp:4021 #11 0x00007fdc01def5d6 in KApplication::notify (this=0x65c180, receiver=0x80f040, event=0x7fff5d010c90) at /usr/src/debug/kdelibs-4.3.0/kdeui/kernel/kapplication.cpp:302 #12 0x00007fdc0367876c in QCoreApplication::notifyInternal (this=0x65c180, receiver=0x80f040, event=0x7fff5d010c90) at kernel/qcoreapplication.cpp:610 #13 0x00007fdc0451babb in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:213 #14 QWidgetPrivate::sendPendingMoveAndResizeEvents (event=<value optimized out>, receiver=<value optimized out>) at kernel/qwidget.cpp:6646 #15 0x00007fdc04521ce3 in QWidgetPrivate::show_helper (this=0x80ea18) at kernel/qwidget.cpp:6697 #16 0x00007fdc04522f1a in QWidget::setVisible (this=0x80f040, visible=<value optimized out>) at kernel/qwidget.cpp:6975 #17 0x00007fdc04522176 in show (this=<value optimized out>) at ../../src/gui/kernel/qwidget.h:473 #18 QWidgetPrivate::showChildren (this=<value optimized out>) at kernel/qwidget.cpp:7063 #19 0x00007fdc04521cff in QWidgetPrivate::show_helper (this=0x815c30) at kernel/qwidget.cpp:6703 #20 0x00007fdc04522f1a in QWidget::setVisible (this=0x80e9f0, visible=<value optimized out>) at kernel/qwidget.cpp:6975 #21 0x000000000041670f in show (this=<value optimized out>) at /usr/include/QtGui/qwidget.h:473 #22 KWD::Window::resizeDecoration (this=<value optimized out>) at window.cpp:1273 #23 0x000000000041c4d0 in KWD::Window::Window (this=0x80e9f0, parentId=<value optimized out>, clientId=<value optimized out>, frame=<value optimized out>, type=<value optimized out>, x=0, y=0, w=1, h=1) at window.cpp:158 #24 0x0000000000413f12 in KWD::Decorator::enableDecorations (this=0x65c180, timestamp=<value optimized out>, damageEvent=<value optimized out>) at decorator.cpp:240 #25 0x000000000040c7da in main (argc=<value optimized out>, argv=<value optimized out>) at main.cpp:177 With "Compiz custom ..." I get only the box which tells me that the window manager could not be started and is reverted to "KWin" Shall I try it with 0.8.2, too?
@Johannes Obermayr: the application which is crashing is not supported in this bugtracker. Please read http://wiki.compiz-fusion.org/HowtoSubmitBugReports and report the bug to its maintainers. Thanks @David: any news about this ? still happening on a current version? Thanks
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Not sure how this is relevant to the Default Applications KCM. Can you clarify?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!