gedit crashed with SIGSEGV in magazine_chain_pop_head()

Bug #1196523 reported by Mitsuya Shibata
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gedit
Fix Released
Unknown
gedit (Fedora)
Won't Fix
Undecided
gedit (Ubuntu)
Invalid
High
Unassigned
Saucy
Invalid
High
Unassigned
gtk+3.0 (Ubuntu)
Fix Released
High
Unassigned
Saucy
Fix Released
High
Unassigned

Bug Description

* Impact: the text editor segfaults when using some input methods

* Test Case:

Enable japanese input methods and
input characters between "" on this document

-------------------------------------------------------
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2012-10-31T14:54:16\n"
"PO-Revision-Date: 2012-10-31T14:54:16\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

-------------------------------------------------------

* Regression potential: check that there is no stability issues in gedit

Revision history for this message
In , Cheng-Chia (cheng-chia-redhat-bugs) wrote :

Description of problem:
1. I use gedit to edit a existing file ( I am upload it later)
2. I selected one of Chinese characters
3. I pressed Super + Space to switch to ibus-chewing input engine which I set with GNOME Settings.
4. I pressed "j" key with ibus-chewing
5. gedit crashed

Version-Release number of selected component:
gedit-3.8.1-1.fc19

Additional info:
backtrace_rating: 4
cmdline: gedit /home/zerng07/Translations/anjuta.gnome-3-8.zh_TW.po
crash_function: magazine_chain_pop_head
executable: /usr/bin/gedit
kernel: 3.9.0-0.rc8.git0.2.fc19.x86_64
runlevel: N 5
uid: 1000
ureports_counter: 1
xsession_errors:

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 magazine_chain_pop_head at gslice.c:532
 #1 thread_memory_magazine1_alloc at gslice.c:835
 #2 g_slice_alloc at gslice.c:994
 #3 pango_attr_list_new at pango-attributes.c:1113
 #4 pango_attr_list_filter at pango-attributes.c:1992
 #5 filter_no_shape_attributes at pango-layout.c:3812
 #6 pango_layout_check_lines at pango-layout.c:3872
 #7 pango_layout_get_extents_internal at pango-layout.c:2534
 #8 pango_layout_get_extents at pango-layout.c:2729
 #9 gtk_text_layout_get_line_display at gtktextlayout.c:2438

Potential duplicate: bug 750087

Revision history for this message
In , Cheng-Chia (cheng-chia-redhat-bugs) wrote :

Created attachment 741062
File: backtrace

Revision history for this message
In , Cheng-Chia (cheng-chia-redhat-bugs) wrote :

Created attachment 741063
File: cgroup

Revision history for this message
In , Cheng-Chia (cheng-chia-redhat-bugs) wrote :

Created attachment 741064
File: core_backtrace

Revision history for this message
In , Cheng-Chia (cheng-chia-redhat-bugs) wrote :

Created attachment 741065
File: dso_list

Revision history for this message
In , Cheng-Chia (cheng-chia-redhat-bugs) wrote :

Created attachment 741066
File: environ

Revision history for this message
In , Cheng-Chia (cheng-chia-redhat-bugs) wrote :

Created attachment 741068
File: limits

Revision history for this message
In , Cheng-Chia (cheng-chia-redhat-bugs) wrote :

Created attachment 741069
File: maps

Revision history for this message
In , Cheng-Chia (cheng-chia-redhat-bugs) wrote :

Created attachment 741070
File: open_fds

Revision history for this message
In , Cheng-Chia (cheng-chia-redhat-bugs) wrote :

Created attachment 741071
File: proc_pid_status

Revision history for this message
In , Cheng-Chia (cheng-chia-redhat-bugs) wrote :

Created attachment 741072
File: var_log_messages

Revision history for this message
In , Cheng-Chia (cheng-chia-redhat-bugs) wrote :

Created attachment 741083
The file which I edited from.

