Version: (using KDE 4.3.1) OS: Linux Installed from: Debian testing/unstable Packages I'm reporting this because it persisted through a reboot (and so might be serious). Opened dolphin, created new folder, entered folder, created new text file. Opened text file with kate. Entered this: position 692,0 and pressed enter, and kde crashed. Thereafter, I had a solid bug that persisted through a reboot. I purged kate and installed kwrite- same bug. On a whim I tried entering this into krunner, and discovered that just entering strings like the following into krunner (without even pressing enter) would crash kde: 692 61912 6a9a2 6 [backspace] 9 [backspace] 2 Some freak corruption maybe, but a reboot didn't fix it. I don't know what did. It is gone now.
A pure guess: the spell check and/or auto completion in kate choked on "position 692,0" because there was no space after the comma. Then a process with a history, like auto complete, etc, that reads the krunner command line while it is being entered continued choking on it. I would normally turn off spell check and especially word completion, but I had just installed kate some hours before, and had not bothered to turn it off. I have now reinstalled kate and left those options on. I'll let you know if this bug comes back. One last thing: That string (692,0) first arose because I had just entered it into the alt+f3...advanced...special window settings... "Position" setting for one of my programs. The honoring of these preferences had been rock solid... but for some reason this window "forgot" the settings (a first symptom?). I went back in to reset them. I then immediately took the steps I described above, because I was recording these numbers in case they were forgotten again.
This bug is back, and also it just happened in *this* comment box. Woke up, booted, opened iceweasel to weather page, entered my zip code... crash. Now entry of the numeral two into *this* box or krunner will cause a crash. I intend to delete the word-completion history if I can find it. I might save it for you.
If you can reproduce the bug you should install debug enabled packages and paste a complete backtrace. Please read this page for more information about generating an useful backtrace: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports Many thanks
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!