glipper crashed with SIGSEGV in settings_notify_cb()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glipper (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
after restart on quantal
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: glipper 2.3-3
ProcVersionSign
Uname: Linux 3.5.0-15-generic i686
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
Date: Fri Sep 21 16:01:51 2012
ExecutablePath: /usr/bin/glipper
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/glipper
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xb4d87dad: mov 0x1c(%esi),%eax
PC (0xb4d87dad) ok
source "0x1c(%esi)" (0x0000001c) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: glipper
StacktraceTop:
?? () from /usr/lib/
g_cclosure_
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: glipper crashed with SIGSEGV in g_cclosure_
UpgradeStatus: Upgraded to quantal on 2012-08-17 (34 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
information type: | Private → Public |
Thank you for reporting this bug, sorry that we weren't able to provide a proper fix.
This package has been removed from the Ubuntu development release and upstream development has not been active in many years.