Version: (using KDE 4.3.0) Installed from: SuSE RPMs Steps to reproduce: 1. Make sure to have desktop effects enabled. 2. Login from kdm by entering user/pass. 3. As soon as desktop loads, click ALT+Shift+F12. 4. Kwin dies.
can you please post a backtrace. Without the backtrace we can't see why kwin died.
How to generate backtrace in this case. It appears that just windows don't have title bar. I have to get it back by running "kwin --replace" from command line.
so the window manager is still running? You are able to switch windows?
I don't remember exactly but at least title bar was gone. I'll test again and let you know.
On bug #203794 you've wrote that it is plasma-desktop crashing, does plasma crash with kwin?
Well sometimes plasma crashes and sometimes kwin. It's tricky to reproduce as after login, in certain time pressing ALT+Shift+F12 can cause this. However it doesn't trigger drkonqui and can't get backtrace. However I can open konsole(as I've configured a shortcut "win+k") and start the process again.
if possible please try to run kwin inside gdb and try to produce a backtrace. Without the backtrace there is nothing we can do as we don't know where it crashes.
Unfortunately this is very hard to reproduce as this happens at the time of login only and that time it doesn't generate backtrace. If you can guide me how to run kwin in gdb at login, I can try and post backtrace.
I have no idea how to start kwin directly at login inside gdb. Perhaps someone else has an idea?
1. identify the kde startup script "which startkde" 2. check if you can get writing permissions on that script (i.e you must have root access, otherwise you can stop here) 3. make a backup copy of the script 4. really ;-) 5. identify the full path to kwin "which kwin" 6. write a file anywhere, anyname. e.g. kwrite ~/gdb.kwin-cmds --- snip -- file /full/path/to/kwin run bt -- end snip -- 7. edit the startkde script 8. find some "KDEWM" string 9. comment the line test -n "$KDEWM" && KDEWM="--windowmanager $KDEWM" #test -n "$KDEWM" && KDEWM="--windowmanager $KDEWM" 10. instead add KDEWM="--windowmanager gdb < $HOME/gdb.kwin-cmds > $HOME/gdb.kwin-log" 11. save, logout, login, wait for crash 12. "~/gdb.kwin-log" should contain the backtrace 13. replace the manipulated startup script with the backup you made... traps: - if your system has it's debug and run libs split in a way gdb can not automatically detect them, the backtrace might be useless (you'd have to extend the gbd command file then) - i've not actually tested this, so i do not know whether "kwrapper4 ksmserver --windowmanager" might stumble on the complex and IO redirecting WM command, so to bypass this, try KDEWM="--windowmanager 'gdb < /home/ruchir/gdb.kwin-cmds > /home/ruchir/gdb.kwin-log'" instead (i.e. replace the $HOME variable with the path to your account and notice the single quotes >>'<<)
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 set the bug status 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!