gedit crashed with SIGSEGV in gdk_property_change()

Bug #930601 reported by dino99
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gedit
Invalid
Medium
gedit (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Precise i386, logged as gnome-classic

was successfully using gedit to check the daily logs:
- i first opened xsession-errors
- then checked a few other logs into a second tab , closing that tab, then reopening it with an other log
- thats was working smootly till i've tried to open wtmp log: i get a greyed tab, seems to be frozen then get the crash

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gedit 3.3.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic-pae 3.2.5
Uname: Linux 3.2.0-15-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sat Feb 11 11:38:01 2012
ExecutablePath: /usr/bin/gedit
ProcCmdline: gedit /home/User Name/.xsession-errors
SegvAnalysis:
 Segfault happened at: 0xb71b30cb <gdk_property_change+11>: mov 0xc(%eax),%edx
 PC (0xb71b30cb) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 gdk_property_change () from /usr/lib/i386-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gedit crashed with SIGSEGV in gdk_property_change()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio avahi avahi-autoipd boinc cdrom couchdb crontab daemon debian-tor dialout disk fuse haldaemon klog kmem libuuid lpadmin mail messagebus mlocate mysql mythtv netdev ntp operator plugdev polkituser pulse root sambashare saned shadow ssh ssl-cert sudo syslog tty users utmp video voice www-data

Revision history for this message
dino99 (9d9) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #908713. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags: added: regression-retracer
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gdk_property_change (window=0x0, property=0x68, type=0x4, format=32, mode=GDK_PROP_MODE_REPLACE, data=0x8d705c0 "\217", nelements=12) at /build/buildd/gtk+3.0-3.3.14/./gdk/gdkwindow.c:11008
 _gtk_selection_request (widget=0x85e1600, event=0x86b60c8) at /build/buildd/gtk+3.0-3.3.14/./gtk/gtkselection.c:2455
 _gtk_marshal_BOOLEAN__BOXED (closure=0x82b9cc0, return_value=0xbfdd3e34, n_param_values=2, param_values=0x903d4f0, invocation_hint=0xbfdd3e20, marshal_data=0xb7419b60) at /build/buildd/gtk+3.0-3.3.14/./gtk/gtkmarshalers.c:85
 g_type_class_meta_marshal (closure=0x82b9cc0, return_value=0xbfdd3e34, n_param_values=2, param_values=0x903d4f0, invocation_hint=0xbfdd3e20, marshal_data=0x104) at /build/buildd/glib2.0-2.31.16/./gobject/gclosure.c:885
 g_closure_invoke (closure=0x82b9cc0, return_value=0xbfdd3e34, n_param_values=2, param_values=0x903d4f0, invocation_hint=0xbfdd3e20) at /build/buildd/glib2.0-2.31.16/./gobject/gclosure.c:774

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
tags: removed: need-i386-retrace
Revision history for this message
Vadim Rutkovsky (roignac) wrote :

Reproduced in Oneiric's version for dino99's wtmp and my own.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in gedit (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

Adding more comments:

- i hardly beleive that gedit fails to open "unknown type file. The wtmp attached is not identified as "wtmp.log" nor as a "txt" file, its "type" is "unknown" inside nautilus.
- i've selected an other file with "unknown" type, and i see gedit trying to open it, using 100 % cpu, then crash again or if not, i need to kill its process (file attached: lastlog)

So its clearly an "identification" content issue.

summary: - gedit crashed with SIGSEGV in gdk_property_change()
+ 3.3.3 : gedit crashed with SIGSEGV in gdk_property_change()
Changed in gedit:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
dino99 (9d9) wrote : Re: 3.3.3 : gedit crashed with SIGSEGV in gdk_property_change()

Following post #7 comments above, maybe gedit should consider "unknown" type file as "txt" with utf-8 formatting.

tags: added: 3.3.3
Revision history for this message
dino99 (9d9) wrote :

or ask the user to set a default type, before freezing or crashing.

Revision history for this message
dino99 (9d9) wrote :

Seems that "gedit not able to recognize encoding" has already been fixed some times ago into an "old" gedit version:

https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/75151

would like to get the same fix (#4) applied again to be able to open/read such files.

Changed in gedit (Ubuntu):
status: Confirmed → Triaged
dino99 (9d9)
summary: - 3.3.3 : gedit crashed with SIGSEGV in gdk_property_change()
+ gedit crashed with SIGSEGV in gdk_property_change()
Changed in gedit:
status: New → Invalid
Revision history for this message
dino99 (9d9) wrote :

works as expected now

Changed in gedit (Ubuntu):
status: Triaged → 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.