Bug 321931 - Close it (crash) automatically after save file or after other actions
Summary: Close it (crash) automatically after save file or after other actions
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kate
Classification: Applications
Component: application (other bugs)
Version First Reported In: 3.10.4
Platform: Ubuntu Linux
: NOR critical
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-04 04:19 UTC by Diego Zea
Modified: 2013-07-09 15:50 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Diego Zea 2013-07-04 04:19:15 UTC 
At some moment, the program automatically close it. Happens when I push save. Happens in other situations too. This is what I see on console when crash (Ubuntu 13.04):

The program 'kate' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 4428 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.)
kate(4568)/konsole Konsole::SessionManager::~SessionManager: Konsole SessionManager destroyed with sessions still alive 


Reproducible: Always

Steps to Reproduce:
Trying to save a file
Actual Results:  
The program 'kate' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 4428 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.)
kate(4568)/konsole Konsole::SessionManager::~SessionManager: Konsole SessionManager destroyed with sessions still alive