Version: (using KDE 4.2.3) OS: Linux Installed from: I Don't Know While using Mozilla Firefox a crash report came then the screen went blank
This is going to be difficult/impossible to triage without a backtrace. :( If the crash happens regularly we can try another debug methods to try to get information. Regards
(In reply to comment #1) > This is going to be difficult/impossible to triage without a backtrace. :( > If the crash happens regularly we can try another debug methods to try to get > information. > Regards It's happened to me before. But thats when I didn't know how to get here.
Just to be sure, do you had time to see what application crashed after the screen went blank ? Did you saw any other details during that time? Thanks
(In reply to comment #3) > Just to be sure, do you had time to see what application crashed after the > screen went blank ? Did you saw any other details during that time? > Thanks I saw the window come up and noticed it said KWin. I couldn't see any other details.
Ok, let's try to get a backtrace. - Start KDE normally - Go to a virtual terminal (Ctrl+alt+f1) - Log as your KDE user - Export the variable DISPLAY (type "export DISPLAY=:0" and press Return) - Type "gdb kwin" and press Return - Type "run --replace" and press Return KWin will be restarted - Now go back to the KDE session (ctrl+alt+f7) and try to reproduce the crash (or wait for it ) - Once KWin crashes and the screen goes to black; go back to the virtual terminal (Ctrl+alt+f1) - Type "set logging on" and press Return (this will force the app to log all the backtrace to the file: gdb.txt ) - Type "bt full" and press Return until the backtrace is fetched - You can close GDB/that virtual terminal session You will have now a "gdb.txt" file containing the backtrace of the KWin crash. Regards
(In reply to comment #5) > Ok, let's try to get a backtrace. > > - Start KDE normally > - Go to a virtual terminal (Ctrl+alt+f1) > - Log as your KDE user > - Export the variable DISPLAY (type "export DISPLAY=:0" and press Return) > - Type "gdb kwin" and press Return > - Type "run --replace" and press Return > KWin will be restarted > - Now go back to the KDE session (ctrl+alt+f7) and try to reproduce the crash > (or wait for it ) > - Once KWin crashes and the screen goes to black; go back to the virtual > terminal (Ctrl+alt+f1) > - Type "set logging on" and press Return (this will force the app to log all > the backtrace to the file: gdb.txt ) > - Type "bt full" and press Return until the backtrace is fetched > - You can close GDB/that virtual terminal session > > You will have now a "gdb.txt" file containing the backtrace of the KWin crash. > Regards Thanks. I'll work on it as soon as I can.
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!