gedit crashed with SIGSEGV in pango_renderer_draw_glyphs()

Bug #272966 reported by nullack
6
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gedit

Gedit crashed unexpectedly while I was trying to view a log file.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gedit
NonfreeKernelModules: nvidia
Package: gedit 2.23.93-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: gedit file:///home/User Name/log.txt
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gedit
StacktraceTop:
 ?? () from /usr/lib/libcairo.so.2
 ?? () from /usr/lib/libpangocairo-1.0.so.0
 ?? () from /usr/lib/libpangocairo-1.0.so.0
 pango_renderer_draw_glyphs ()
 pango_renderer_draw_glyph_item ()
Title: gedit crashed with SIGSEGV in pango_renderer_draw_glyphs()
Uname: Linux 2.6.27-3-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
nullack (nullack) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:save_current_point (renderer=0x17c4490)
_pango_cairo_do_glyph_string (cr=0x7fd4f09a1ba0, font=0x15cb010, glyphs=0x1c36740,
pango_renderer_draw_glyphs (renderer=0x1544930, font=0x15cb010, glyphs=0x1c36740,
pango_renderer_draw_glyph_item (renderer=0x1544930,
pango_renderer_draw_layout_line (renderer=0x1544930, line=0x1c6a280, x=2048, y=216064)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gedit:
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in gedit:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in gedit:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.