gedit assert failure: *** stack smashing detected ***: /usr/bin/gedit terminated

Bug #1386815 reported by zob
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
Expired
Undecided
Unassigned

Bug Description

Gedit from Gnome3 staging crashes when pressing CTRL+SHIFT+I on this system (whatever that is supposed to do).
It does it every time. To reproduce:
1 Open gedit
2 Press CTRL+SHIFT+I
3 Crashes immediately

Running ubuntu-gnome 14.10 fully updated, kernel 3.16.0-23-generic

Gedit is the staging version 3.14:

Installed: 3.14.0-0ubuntu1~utopic1
  Candidate: 3.14.0-0ubuntu1~utopic1
  Version table:
 *** 3.14.0-0ubuntu1~utopic1 0
        500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ utopic/main amd64 Packages
        100 /var/lib/dpkg/status
     3.12.2-0ubuntu1~trusty1 0
        500 http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/ utopic/main amd64 Packages
     3.10.4-0ubuntu6 0
        500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: gedit 3.14.0-0ubuntu1~utopic1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AssertionMessage: *** stack smashing detected ***: /usr/bin/gedit terminated
CurrentDesktop: GNOME
Date: Tue Oct 28 10:41:13 2014
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2014-10-26 (2 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: /usr/bin/gedit --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: gedit
StacktraceTop:
 __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fd1c62d74a6 "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:175
 __GI___fortify_fail (msg=<optimized out>, msg@entry=0x7fd1c62d748e "stack smashing detected") at fortify_fail.c:37
 __stack_chk_fail () at stack_chk_fail.c:28
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: gedit assert failure: *** stack smashing detected ***: /usr/bin/gedit terminated
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
zob (zob) wrote :
information type: Private → Public
Revision history for this message
Ubuntu GNOME (ug-bot) wrote :

StacktraceTop:
 __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fd1c62d74a6 "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:175
 __GI___fortify_fail (msg=<optimized out>, msg@entry=0x7fd1c62d748e "stack smashing detected") at fortify_fail.c:37
 __stack_chk_fail () at stack_chk_fail.c:28
 size_data_func (col=<optimized out>, cell=0x13ea360, model=<optimized out>, iter=<optimized out>, data=<optimized out>) at /build/buildd/gtk+3.0-3.15.0+git20141026.4d075cf2/./gtk/inspector/resource-list.c:348
 apply_cell_attributes (renderer=0x13ea360, info=0x1415400, data=0x7fff67efb8a0) at /build/buildd/gtk+3.0-3.15.0+git20141026.4d075cf2/./gtk/gtkcellarea.c:1258

Revision history for this message
Ubuntu GNOME (ug-bot) wrote : Stacktrace.txt
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : ThreadStacktrace.txt
tags: removed: need-amd64-retrace
Revision history for this message
Tim Lunn (darkxst) wrote :

ctl-shift-I launches the gtk+ inspector, but only if you have libgtk-3-dev installed. Without that it should do nothing

Also it seems you have git snapshots of gtk 3.15 installed (via ricotz/testing), does it still happen if you purge that ppa?

Changed in ubuntu-gnome:
status: New → Incomplete
Revision history for this message
zob (zob) wrote :

I just got these updates (among them is libgtk-3.0) and it seems to be fixed. At least I can't make it crash with CTRL+SHIFT+I anymore:

Start-Date: 2014-11-01 06:52:56
Commandline: apt-get dist-upgrade
Upgrade: libgail-3-0:amd64 (3.15.1+git20141028.3f1dc871-0ubuntu1~14.10~ricotz0, 3.15.1+git20141031.00f618ea-0ubuntu1~14.10~ricotz0), gir1.2-gtk-3.0:amd64 (3.15.1+git20141028.3f1dc871-0ubuntu1~14.10~ricotz0, 3.15.1+git20141031.00f618ea-0ubuntu1~14.10~ricotz0), libglib2.0-0:amd64 (2.43.0~git20141021.4125415e-0ubuntu1~14.10~ricotz1, 2.43.0+git20141030.0728e62b-0ubuntu1~14.10~ricotz0), libgtk-3-bin:amd64 (3.15.1+git20141028.3f1dc871-0ubuntu1~14.10~ricotz0, 3.15.1+git20141031.00f618ea-0ubuntu1~14.10~ricotz0), libglib2.0-data:amd64 (2.43.0~git20141021.4125415e-0ubuntu1~14.10~ricotz1, 2.43.0+git20141030.0728e62b-0ubuntu1~14.10~ricotz0), libgtk-3-0:amd64 (3.15.1+git20141028.3f1dc871-0ubuntu1~14.10~ricotz0, 3.15.1+git20141031.00f618ea-0ubuntu1~14.10~ricotz0), libgtk-3-common:amd64 (3.15.1+git20141028.3f1dc871-0ubuntu1~14.10~ricotz0, 3.15.1+git20141031.00f618ea-0ubuntu1~14.10~ricotz0), libglib2.0-bin:amd64 (2.43.0~git20141021.4125415e-0ubuntu1~14.10~ricotz1, 2.43.0+git20141030.0728e62b-0ubuntu1~14.10~ricotz0)
End-Date: 2014-11-01 06:53:04

Revision history for this message
zob (zob) wrote :

Just for testing purposes I then installed libgtk-3-dev with these new versions and tried CTRL+SHIFT+I, which now should open the gtk+ inspector. Unfortunately it now crashes with libgtk-3-dev (3.15.1+git20141031.00f618ea-0ubuntu1~14.10~ricotz0) installed.

Revision history for this message
zob (zob) wrote :

I now purged the gnome 3 ppa and back at version 3.12.2-0ubuntu15 of libgtk-3-0 nothing crashes, neither without libgtk-3-dev installed nor without.
I should add that gtk+-inspector does not open. In fact CTRL+SHIFT+I does nothing. However it doesn't crash anything. So that bug is for the ricotz version only.

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

[Expired for Ubuntu GNOME because there has been no activity for 60 days.]

Changed in ubuntu-gnome:
status: Incomplete → Expired
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.