gedit crashed with SIGSEGV in gdk_property_change()
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
ProcVersionSign
Uname: Linux 3.2.0-15-
NonfreeKernelMo
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sat Feb 11 11:38:01 2012
ExecutablePath: /usr/bin/gedit
ProcCmdline: gedit /home/User Name/.xsession-
SegvAnalysis:
Segfault happened at: 0xb71b30cb <gdk_property_
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_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
Title: gedit crashed with SIGSEGV in gdk_property_
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
Changed in gedit: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Changed in gedit (Ubuntu): | |
status: | Confirmed → Triaged |
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 |
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.