Revision history for this message
Mitsuya Shibata (cosmos-door) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=0x2454670) at /build/buildd/glib2.0-2.37.3/./glib/gslice.c:545
 thread_memory_magazine1_alloc (tmem=<optimized out>, ix=1) at /build/buildd/glib2.0-2.37.3/./glib/gslice.c:848
 g_slice_alloc (mem_size=mem_size@entry=24) at /build/buildd/glib2.0-2.37.3/./glib/gslice.c:1007
 pango_attr_font_desc_new (desc=0x2e1cc60) at /build/buildd/pango1.0-1.32.5/./pango/pango-attributes.c:712
 pango_attribute_copy (attr=0x25ff8e0) at /build/buildd/pango1.0-1.32.5/./pango/pango-attributes.c:163

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gedit (Ubuntu):
importance: Undecided → Medium
summary: - gedit crashed with SIGSEGV in g_slice_alloc()
+ gedit crashed with SIGSEGV in magazine_chain_pop_head()
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
In , Jiro (jiro-redhat-bugs) wrote :

Steps to reproduce
==================
1. Launch gedit
2. Open a file in any format whose syntax gedit can recognize to highlight the text
3. Move the cursor to any position where strings highlighted
4. Input Japanese characters through ibus and try to convert them with the space key there, and gedit cranshes

reporter: libreport-2.1.5
backtrace_rating: 4
cmdline: gedit
crash_function: magazine_chain_pop_head
executable: /usr/bin/gedit
kernel: 3.9.8-300.fc19.x86_64
package: gedit-3.8.3-1.fc19
reason: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV)
runlevel: N 5
uid: 1000

Changed in gedit:
status: Unknown → New
Changed in gedit:
status: New → Confirmed
Revision history for this message
In , Mamoru (mamoru-redhat-bugs) wrote :

100% reproducible, with the following

* Install some tex related packages, ibus, ibus-kkc
* $ gedit tmp.txt
* On the window
  - type $$
  - go to head
  - type ctrl-space, entering ibus-kkc mode
  - type "ima"
  - enter space to convert "Ima" to kanji
  - then crash

reporter: libreport-2.1.5
backtrace_rating: 4
cmdline: gedit
crash_function: magazine_chain_pop_head
executable: /usr/bin/gedit
kernel: 3.10.3-300.fc19.i686
package: gedit-3.8.3-1.fc19
reason: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV)
runlevel: 3 5
uid: 500

Revision history for this message
In , Mamoru (mamoru-redhat-bugs) wrote :

CC-ing to i18n, because it seems this issue is affecting several people using ibus on CJK locale.

Revision history for this message
In , Mamoru (mamoru-redhat-bugs) wrote :

Created attachment 781795
screenshot just before gedit crashes

