Comment 2 for bug 1195007

Revision history for this message
Alet Roux (alet-roux) wrote : Re: kile crashes when click on "file new + save"

I have the same problem. While trying to solve the problem, I deleted kile's config files, and now when I run kile, it opens up, I get a dialog saying "The standard tool list need to be reloaded because of the switch from KDE3 to KDE4. This will overwrite any changes in the tools you have made. Do you want to reload the list now (recommended)?", and, independent of whether I click "Yes" or "No", kile then crashes and leaves the following error message on the console:

kile(9877)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix: "libkonsolepart.so"
kile(9877)/konsole Konsole::Session::run: Attempted to re-run an already running session.
kile(9877)/kdeui (KNotification) KNotification::slotReceivedIdError: Error while contacting notify daemon "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
The program 'kile' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 2084 error_code 3 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
kile(9877)/konsole Konsole::SessionManager::~SessionManager: Konsole SessionManager destroyed with sessions still alive

I discovered this problem for the first time today, and suspect it started just after a massive update of kde related packages. I wouldn't know where to start debugging this, but would be happy to provide further info - just ask.