desktop-packages team mailing list archive

[Sebastien Bacher <seb128@xxxxxxxxxx>]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will
automatically open a new bug report which can then dealt with more
efficiently. Thanks in advance for your cooperation and understanding.

** Changed in: gedit (Ubuntu)
   Importance: Undecided => Low

** Changed in: gedit (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1429248

Title:
  gedit crashes frequently - every 10min or so

Status in gedit package in Ubuntu:
  Invalid

Bug description:
  Here's the trace:

  $ gedit

  (gedit:20735): Gdk-ERROR **: The program 'gedit' received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadLength (poly request too large or internal Xlib length erro'.
    (Details: serial 23634806 error_code 16 request_code 18 (core protocol) 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 GDK_SYNCHRONIZE environment
     variable to change this behavior. You can then get a meaningful
     backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gedit 3.10.4-0ubuntu6
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar  6 13:46:09 2015
  EcryptfsInUse: Yes
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1429248/+subscriptions