(In reply to Jiro Matsuzawa from comment #12)
> Steps to reproduce
> ==================
> 2. Open a file in any format whose syntax gedit can recognize to highlight
> the text

With my steps, when typing "ima" before $$, "ima" is highlightened (see screenshot)

Revision history for this message
In , Mamoru (mamoru-redhat-bugs) wrote :

Created attachment 781796
correct screenshot

The above screenshot was wrong, sorry

Revision history for this message
In , Jiro (jiro-redhat-bugs) wrote :
Revision history for this message
In , Mamoru (mamoru-redhat-bugs) wrote :

(In reply to Jiro Matsuzawa from comment #17)
> This issue has been fixed on the upstream. [1][2]
>
> [1] https://bugzilla.gnome.org/show_bug.cgi?id=703533
> [2]
> https://git.gnome.org/browse/gtk+/commit/
> ?id=837a0d3e4002e640be2aea2a67802c474997e354

Confirmed that applying this patch to gtk3-3.8.2-2.fc19.src resolves this issue.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gedit (Ubuntu):
status: New → Confirmed
Revision history for this message
Ikuya Awashiro (ikuya-fruitsbasket) wrote :

It is not a gedit issue but gtk+3 issue.

Revision history for this message
Ikuya Awashiro (ikuya-fruitsbasket) wrote :
Revision history for this message
Ikuya Awashiro (ikuya-fruitsbasket) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

@Ikuya: thanks for adding debdiffs for this issue!

 when you do that you should also subscribe "ubuntu-sponsors" to the bug to make sure the changes are going to be reviewed

GTK 3.10.6 is going to be uploaded to trusty this week so I'm discarding your debdiff for that serie, I'm going to sponsor the saucy fix as a SRU though

Changed in gtk+3.0 (Ubuntu):
status: New → Fix Committed
importance: Undecided → High
Changed in gtk+3.0 (Ubuntu Saucy):
importance: Undecided → High
status: New → Triaged
description: updated
Changed in gedit (Ubuntu Saucy):
status: New → Invalid
importance: Undecided → High
Changed in gedit (Ubuntu):
importance: Medium → High
status: Confirmed → Invalid
Revision history for this message
Stéphane Graber (stgraber) wrote : Please test proposed package

Hello Mitsuya, or anyone else affected,

Accepted gtk+3.0 into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gtk+3.0/3.8.6-0ubuntu3.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in gtk+3.0 (Ubuntu Saucy):
status: Triaged → Fix Committed
tags: added: verification-needed
Revision history for this message
Mitsuya Shibata (cosmos-door) wrote :

Thank you for upload. I tested, everything is ok.

Test steps is following:
$ echo "deb http://archive.ubuntu.com/ubuntu/ saucy-proposed main restricted" | sudo tee /etc/apt/sources.list.d/proposed.list
$ sudo vi /etc/apt/preferences.d/proposed
Package: *
Pin: release a=saucy-proposed
Pin-Priority: 400
$ sudo apt-get update
$ sudo apt-get install -t saucy-proposed gir1.2-gtk-3.0 libgail-3-0 libgtk-3-0 libgtk-3-bin libgtk-3-common
$ gedit test.po
and can input japanese text.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Mitsuya Shibata (cosmos-door) wrote :

Tested package version:
$ LANG=C dpkg -l gir1.2-gtk-3.0 libgail-3-0 libgtk-3-0 libgtk-3-bin libgtk-3-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=============================-===================-===================-================================================================
ii gir1.2-gtk-3.0 3.8.6-0ubuntu3.1 amd64 GTK+ graphical user interface library -- gir bindings
ii libgail-3-0:amd64 3.8.6-0ubuntu3.1 amd64 GNOME Accessibility Implementation Library -- shared libraries
ii libgtk-3-0:amd64 3.8.6-0ubuntu3.1 amd64 GTK+ graphical user interface library
ii libgtk-3-bin 3.8.6-0ubuntu3.1 amd64 programs for the GTK+ graphical user interface library
ii libgtk-3-common 3.8.6-0ubuntu3.1 all common files for the GTK+ graphical user interface library

Revision history for this message
Akira Tanaka (popo1897) wrote :

Thank you for your upload. I also confirmed the bug fixed.

The test procedure is following:
1) Install saucy in Virtualbox
2) Enable 'saucy-proposed' in 'Software & Updates'
3) Do `apt-get upgrade`
4) `gedit test.tex`

Then, I confirmed gedit and Japanese input method work fine.

Tested package version:

$ dpkg -l libgtk-3-bin libgtk-3-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=======================-================-================-====================================================
ii libgtk-3-bin 3.8.6-0ubuntu3.1 amd64 programs for the GTK+ graphical user interface libra
ii libgtk-3-common 3.8.6-0ubuntu3.1 all common files for the GTK+ graphical user interface l

Revision history for this message
katsu (katsukatsu-deactivatedaccount) wrote :

installed: gir1.2-gtk-3.0/saucy-proposed libgail-3-0/saucy-proposed libgtk-3-0/saucy-proposed libgtk-3-bin/saucy-proposed libgtk-3-common/saucy-proposed

check: gedit with syntaxhighlight
japanese input char & conversion between "". --> no problem

check: gedit without syntaxhighlight
japanese input char & conversion between "". --> no problem

thank you it works.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gtk+3.0 - 3.10.6-0ubuntu2

---------------
gtk+3.0 (3.10.6-0ubuntu2) trusty; urgency=low

  * debian/tests/build: update to not use gtkstock which is deprecated,
    the warning is making the autopkgtest unhappy
 -- Sebastien Bacher <email address hidden> Wed, 11 Dec 2013 10:52:41 +0100

Changed in gtk+3.0 (Ubuntu):
status: Fix Committed → Fix Released
tags: added: verification-done-saucy
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gtk+3.0 - 3.8.6-0ubuntu3.1

---------------
gtk+3.0 (3.8.6-0ubuntu3.1) saucy; urgency=low

  * debian/patches/git_textlayout_fix.patch:
     - gedit crashed with SIGSEGV in magazine_chain_pop_head() (lp: #1196523)
 -- Ikuya Awashiro <email address hidden> Mon, 09 Dec 2013 11:54:09 +0900

Changed in gtk+3.0 (Ubuntu Saucy):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for gtk+3.0 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Changed in gedit:
status: Confirmed → Fix Released
Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Changed in gedit (Fedora):
importance: Unknown → Undecided
status: Unknown → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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