Version: Gideon 3.0a5, sources from 04.08.2003 (using KDE KDE 3.1.3) Installed from: SuSE RPMs Compiler: gcc (GCC) 3.3 20030226 (prerelease) (SuSE Linux) OS: Linux Last messages from gideon ... kdevelop (core): mimeType = text/x-chdr kdevelop (core): factory = 0x89a5b00 kdevelop (core): Encoding: , extension: 0x9fb8ee8 kdevelop (core): MainWindowShare::slotGUICreated() kdevelop (core): *** found "set_confdlg" action - unplugging kdevelop (abbrev): AbbrevPart::slotActivePartChanged() kdevelop (abbrev): AbbrevPart::slotActivePartChanged() -- OK kdevelop (history): history-length=78 qeditor: CppSupportPart::activePartChanged() kdevelop (cpp support): ProblemReporter::reparse() kdevelop (cpp support): ---> file added kdevelop (cpp support): CppCodeCompletion::slotActivePartChanged() kdevelop (cpp support): enabling code completion kdevelop (cpp support): CppCodeCompletion::slotActivePartChanged() -- end kdevelop (history): partAdded=0x93c17b0 gideon: BookmarksPart::partAdded() kdevelop (core): dcop emitting loadedFile /usr/lib/qt3/include/qvaluelist.h QObject::connect: No such signal KateDocument::fileNameChanged(const KURL&) QObject::connect: (sender name: 'Kate::Document') QObject::connect: (receiver name: 'unnamed') Alarm clock Then gideon is finished.
This seams to be a KATE thing Have you installed all KDE 3.1.3 packages?
:/ could you tell me why that seems to be a kate thing ?, beside it crashs after the file load stuff, there is no incident that this crash is in the kate part (that the connect fails is not critical at all, only noise which should be cleaned up and is cleanup up in cvs head
No, this is probably not related to kate, and is totally meaningless to keep around as a bug report. I think it has been fixed but it's impossible to verify since the report doesn't contain much to go on. Closing.
Almost all "alarm clock" problems are related to linking problems. I recommend everybody who have this problem rebuild and reinstall KDevelop: make clean && make && make install