Application that crashed: kile Version of the application: 2.0.83 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-20-generic i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: Kile freezes under two conditions while editing a file: 1. Autosave after x minutes 2. System screensaver kicks in after y minutes of inactivity, y < x In a freeze, the file becomes read-only, and cannot be edited. The cursor does not blink. The file can be saved. Opening a new file, or reloading the frozen file, leads to the same read-only mode. When Kile is closed, the crash report assistant recognizes a crash and prompts me for a report. -- Backtrace: Application: Kile (kile), signal: Segmentation fault [KCrash Handler] #6 0x030587f0 in QList (this=0xa3802d0) at ../../include/QtCore/../../src/corelib/tools/qlist.h:111 #7 QActionGroup::actions (this=0xa3802d0) at kernel/qactiongroup.cpp:252 #8 0x03fab27b in KRecentFilesAction::addUrl (this=0xa3800d8, _url=..., name=...) at ../../kdeui/actions/krecentfilesaction.cpp:137 #9 0x081cbe07 in _start () Reported using DrKonqi
This could be related to bug 208151. Does the file you are editing have non-ascii characters (or another "non-standard" encoding) ? Regards
I was editing LaTeX files during the time of the crash. AFAIK, all characters were standard. Note: I opened Kile to read about "non-standard" encoding. I closed the file I had been working on without editing it. A minute after closing Kile, I received another crash notice.
I have just opened and closed Kile without taking any actions (like closing a file or looking through the help menu). I didn't receive a notice from the KDE Crash Handler on closing Kile. But reopening Kile resulted in a crash. Therefore, this bug could be related to bug 208151, even without nonstandard characters.
Please update KDE to at least version 4.5 and Kile to 2.1 beta 5, and check if this bugs still occurs. Thanks.
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.