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: Confirmed => 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/1390068

Title:
  Gedit crashes when editing a file

Status in gedit package in Ubuntu:
  Invalid

Bug description:
  I am using Linux Mint (I don't know if I should report bugs here or somewhere 
else).
  After upgrading to Qiana, gedit has become very slow, in particular after 
long sessions of editing Prolog files,
  and seems to be very slow in finding matching brackets.
  I don't know if this can help, but I noticed that the bracket matching tries 
to match the symbols "less than" < and "greater than" >
  as if I was editing an html file; maybe it gets confused and finds too many 
unmatched '<' symbols?

  Occasionally, it crashes. This happens rather often, but non-
  deterministically.

  This is the message I got:

  (gedit:6314): 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 3222167 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 (core dumped)

  Thank you!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gedit 3.10.4-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Nov  6 13:34:59 2014
  InstallationDate: Installed on 2013-02-27 (617 days ago)
  InstallationMedia: Linux Mint 14 "Nadia" - Release amd64 (20121120)
  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/1390068/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to